Re: libtool: static libs where shared can't be built

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yaakov S (Cygwin Ports) wrote: > I have a libtool library that has undefined symbols by design, so I need > to build it static. But that seems to be impossible: > > 1) Simply omit '-no-undefined': > > /bin/sh ../libtool --mode=link --tag=CXX g++ -W

Re: libtool: static libs where shared can't be built

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Wilson wrote: > First what does "/bin/sh ../libtool --version" say, when you run it in > your build directory? If it doesn't say 1.5.20, then you need to > re-libtoolize your project. I forgot to mention that I had already re-libtoolized (I c

Re: libtool: static libs where shared can't be built

Yaakov S (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a libtool library that has undefined symbols by design, so I need to build it static. But that seems to be impossible: 1) Simply omit '-no-undefined': 2) Add '-no-undefined -static' to LDFLAGS: Either way I g

libtool: static libs where shared can't be built

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a libtool library that has undefined symbols by design, so I need to build it static. But that seems to be impossible: 1) Simply omit '-no-undefined': /bin/sh ../libtool --mode=link --tag=CXX g++ -Wno-long-long -Wundef - -Wall -W -Wpointer-a