1 |
On Mar 24, 2006, at 6:56 PM, m h wrote: |
2 |
|
3 |
> On 3/24/06, m h <sesquile@×××××.com> wrote: |
4 |
>> On 3/24/06, Grobian <grobian@g.o> wrote: |
5 |
>>> On 23-03-2006 21:07:21 -0600, Kito wrote: |
6 |
>>>> On Mar 23, 2006, at 7:52 PM, m h wrote: |
7 |
>>>>>> I get: |
8 |
>>>>>> /usr/bin/ld: cannot find /lib/libz.so |
9 |
>>>>>> collect2: ld returned 1 exit status |
10 |
>>>>>> |
11 |
>>>>>> Very weird..... |
12 |
>>>>>> |
13 |
>>>> |
14 |
>>>> Hrmm, your gcc is using the system ld.... we need to fix that |
15 |
>>>> first I think. |
16 |
>>> |
17 |
>>> Probably forgot to update the symlink to ld? |
18 |
>>> |
19 |
>>>> Yeah, lets go back to the first problem of getting gcc using the |
20 |
>>>> portage |
21 |
>>>> binutils....I don't like this one ;) |
22 |
>>> |
23 |
>>> Please try. |
24 |
>>> |
25 |
>> |
26 |
>> So I tried re-emerging binutils. I guess it fails at the end, but |
27 |
>> gets far enough that it thinks it's installed... Here's the tail end: |
28 |
>> --- !empty dir /data1/tmp/Mar21 |
29 |
>> --- !empty dir /data1/tmp |
30 |
>> --- !empty dir /data1 |
31 |
>> !!! EBUILD_PHASE=postrm |
32 |
>> !!! D=/data1/tmp/Mar21/var/tmp/binpkgs/binutils-2.16.1-r1/image/ |
33 |
>> data1/tmp/Mar21 |
34 |
>> !!! DEST=/data1/tmp/Mar21/var/tmp/binpkgs/binutils-2.16.1-r1/image/ |
35 |
>> !!! PREFIX=/data1/tmp/Mar21 |
36 |
>> !!! ROOT=/data1/tmp/Mar21 |
37 |
>> /data1/tmp/Mar21/usr/bin/binutils-config: line 14: |
38 |
>> /etc/init.d/functions.sh: No such file or directory |
39 |
>> /data1/tmp/Mar21/usr/bin/binutils-config: line 14: |
40 |
>> /etc/init.d/functions.sh: No such file or directory |
41 |
>> !!! EBUILD_PHASE=clean |
42 |
>> !!! D=/data1/tmp/Mar21/var/tmp/binpkgs/binutils-2.16.1-r1/image/ |
43 |
>> data1/tmp/Mar21 |
44 |
>> !!! DEST=/data1/tmp/Mar21/var/tmp/binpkgs/binutils-2.16.1-r1/image/ |
45 |
>> !!! PREFIX=/data1/tmp/Mar21 |
46 |
>> !!! ROOT=/data1/tmp/Mar21 |
47 |
>>>>> Original instance of package unmerged safely. |
48 |
>> !!! EBUILD_PHASE=postinst |
49 |
>> !!! D=/data1/tmp/Mar21/var/tmp/portage/binutils-2.16.1-r1/image/ |
50 |
>> data1/tmp/Mar21 |
51 |
>> !!! DEST=/data1/tmp/Mar21/var/tmp/portage/binutils-2.16.1-r1/image/ |
52 |
>> !!! PREFIX=/data1/tmp/Mar21 |
53 |
>> !!! ROOT=/data1/tmp/Mar21 |
54 |
>> /data1/tmp/Mar21/usr/bin/binutils-config: line 14: |
55 |
>> /etc/init.d/functions.sh: No such file or directory |
56 |
>> /data1/tmp/Mar21/usr/bin/binutils-config: Could not source |
57 |
>> /etc/init.d/functions.sh! |
58 |
>>>>> Regenerating /etc/ld.so.cache... |
59 |
>>>>> sys-devel/binutils-2.16.1-r1 merged. |
60 |
>> !!! EBUILD_PHASE=clean |
61 |
>> !!! D=/data1/tmp/Mar21/var/tmp/portage/binutils-2.16.1-r1/image/ |
62 |
>> data1/tmp/Mar21 |
63 |
>> !!! DEST=/data1/tmp/Mar21/var/tmp/portage/binutils-2.16.1-r1/image/ |
64 |
>> !!! PREFIX=/data1/tmp/Mar21 |
65 |
>> !!! ROOT=/data1/tmp/Mar21 |
66 |
>> |
67 |
>>>>> No packages selected for removal by clean. |
68 |
>> |
69 |
>>>>> Auto-cleaning packages... |
70 |
>> |
71 |
>>>>> No outdated packages were found on your system. |
72 |
>> |
73 |
>> |
74 |
>> * error scanning /etc |
75 |
>> |
76 |
>> ------------------------------- |
77 |
>> Then it dies.... |
78 |
>> |
79 |
>> Also looking over the directories when it's trying to install, it |
80 |
>> seems like there are some places where it's trying to install/remove |
81 |
>> from ${PREFIX}/${PREFIX}! |
82 |
>> |
83 |
>> Here's an example of what I mean... |
84 |
>> --- !empty dir /data1/tmp/Mar21/data1/tmp/Mar21/usr/lib/binutils/ |
85 |
>> i686-pc-linux-gnu/2.16.1/ldscripts |
86 |
>> --- !empty dir /data1/tmp/Mar21/data1/tmp/Mar21/usr/lib/binutils/ |
87 |
>> i686-pc-linux-gnu/2.16.1/include |
88 |
>> --- !empty dir /data1/tmp/Mar21/data1/tmp/Mar21/usr/lib/binutils/ |
89 |
>> i686-pc-linux-gnu/2.16.1 |
90 |
>> --- !empty dir /data1/tmp/Mar21/data1/tmp/Mar21/usr/lib/binutils/ |
91 |
>> i686-pc-linux-gnu |
92 |
>> |
93 |
>> My PREFIX is /data1/tmp/Mar21 so there are a lot of ${PREFIX}/$ |
94 |
>> {PREFIX} |
95 |
>> |
96 |
>> Ideas about dealing with the double PREFIX? I guess Mac people are |
97 |
>> running binutils issues since they use the host linker? |
98 |
>> |
99 |
>> -matt |
100 |
>> |
101 |
> |
102 |
> Some detective work. |
103 |
> |
104 |
> It appears that the Makefile for binutils is combining together 2 |
105 |
> variables. $(DESTDIR)$(prefix) and storing it in a variable called |
106 |
> $(MAKEDIRS). DESTDIR is equal to ${D} (this is set in |
107 |
> toolchain-binutils.eclass). And ${prefix} is ... ${PREFIX} (which |
108 |
> also comes from the eclass where --prefix=${PREFIX}/usr). Since ${D} |
109 |
> ends with ${PREFIX} there ends up being a double prefix..... |
110 |
|
111 |
Nice work. I'll fix this in the next big commit. In the meantime you |
112 |
can try changing that ${D} to ${DEST}. |
113 |
|
114 |
FYI, in the ebuild environment from now on we will be using the $ |
115 |
{EDEST} variable, which equates to ${D} without the appended PREFIX. |
116 |
|
117 |
--Kito |
118 |
|
119 |
|
120 |
|
121 |
|
122 |
-- |
123 |
gentoo-osx@g.o mailing list |