On Sat, 14 Nov 2009 23:34:46 +0100 Daniel Pielmeier wrote: > David Relson schrieb am 14.11.2009 21:33: > > As background, http://bugs.gentoo.org/show_bug.cgi?id=233097 has an > > experimental, unsupported ebuild for openwatcom-1.7.1 and it doesn't > > quite work :-< > > > > The ebuild's src_compile function is: > > > > src_compile() { > > ./build.sh || die "build.sh failed" > > } > > > > When I run "emerge =dev-lang/openwatcom-1.7.1", the build fails with > > > > > > /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../i686-pc-linux-gnu/bin/ld: > > i386:x86-64 architecture of input file `bootstrp/clibext.o' is > > incompatible with i386 output distcc[16016] ERROR: compile > > (null) on localhost failed > > > > The full output of the emerge command is in the attached file. > > > > Alternatively, I can manually unpack and build with commands: > > > > ebuild =dev-lang/openwatcom-1.7.1.ebuild unpack > > cd /var/tmp/dev-lang/openwatcom-1.7.1/work > > ./build.sh > > > > With the steps performed manually, the compilation works properly. > > > > Anybody familiar with the "i386:x86-64 ... incompatible ... i386" > > message and know what it means? > > > > Any suggestions on ebuild changes to correct this behavior? > > > > Thanks ! > > > > David > > Okay, this is not a distcc problem. > > From looking at the bug. Do you really think by just tricking the > architecture check to accept x86_64 will make it magically compile. > You can't be serious! This software does not build on x86_64 at the > moment. If you don't have the appropriate programming skills to fix > this yourself you have to wait for the openwatcom developers to make > it x86_64 ready. > > -- > Daniel Pielmeier
Daniel, A detail I meant to include in my original posting is that I'm attempting the build on (and for) a 32 bit machine. So distcc _is_ the problem. The lack of 64-bit buildability for openwatcom is a whole 'nother subject and I'm in communication with the developer about it. Regards, David
