[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem with Libtool 2.2.x's AC_PROG_SED on Solaris
From: |
Daniel Richard G. |
Subject: |
Problem with Libtool 2.2.x's AC_PROG_SED on Solaris |
Date: |
Sat, 25 Oct 2008 00:31:25 -0400 |
I am migrating a build process from Libtool 1.5.x to 2.2.6a. This build
involves programs with many dependencies, such that very long
compiler/linker invocations are the norm.
1.5.x worked correctly for this build on both Linux and Solaris. 2.2.6a
works correctly on Linux, but fails on Solaris. Just prior to said failure,
libtool gives three "Output line too long" warnings, and a linker
invocation that is clearly truncated.
The problem is sed(1); more specifically, /usr/bin/sed. This is the program
that AC_PROG_SED finds and returns for use in the libtool script. But this
same program truncates its output, which makes it unsuitable for libtool.
1.5.x, on the other hand, used /usr/xpg4/bin/sed. This one does not
truncate output. If I edit the 2.2.6a libtool script to use the XPG4
version, the build completes without further trouble.
Between 1.5.x and 2.2.x, the behavior of AC_PROG_SED changed so that now,
on Solaris, it chooses the broken version of sed(1).
P.S.: Please Cc: any replies to me, as I am not subscribed to this list.
--Daniel
--
NAME = Daniel Richard G. ## Remember, skunks _\|/_ meef?
EMAIL1 = address@hidden ## don't smell bad--- (/o|o\) /
EMAIL2 = address@hidden ## it's the people who < (^),>
WWW = http://www.******.org/ ## annoy them that do! / \
--
(****** = site not yet online)
- Problem with Libtool 2.2.x's AC_PROG_SED on Solaris,
Daniel Richard G. <=