1 |
On 2009-10-31, Dirk Tilger <dirk@××××××.de> wrote: |
2 |
> I'm currently freshly bootstrapping prefix on a Debian system. Bash |
3 |
> fails compilation with: |
4 |
> |
5 |
> -----8<----- |
6 |
> gcc -L./builtins -L./lib/readline -L./lib/readline -L./lib/glob -L./lib/tilde -L./lib/sh -Wl,-O1 -rdynamic -O2 -march=i686 -pipe -o bash shell.o eval.o y.tab.o general.o make_cmd.o print_cmd.o dispose_cmd.o execute_cmd.o variables.o copy_cmd.o error.o expr.o flags.o jobs.o subst.o hashcmd.o hashlib.o mailcheck.o trap.o input.o unwind_prot.o pathexp.o sig.o test.o version.o alias.o array.o arrayfunc.o braces.o bracecomp.o bashhist.o bashline.o list.o stringlib.o locale.o findcmd.o redir.o pcomplete.o pcomplib.o syntax.o xmalloc.o -lbuiltins -lsh -lreadline -lhistory -lcurses -lglob -ltilde -ldl |
7 |
> /usr/bin/ld: cannot find -lcurses |
8 |
> collect2: ld returned 1 exit status |
9 |
> make: *** [bash] Error 1 |
10 |
> * ERROR: app-shells/bash-3.2_p48-r1 failed: |
11 |
> * make failed |
12 |
> -----8<----- |
13 |
> |
14 |
> For some reason the prefix linkage path ($EPREFIX/usr/lib) does not make |
15 |
> it into the compilation script. I had the ebuild dropping into a bash |
16 |
> and noticed no LD_LIBRARY_FLAGS&Co had been set either. Where are these |
17 |
> things set normally? |
18 |
|
19 |
bash compiles just fine if I modify the ebuild as follows: |
20 |
|
21 |
-----8<----- |
22 |
--- var/db/patchmaker/app-shells/bash/4.0_p33/bash-4.0_p33.ebuild 2009-09-14 09:17:25.000000000 +0200 |
23 |
+++ usr/portage/app-shells/bash/bash-4.0_p33.ebuild 2009-11-03 08:51:28.000000000 +0100 |
24 |
@@ -121,6 +121,7 @@ |
25 |
-DSYS_BASH_LOGOUT=\'\"${EPREFIX}/etc/bash/bash_logout\"\' \ |
26 |
-DNON_INTERACTIVE_LOGIN_SHELLS \ |
27 |
-DSSH_SOURCE_BASHRC |
28 |
+ append-ldflags -L${EPREFIX}/usr/lib |
29 |
else |
30 |
append-cppflags \ |
31 |
-DDEFAULT_PATH_VALUE=\'\"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\"\' \ |
32 |
-----8<----- |
33 |
|
34 |
That doesn't make much sense, does it? |
35 |
|
36 |
Dirk. |