I don't think this has much to do with ruby-god itself; the C extension is built using a Makefile dynamically produced by a gem2deb utility:
/usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb ruby-god /usr/bin/ruby1.8 extconf.rb checking for linux/netlink.h... yes checking for linux/connector.h... yes checking for linux/cn_proc.h... yes creating Makefile ... Would you then agree that a faulty linking of this extension on some architectures is more likely a result of some bug in gem2deb ? Cheers, --Seb On Sep/17, YunQiang Su wrote: > Package: ruby-god > Version: 0.13.2-3 > X-Debbugs-CC: wzss...@gmail.com > > This package has one or more -L/usr/lib in its build system, > which will make it ftbfs if there is libraries under /usr/lib, > while is not the default architecture, mips* for example. > > On mips* systems, /usr/lib is defined as place to hold O32 > libraries, and /usr/lib32 for N32, and /usr/lib64 is for N64. > > Beside the way, on the multiarch system like Debian, user may install > libraries under /usr/lib by hand. > > Please use the default search path if you can, and please consider fix > this. > > I will try to fix this bug, while if you can help to fix it, > It will be very appreciative. > > The attachement is the buildlog of this package on mips64el platform. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
