Hi,
Right the release is done so I've got round to try your suggestion of:
set -x
AC_EXEEXT
set +x
Libtool 1.3c still gets the extension of ".C" for an executable. I've
attached to config.log and a copy of all the output messages on the screen.
Hope this helps,
Simon
configure.out.gz
On Apr 3, 2001, "s_a_white" [EMAIL PROTECTED] wrote:
Gary second suggestion worked after removing the back slashes:
Really? Wow! This is very good news, indeed. I'm quite surprised!
I suppose we could arrange for AC_PROG_LIBTOOL to pre-pend
'${CONFIG_SHELL-/bin/sh} `pwd`/libtool ' to
On Tuesday 03 April 2001 9:28 am, Alexandre Oliva wrote:
On Apr 3, 2001, "s_a_white" [EMAIL PROTECTED] wrote:
Gary second suggestion worked after removing the back slashes:
Really? Wow! This is very good news, indeed. I'm quite surprised!
I suppose we could arrange for AC_PROG_LIBTOOL
On Apr 1, 2001, "Gary V. Vaughan" [EMAIL PROTECTED] wrote:
This is a known deficiency in the coupling between libtool and autoconf,
which needs fixing at some point. In the mean time how about (wild guess
here!):
save_CC=$CC
CC="${SHELL-/bin/sh} ${top_srcdir)/libtool $CC"
Hi,
I've been using libtool 1.3c for a while due to needing it so dependency
information is correctly obtained from the la files. However, I came to
build a binary which uses libtool libraries and found that this version
detects that my system should use an executable extention of ".C". This
