LDFLAGS=-static isn't good enough?
On Fri, Jul 9, 2010 at 6:08 AM, Oliver Jowett <oliver.jow...@gmail.com>wrote:
> Jacky wrote:
> > Many thanks! sorry for the late reply - I've just went back. :)
> > I tried this:
> > ja...@alpha:~/workspace/protobuf-2.3.0/src$ ldd protoc
> > linux-vdso.so.1 => (0x00007fff427ba000)
> > libz.so.1 => /lib/libz.so.1 (0x00007fe2e1485000)
> > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fe2e1171000)
> > libm.so.6 => /lib/libm.so.6 (0x00007fe2e0eed000)
> > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fe2e0cd6000)
> > libpthread.so.0 => /lib/libpthread.so.0 (0x00007fe2e0ab9000)
> > libc.so.6 => /lib/libc.so.6 (0x00007fe2e0736000)
> > /lib64/ld-linux-x86-64.so.2 (0x00007fe2e16b9000)
> > It seems like the binary file still depends on some gcc-related shared
> > objects.
> I actually spent a while today dealing with the same issue, and
> eventually admitted defeat and gave up on trying to convince libtool and
> friends to behave.
> Instead I did this:
> ./configure --disable-shared
> rm src/protoc && make # this is just to make the link command obvious
> Then rerun the final invocation of g++ that libtool runs to link protoc,
> adding "-static" to it.
> (Yes, I know, static binaries are evil, but so is libstdc++ version skew)
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@googlegroups.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at