[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libtool 2.2.6 bug: CR/LF result (from sed?) causes "not a valid .la / .l
From: |
Rugxulo |
Subject: |
libtool 2.2.6 bug: CR/LF result (from sed?) causes "not a valid .la / .lo" errors |
Date: |
Sun, 21 Feb 2010 08:47:32 -0600 |
Hi, it's me again,
I know the latest libtool is (apparently) 2.2.7.a, but I'm unsure how
to "upgrade" to it from 2.2.6. Replace ltmain.sh? Run "./libtoolize"?
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. 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).
For now, my workaround is this (which is lots better than manually
running "dtou .../*.l[ao]" every time it errors / exits):
sed -i "/\.l[oa]:/{n;n;s/.*/\tdtou address@hidden&/}" src/makefile
lstring/makefile
(this is after running "./configure", of course)
Any chance of fixing this in future releases?
- libtool 2.2.6 bug: CR/LF result (from sed?) causes "not a valid .la / .lo" errors,
Rugxulo <=