[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tilde problem when creating libtool
From: |
Peter Dyballa |
Subject: |
Tilde problem when creating libtool |
Date: |
Sat, 2 Dec 2006 15:27:24 +0100 |
Hello!
Recently, it seems, things for some X libraries in X11R7.1 changed in
a way that libtool scripts cannot be re-created OK. The symptom is:
ar cru .libs/libXdmcp.a A8Eq.o AA16.o AA32.o AA8.o Alloc.o AofA8.o
CA8.o CmpKey.o DA16.o DA32.o DA8.o DAofA8.o DecKey.o Fill.o Flush.o
GenKey.o IncKey.o RA16.o RA32.o RA8.o RAofA8.o RC16.o RC32.o RC8.o
RHead.o RR.o RaA16.o RaA32.o RaA8.o RaAoA8.o Unwrap.o WA16.o WA32.o
WA8.o WAofA8.o WC16.o WC32.o WC8.o Whead.o Wrap.o
Wraphelp.o~ranlib .libs/libXdmcp.a
ar: Wraphelp.o~ranlib: No such file or directory
Inside the libtool script lines like these appear where a ~
amalgamates different lines to one:
old_archive_cmds="\$AR \$AR_FLAGS \$oldlib\$oldobjs\$old_deplibs~\
$RANLIB \$oldlib"
old_postinstall_cmds="chmod 644 \$oldlib~\$RANLIB \$oldlib"
archive_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC -dynamiclib \$allow_undefined_flag -o \
$lib \$libobjs \$deplibs \$compiler_flags -install_name \$rpath/\
$soname \$verstring~nmedit -s \$output_objdir/\${libname}-
symbols.expsym \${lib}"
module_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC \$allow_undefined_flag -o \$lib -
bundle \$libobjs \$deplibs\$compiler_flags~nmedit -s \$output_objdir/\
${libname}-symbols.expsym \${lib}"
old_archive_cmds="\$AR \$AR_FLAGS \$oldlib\$oldobjs\$old_deplibs~\
$RANLIB \$oldlib"
old_postinstall_cmds="chmod 644 \$oldlib~\$RANLIB \$oldlib"
archive_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC -dynamiclib -single_module \
$allow_undefined_flag -o \$lib \$libobjs \$deplibs \$compiler_flags -
install_name \$rpath/\$soname \$verstring~nmedit -s \$output_objdir/\$
{libname}-symbols.expsym \${lib}"
module_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC \$allow_undefined_flag -o \$lib -
bundle \$libobjs \$deplibs\$compiler_flags~nmedit -s \$output_objdir/\
${libname}-symbols.expsym \${lib}"
old_archive_cmds="\$AR \$AR_FLAGS \$oldlib\$oldobjs\$old_deplibs~\
$RANLIB \$oldlib"
old_postinstall_cmds="chmod 644 \$oldlib~\$RANLIB \$oldlib"
archive_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC -dynamiclib \$allow_undefined_flag -o \
$lib \$libobjs \$deplibs \$compiler_flags -install_name \$rpath/\
$soname \$verstring~nmedit -s \$output_objdir/\${libname}-
symbols.expsym \${lib}"
module_expsym_cmds="sed -e \\\"s,#.*,,\\\" -e \\\"s,^[ ]*,,\\\" -
e \\\"s,^\\\\(..*\\\\),_&,\\\" < \$export_symbols > \$output_objdir/\$
{libname}-symbols.expsym~\$CC \$allow_undefined_flag -o \$lib -
bundle \$libobjs \$deplibs\$compiler_flags~nmedit -s \$output_objdir/\
${libname}-symbols.expsym \${lib}"
These ~ also appear in aclocal.m4 when it's built from 'autoreconf -
fvi', libtool is created from the configure script. What can I do to
avoid the ~ in aclocal.m4 and libtool?
The tools I use in Mac OS X 10.4.8 are:
autoconf (GNU Autoconf) 2.60
autoheader (GNU Autoconf) 2.60
automake (GNU automake) 1.9.6
aclocal (GNU automake) 1.9.6
autopoint (GNU gettext-tools) 0.14.5
libtoolize (GNU libtool) 1.5.23a
GNU M4 1.4.5
--
Greetings
Pete
A lot of us are working harder than we want, at things we don't like
to do. Why? ...In order to afford the sort of existence we don't care
to live.
-- Bradford Angier
- Tilde problem when creating libtool,
Peter Dyballa <=