1 |
On Mon, 2005-11-28 at 15:07 +0100, Nicolas MASSE wrote: |
2 |
> Hello, |
3 |
> |
4 |
> I experience problems when trying to emerge bash-3.0-r13 on amd64. |
5 |
> |
6 |
> The compilation ends with : |
7 |
> |
8 |
> make[1]: Leaving directory `/tmp/portage/bash-3.0-r13/work/bash-3.0/lib/tilde' |
9 |
> rm -f bash |
10 |
> x86_64-pc-linux-gnu-gcc -L./builtins -L./lib/readline -L./lib/readline |
11 |
> -L./lib/glob -L./lib/tilde -L./lib/sh -rdynamic -march=athlon64 -O2 -pipe |
12 |
> -fforce-addr -o bash shell.o eval.o y.tab.o general.o make_cmd.o print_cmd.o |
13 |
> dispose_cmd.o execute_cmd.o variables.o copy_cmd.o error.o expr.o flags.o |
14 |
> jobs.o subst.o hashcmd.o hashlib.o mailcheck.o trap.o input.o unwind_prot.o |
15 |
> pathexp.o sig.o test.o version.o alias.o array.o arrayfunc.o braces.o |
16 |
> bracecomp.o bashhist.o bashline.o list.o stringlib.o locale.o findcmd.o |
17 |
> redir.o pcomplete.o pcomplib.o syntax.o xmalloc.o -lbuiltins |
18 |
> -lsh ./lib/readline/libreadline.a ./lib/readline/libhistory.a -Wl,-Bstatic |
19 |
> -lncurses -Wl,-Bdynamic -lglob -ltilde -ldl |
20 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/libncurses.a(lib_termcap.o): |
21 |
> relocation R_X86_64_32S against `boolcodes' can not be used when making a |
22 |
> shared object; recompile with -fPIC |
23 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../lib64/libncurses.a: could |
24 |
> not read symbols: Bad value |
25 |
> collect2: ld returned 1 exit status |
26 |
> make: *** [bash] Error 1 |
27 |
> |
28 |
> !!! ERROR: app-shells/bash-3.0-r13 failed. |
29 |
> !!! Function src_compile, Line 123, Exitcode 2 |
30 |
> !!! make failed |
31 |
> !!! If you need support, post the topmost build error, NOT this status |
32 |
> message. |
33 |
> |
34 |
> I use the profile default-linux/amd64/2005.1 and I started from a stage 3. |
35 |
> |
36 |
> I understand that I must recompile something with the -fPIC option, but I |
37 |
> don't know if it's bash or ncurses. And then, I think I shouldn't add -fPIC |
38 |
> to my LDFLAGS or CFLAGS because it seems discouraged. Is it a bug in an |
39 |
> ebuild ? |
40 |
> |
41 |
> Here are information : |
42 |
> CFLAGS="-march=athlon64 -O2 -pipe -fforce-addr" |
43 |
> CHOST="x86_64-pc-linux-gnu" |
44 |
> USE="amd64 X acl alsa berkdb crypt hardened ipv6 jpeg kde nls nptl nptlonly |
45 |
> pam pic png readline ssl tcpd tiff unicode userlocales xinerama zlib |
46 |
> userland_GNU kernel_linux elibc_glibc" |
47 |
> |
48 |
> I hope it was not to hard to understand my (bad) english. |
49 |
> |
50 |
> Thanks. |
51 |
> |
52 |
> Nicolas MASSE |
53 |
> |
54 |
First, I suggest that you try it without the -fforce-addr option as that |
55 |
forces registers to be used for addr arithmetic and the pic stuff uses |
56 |
the rbx register for other address stuff. The -fPIC option should only |
57 |
be enabled by the ebuild author and never placed in your CFLAGS. If the |
58 |
problem persists without the un-advised cflag then please file a bug |
59 |
report and include me in the CC list. |
60 |
|
61 |
-- |
62 |
Tres Melton |
63 |
IRC & Gentoo: RiverRat |