Restating the remaining issues since (a) it's a new month for the
mailman archiver (b) some issues have been resolved (yay!)
> 3. relinking .exe's. Over and over and over and over. This doesn't
> really cause project builds to FAIL, but it is HIGHLY annoying --
> and has the possibility of an
Charles Wilson wrote:
Bob Friesenhahn wrote:
Yes, but I only saw that once. I have not verified that it always
happens. It might've been a fluke. Have you seen this 'go ahead and
build the shared lib even though I just finished complaining that I
couldn't' behavior, too?
Yes, I have. I
this problem has been resolved. See patch on libtool-patches.
--Chuck
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
Restating the remaining issues since (a) it's a new month for the
mailman archiver (b) some issues have been resolved (yay!)
> 1. C++ (actually, all tags except C) is broken. This is because the
> non-C tags extract the list of runtime stdlibs from the compiler,
> and then explicitly add them t
this problem has been resolved. See patch on libtool-patches.
--Chuck
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
Hello,
i want to compile libtool. But i received by exwecuting the 'make'
command the following message:
cd libtool-1.4.3
bash-2.03# ./configure
creating cache ./config.cache
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking wheth
Whats wrong ??
make
Making all in .
make[1]: Entering directory `/usr/apache_1.3.27/source/libtool-1.4.3'
CONFIG_FILES=libtoolize CONFIG_HEADERS= /bin/sh ./config.status
creating libtoolize
chmod +x libtoolize
make[1]: Leaving directory `/usr/apache_1.3.27/source/libtool-1.4.3'
Making all in libl
