Michael Carmack [EMAIL PROTECTED] writes:
The specific problem you are having seems to be that the
libltdl/configure script is produced by a different autoconf version
than Guile's configure script.
Hmm. Do you know of a way to resolve this? Should I just try to avoid
setting
On Wed, Jan 02, 2002 at 11:05:06PM +0100, Marius Vollmer wrote:
Michael Carmack [EMAIL PROTECTED] writes:
The problem below still seems to be present in a recent CVS checkout.
It seems that the environment variables that I have set are causing
'configure' to fail once it enters libltdl.
On Mon, Oct 29, 2001 at 08:50:16PM +, Michael Carmack wrote:
Hello bug-guile.
The problem below still seems to be present in a recent CVS checkout.
It seems that the environment variables that I have set are causing
'configure' to fail once it enters libltdl. Apparently the manner in
which
On Mon, Nov 12, 2001 at 11:07:41PM +0100, Marius Vollmer wrote:
Short followup to the previous message: The following is the way that
I originally called 'configure'. Note that I did not explicitly call
configure with the environment variables, but they show up in the
recursive calls:
Michael Carmack [EMAIL PROTECTED] writes:
This affects 1.5.4, but not 1.4 or 1.3.2a. Apparently in some sort of
recursive configure, the original configure attempts to pass environment
variables, but during 'libltdl' this seems to cause a problem.
This is probably caused by libltdl using
This affects 1.5.4, but not 1.4 or 1.3.2a. Apparently in some sort of
recursive configure, the original configure attempts to pass environment
variables, but during 'libltdl' this seems to cause a problem. Here is
the output:
configure: configuring in libltdl
configure: running /bin/sh
