1 |
David Relson schrieb am 14.11.2009 21:33: |
2 |
> As background, http://bugs.gentoo.org/show_bug.cgi?id=233097 has an |
3 |
> experimental, unsupported ebuild for openwatcom-1.7.1 and it doesn't |
4 |
> quite work :-< |
5 |
> |
6 |
> The ebuild's src_compile function is: |
7 |
> |
8 |
> src_compile() { |
9 |
> ./build.sh || die "build.sh failed" |
10 |
> } |
11 |
> |
12 |
> When I run "emerge =dev-lang/openwatcom-1.7.1", the build fails with |
13 |
> |
14 |
> /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../i686-pc-linux-gnu/bin/ld: |
15 |
> i386:x86-64 architecture of input file `bootstrp/clibext.o' is |
16 |
> incompatible with i386 output distcc[16016] ERROR: compile (null) |
17 |
> on localhost failed |
18 |
> |
19 |
> The full output of the emerge command is in the attached file. |
20 |
> |
21 |
> Alternatively, I can manually unpack and build with commands: |
22 |
> |
23 |
> ebuild =dev-lang/openwatcom-1.7.1.ebuild unpack |
24 |
> cd /var/tmp/dev-lang/openwatcom-1.7.1/work |
25 |
> ./build.sh |
26 |
> |
27 |
> With the steps performed manually, the compilation works properly. |
28 |
> |
29 |
> Anybody familiar with the "i386:x86-64 ... incompatible ... i386" |
30 |
> message and know what it means? |
31 |
> |
32 |
> Any suggestions on ebuild changes to correct this behavior? |
33 |
> |
34 |
> Thanks ! |
35 |
> |
36 |
> David |
37 |
|
38 |
Okay, this is not a distcc problem. |
39 |
|
40 |
From looking at the bug. Do you really think by just tricking the |
41 |
architecture check to accept x86_64 will make it magically compile. You |
42 |
can't be serious! This software does not build on x86_64 at the moment. |
43 |
If you don't have the appropriate programming skills to fix this |
44 |
yourself you have to wait for the openwatcom developers to make it |
45 |
x86_64 ready. |
46 |
|
47 |
-- |
48 |
Daniel Pielmeier |