------- Comment #8 from 3dw4rd at verizon dot net  2009-12-09 13:22 -------
Subject: Re:  cannot find -lgcc_s

howarth at nitro dot med dot uc dot edu wrote:
> ------- Comment #7 from howarth at nitro dot med dot uc dot edu  2009-12-09 
> 04:21 -------
> (In reply to comment #6)
>   
>> I have this problem of MacOSX 10.3
>> $ gcc -v
>> Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
>> Thread model: posix
>> gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)
>>
>> When I do a make on an empty directory it gets all the way into stage3 
>> linking
>> libstdc++ until this:
>>
>> /usr/bin/ld: can't locate file for: -lgcc_s.10.4
>>
>> There are several libgcc_s around:
>>
>> MacOSX:~/obj ed$ find . -name libgcc_s\*
>> ./gcc/libgcc_s.1.dylib
>> ./gcc/libgcc_s_ppc64.1.dylib
>> ./gcc/libgcc_s_x86_64.1.dylib
>> ./powerpc-apple-darwin7.9.0/libgcc/libgcc_s.1.dylib
>> ./powerpc-apple-darwin7.9.0/libgcc/libgcc_s.dylib
>> ./prev-gcc/libgcc_s.1.dylib
>> ./prev-gcc/libgcc_s_ppc64.1.dylib
>> ./prev-gcc/libgcc_s_x86_64.1.dylib
>> ./prev-powerpc-apple-darwin7.9.0/libgcc/libgcc_s.1.dylib
>> ./prev-powerpc-apple-darwin7.9.0/libgcc/libgcc_s.dylib
>> ./stage1-gcc/libgcc_s.1.dylib
>> ./stage1-gcc/libgcc_s_ppc64.1.dylib
>> ./stage1-gcc/libgcc_s_x86_64.1.dylib
>> ./stage1-powerpc-apple-darwin7.9.0/libgcc/libgcc_s.1.dylib
>> ./stage1-powerpc-apple-darwin7.9.0/libgcc/libgcc_s.dylib
>>
>> I'm actually surprised by the ppc64 and x86_64 libs - I'm not building a 
>> cross
>> compiler.
>>
>>     
>
> I would be shocked if gcc trunk built on darwin7. Unless I am mistaken, we now
> assume
> that all darwin targets support dwarf which isn't the default case until Xcode
> 2.4 (10.4).
>
>
>   
I've been bootstrapping trunk happily up till about a couple months ago: 
10.15.2009.

Also, I've noticed a lot of issues with libgcc_s on other targets.  It 
looks like a build system change.

Is there a way to get the SVN version of a gcc?  I remember some 
discussion of that way back.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37079

Reply via email to