On Fri, 17 Aug 2007, Jason Curl wrote:
I have a system that supports shared libraries (Solaris 9). As part of some
checks for 'getopt_long' I check if it exists in 'libiberty' if I can't find
it in the standard system. It's there in libiberty. Now the problem occurs
because there's only "libi
Hello,
I've been testing my library now on various platforms and have come
across something else that I didn't expect.
I have a system that supports shared libraries (Solaris 9). As part of
some checks for 'getopt_long' I check if it exists in 'libiberty' if I
can't find it in the standard s
Ralf Wildenhues wrote:
* Jason Curl wrote on Fri, Aug 17, 2007 at 12:05:44AM CEST:
I've just switched over to using libtool instead of using static
libraries. I've installed autoconf-2.61, automake-1.10 and libtool-1.5.24.
The library builds fine under Linux, but won't link under Solaris Sp
* Jason Curl wrote on Fri, Aug 17, 2007 at 12:05:44AM CEST:
>
> I've just switched over to using libtool instead of using static
> libraries. I've installed autoconf-2.61, automake-1.10 and libtool-1.5.24.
>
> The library builds fine under Linux, but won't link under Solaris Sparc
> 2.10.
[...]
Bad posting to my own posts so soon. But I've tried a few other systems
I have at hand.
Jason Curl wrote:
Hello,
I've just switched over to using libtool instead of using static
libraries. I've installed autoconf-2.61, automake-1.10 and
libtool-1.5.24.
The library builds fine under Linux,
Hello,
I've just switched over to using libtool instead of using static
libraries. I've installed autoconf-2.61, automake-1.10 and libtool-1.5.24.
The library builds fine under Linux, but won't link under Solaris Sparc
2.10.
/bin/bash ../../libtool --tag=CC --mode=link /opt/sfw/bin/gcc
-
