On Sat, 13 Apr 2002 11:44:09 +0900, R. Lahaye wrote:

>
>Hi,
>
>I haven't updated the configure script for the last few weeks.
>Did that today and all of a sudden the configure script stops
>with an error:
>
>$ ./CVSMake
>./CVSMake running in /home/lahaye/SOFTWARE/lesstif
>Running on:
>Linux 2.4.3-20mdk #1 Sun Apr 15 23:03:10 CEST 2001 i686
>Using:
>Autoconf version 2.13
>automake (GNU automake) 1.5
>ltmain.sh (GNU libtool) 1.4 (1.920 2001/04/24 23:26:18)
>
>running libtoolize
>running aclocal
>running autoconf
>running autoheader
>running automake
>automake: configure.in: installing `./install-sh'
>automake: configure.in: installing `./mkinstalldirs'
>automake: configure.in: installing `./missing'
>./CVSMake running in /home/lahaye/SOFTWARE/lesstif/test
>
>running libtoolize
>running aclocal
>running autoconf
>running autoheader
>running automake
>automake: configure.in: installing `./mkinstalldirs'
>automake: configure.in: installing `./missing'
>configure.in: 936: required file `./ltmain.sh' not found
>$ find . | grep ltmain.sh
>./test/ltmain.sh
>./ltmain.sh
>$ ./configure
>configure: error: can not find sources in . or ..
>$
>
>ltmain.sh is there ?!?!
>Any idea what is causing the configure error?
>Is configure.in broken?

The 
configure.in: 936: required file `./ltmain.sh' not found
message is a known bug in the auto* tools of that 
versions. The interesting question is why configure
fails to run - indeed.

Ah, I got it!
configure always checks for the sources by looking
for a single hard-wired file, actually it does look for:
AC_INIT(include/LTmisc.h)

However I just moved that file to include/Motif-1.2/include/
and so the test is broken! I'll repair it in a minute.

Thanks for the report.


---
Alexander Mai
[EMAIL PROTECTED]


_______________________________________________
Lesstif mailing list
[EMAIL PROTECTED]
https://terror.hungry.com/mailman/listinfo/lesstif

Reply via email to