1 |
On Mar 21, 2006, at 1:21 PM, Grobian wrote: |
2 |
|
3 |
> On 21-03-2006 11:05:22 -0800, m h wrote: |
4 |
>> Has anyone else ran into this? I'm not setting this flag and don't |
5 |
>> see it in the ebuilds.... |
6 |
> |
7 |
> Yep sure I do! |
8 |
> |
9 |
> I believe it had to do with my install of GCC. There was a problem |
10 |
> somewhere, but I don't recall anymore what. Let me do a quick google. |
11 |
> |
12 |
> You say you emerged GCC, are you sure it is using it? The stack |
13 |
> protector stuff needs a patch, and I think it's in the Gentoo one. I |
14 |
> think now I now again what the problem is. |
15 |
> |
16 |
> You emerged Gentoo gcc, but you're not using it, because: |
17 |
> to use a Gentoo compiler, you need eselect-gcc or something. And for |
18 |
> that to emerge, you need a lot of packages, including the compiler. |
19 |
|
20 |
Looking at your emerge info, it looks like DEFAULT_PATH has other |
21 |
stuff before the prefixed paths. This will of course have the host os |
22 |
gcc found before the portage version(s). Figure out where the |
23 |
additional path entries are getting prepended and it might work. |
24 |
|
25 |
> |
26 |
> So, what you need to do, is setup yourself the basic symlinks to the |
27 |
> Gentoo compiler, instead of the files you installed manually. |
28 |
> |
29 |
> I remember I made a bunch of symlinks to the Gentoo gcc, and then it |
30 |
> worked flawlessly. |
31 |
> |
32 |
> |
33 |
> -- |
34 |
> Fabian Groffen |
35 |
> Gentoo for Mac OS X Project |
36 |
> -- |
37 |
> gentoo-osx@g.o mailing list |
38 |
> |
39 |
|
40 |
--Kito |
41 |
|
42 |
|
43 |
|
44 |
|
45 |
-- |
46 |
gentoo-osx@g.o mailing list |