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:

./configure 
    --prefix=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1 
    --bindir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/bin 
    --sbindir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/bin 
    --mandir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/doc/man 
    --infodir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/doc/info 
    --sysconfdir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/etc 
    --libdir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/lib 
    --includedir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/include 
    --datadir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/share 
    --localstatedir=/pkg/gnu/guile/1.5.4/.i686-pc-linux-gnu/.karmak.1/var/run


> 
> > 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 autoconf 2.13 while the rest
> of Guile uses autoconf 2.5x.  We need to take care that we deliver
> configure scripts that are consistent.
> 
> I'll fix this.  Can you try a `stable' snapshot from, say, tomorrow?

_______________________________________________
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile

Reply via email to