Re: GCC 4.3.3 can't link stdc++ statically on OS X

[Gregory Weston]

In article 
<66f6b8c1-7f9d-4bc9-9f03-47dcc24e2433@z1g2000yqn.googlegroups.com>,
 "fft1976@gmail.com" <fft1976@gmail.com> wrote:

> Compiling the standard Hello World with
> 
> g++ -static-libgcc hello.cpp
> 
> Results in a binary that's linked dynamically to libstdc++.6.dylib.
> 
> I want that library linked statically, so I tried the insanely geeky
> Linux-inspired workaround:
> 
> http://www.trilithium.com/johan/2005/06/static-libstdc/
> 
> $ a=`g++ -print-file-name=libstdc++.a`
> $ d=`dirname $a`
> $ g++ -static-libgcc -L${d} hello.cpp
> $ otool -L a.out
> 
> This shows a.out still linked dynamically to libstdc++.6.dylib
> 
> Any tips? Is this a bug? I know that Xcode has its own solution, but I
> don't use Xcode.

Possibly this:

<http://lists.apple.com/archives/Unix-porting/2006/Aug/msg00012.html>

-- 
I saw a truck today that had "AAA Batteries / Delivered and Installed" on the
side. My first thought was: That's a really weird business model. How many
inept people have urgent need of skinny little battery cells?