1 |
I'm also happy to see this way as an option at least. I don't have good |
2 |
arguments yet, but I feel there's more in it somehow. |
3 |
|
4 |
On the other hand, (turning my head over to *our* glep42) it imposes a |
5 |
problem that needs to be addressable somehow by having the handles to |
6 |
dynamically do the right things depending on apple/gnu cc-suite, if you |
7 |
get what I mean. |
8 |
|
9 |
Nathan wrote: |
10 |
>> [1] I chose to use the apple branch of gcc, as most upstream packages |
11 |
>> have started expecting it on Darwin systems, and have started using |
12 |
>> apple-specific flags such as -mdynamic-no-pic and -no-cpp-precomp and |
13 |
>> -faltivec, so I figured this is the path of least resistance. Plus |
14 |
>> this allows us to take advantage of Frameworks... |
15 |
> |
16 |
> Coolness. I assumed that upstream support for apple's gcc hadn't |
17 |
> occurred. Glad to be wrong if it means we get extras from Apple. |
18 |
> |
19 |
|
20 |
-- |
21 |
Fabian Groffen |
22 |
Gentoo for Mac OS X Project -- Interim Lead |
23 |
-- |
24 |
gentoo-osx@g.o mailing list |