Re: libtool 2.2.6 bug: CR/LF result (from sed?) causes "not a valid .la / .lo" errors

[Ralf Wildenhues]

Hello Rugxulo,

thanks for the report.

* Rugxulo wrote on Sun, Feb 21, 2010 at 03:47:32PM CET:
> I know the latest libtool is (apparently) 2.2.7.a,

The most recent stable is 2.2.6b, the current git development is 2.2.7a.

> but I'm unsure how
> to "upgrade" to it from 2.2.6. Replace ltmain.sh? Run "./libtoolize"?

Typically, run 'autoreconf -vif' with both the new libtoolize being
early in PATH, and aclocal finding the *.m4 macros of the new Libtool
installation.  To do it manually, replace all macro files/macro
expansions (could be within a m4/ subdir of your package, or a
handwritten acinclude.m4 or aclocal.m4 file, or an aclocal-generated
aclocal.m4 file; I don't know your package setup) as well as ltmain.sh
and rerun autoconf.

> Anyways, it seems that libtool 2.2.6 (used by BRexx 2.1.8 and
> presumably other stuff) doesn't like CR/LF .la .lo files, and it will
> exit with a "not valid" error if found.

Please provide a copy-and-paste of the full command that failed, plus
all of its output.  libtool does not produce a "not valid" error message
without any further details.  If it's a libtool command line, rerun it
with --debug added as first argument to libtool, and send all of that
output as well (gzip'ed is fine).

Your description does not make it clear to me whether it's libtool or
libltdl that fails.  I'm guessing though that one of the func_lalib_p
or func_lalib_unsafe_p functions fails.  Does the command work if you
replace the definition of func_lalib_unsafe_p in the generated libtool
script with a call to
  func_lalib_p "$@"

?

> However, DJGPP sed always
> produces CR/LF text files, even when the file operated on was
> originally LF only. And libtool erroring on every CR/LF .la / .lo is
> definitely disruptive to the make process (several times for BRexx, at
> least).

It seems your shell does not cope well when reading scripts from text
files with exec, a la
  exec <text-file
  read line
  echo $line
  exec <&-

> Any chance of fixing this in future releases?

Sure, if we can analyze the error.

Any chance you could run the Libtool testsuite on your system (see
README for details)?

Thanks,
Ralf