On Wed, Oct 21, 2009 at 1:00 PM, Aidan Gauland <[email protected]>wrote:
> Ryan McCoskrie wrote: > >> Are you setting the archtitecture flag while compiling _as well as_ >> linking? >> > > Ah, yes, that would be helpful, wouldn't it? Now that I *really* have that > option set for the gcc, and not just ld, ld is complaining about > incompatible Shared Object (extention "so") files, which seems to fit what > Volker said. I don't know much about binary execuatbles at this level, but > why does it care about the .so files themselves? I thought they were only > used at runtime and the header files were used for compilation. > > Anyway, if what Volker said is true, then I think I'll follow Nick's > suggestion and compile in a chroot environment. > > Thanks, > Aidan > Also, sometimes you need a differently build CHOST compiler. That is, I believe on amd64, your compiler is likely to have CHOST of 'x86_64-pc-linux-gnu' , and you need an i686 chost. Essentially, I think what you're looking for is a cross-dev toolkit, or a chroot with a crossdev environment built in it. Sorry, Don't know more. -- Kent perl -e "print substr( \"edrgmaM SPA nocomil.i...@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" http://kent-fredric.fox.geek.nz
