I'm curious. I thought I knew shell scripting and the basics of
automake but I don't know what 'fnord' is (or is it just a variable like
foo and/or bar). Perhaps as a consequence of that I don't know why
there is a need for a seperate LIBTOOL_BEGIN_COMPILE_CC and
LIBTOOL_END_COMPILE_CC macro (as
I have a strange problem that is trivial to reproduce as shown here:
~/libtool# libtool --version
ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)
~/libtool# libtool --mode=link gcc -o test test.o -rpath /usr/lib -L/usr/lib -lpng
-lexpat
gcc -o .libs/test test.o -L/usr/lib -lpng /usr/li
At Thu, 27 Nov 2003 11:10:14 +0900,
[EMAIL PROTECTED] wrote:
> So I hope to keep argv[0] for the wrapper, but I have no idea about it
> with portability (bash has -a option, but it is not portable).
I made a patch for it. The patch makes a temporary progam to use
execv(3).
Is the patch is accepta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Trenker wrote:
| I have a strange problem that is trivial to reproduce as shown here:
|
| ~/libtool# libtool --version
| ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)
|
| ~/libtool# libtool --mode=link gcc -o test test.o -rpath /usr/
I am porting a package to Darwin (compiles fine on Linux) consisting of
several convenience libraries, a few test programs, and an application.
I'm using Autoconf 2.58, automake 1.7.9, and libtool 1.5 (with the
AC_LIBTOOL_TAGS patch).
The main application compiles and links correctly, but a tes
