RE: Final(?) patch to update libtool in GCC and src trees

Dave Korn
2007-04-12T10:42:07Z

On 11 April 2007 22:41, Christopher Faylor wrote:

> On Wed, Apr 11, 2007 at 12:18:56PM +0200, Paolo Bonzini wrote:
>> Dave Korn wrote:
>>> On 11 April 2007 10:25, Paolo Bonzini wrote:
>>>
>>>>> That would be the freshly regenerated one:
>>>>>
>>>>> /usr/build/src-winsup/newlib $ head -1 aclocal.m4
>>>>> # generated automatically by aclocal 1.9.6 -*- Autoconf -*- Can you
>>>>> please attach it?
>>>
>>> Cc list trimmed a bit :-)
>>
>> aclocal used your 1.5.x libtool, instead of the new GCC libtool.
>>
>> You have to regenerate it with
>>
>> aclocal -I ../config -I .. -I.
>>
>> or something like that.
>
> It's a minor nit but doesn't the "-I .." rather than "-I.." bother anyone?
> It just seems inconsistent.
>
> cgf

Alas, it didn't help; the same problem recurred. The only difference in the
newly-generated-but-still-faulty aclocal.m4 as compared to my previous attempt
was:

/usr/build/src-winsup/newlib $ diff -pu aclocal.m4.save aclocal.m4
--- aclocal.m4.save 2007-04-11 10:58:44.830368700 +0100
+++ aclocal.m4 2007-04-11 16:04:18.826887600 +0100
@@ -6953,27 +6953,6 @@ AC_DEFUN([AM_PROG_INSTALL_SH],
install_sh=${install_sh-"$am_aux_dir/install-sh"}
AC_SUBST(install_sh)])

-# Copyright (C) 2003, 2005 Free Software Foundation, Inc.
-#
-# This file is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# serial 2
-
-# Check whether the underlying file-system supports filenames
-# with a leading dot. For instance MS-DOS doesn't.
-AC_DEFUN([AM_SET_LEADING_DOT],
-[rm -rf .tst 2>/dev/null
-mkdir .tst 2>/dev/null
-if test -d .tst; then
- am__leading_dot=.
-else
- am__leading_dot=_
-fi
-rmdir .tst 2>/dev/null
-AC_SUBST([am__leading_dot])])
-
# Add --enable-maintainer-mode option to configure. -*- Autoconf -*-
# From Jim Meyering

@@ -7362,4 +7341,10 @@ AC_SUBST([am__tar])
AC_SUBST([am__untar])
]) # _AM_PROG_TAR

+m4_include([../libtool.m4])
+m4_include([../ltoptions.m4])
+m4_include([../ltsugar.m4])
+m4_include([../ltversion.m4])
+m4_include([../config/depstand.m4])
+m4_include([../config/lead-dot.m4])
m4_include([acinclude.m4])

Leading to the same issues at configure time:

configure:3737: checking for a BSD-compatible install
configure:3793: result: /usr/bin/install -c
configure:3808: checking whether to enable maintainer-specific portions of
Makefiles
configure:3817: result: no
configure:21892: checking for .preinit_array/.init_array/.fini_array support
configure:21905: gcc -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup
-L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/cygwin
-L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/w32api/lib -isystem
/usr/build/src-winsup/winsup/include -isystem
/usr/build/src-winsup/winsup/cygwin/include -isystem
/usr/build/src-winsup/winsup/w32api/include
-B/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/ -isystem
/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/targ-include -isystem
/usr/build/src-winsup/newlib/libc/include
-I/usr/build/src-winsup/winsup/cygwin/include -o conftest conftest.c
-static -nostartfiles -nostdlib 1>&5
configure:21908: $? = 0
configure:21921: result: no
configure:21931: checking for array aliasing support
configure:21942: gcc -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup
-L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/cygwin
-L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/w32api/lib -isystem
/usr/build/src-winsup/winsup/include -isystem
/usr/build/src-winsup/winsup/cygwin/include -isystem
/usr/build/src-winsup/winsup/w32api/include
-B/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/ -isystem
/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/targ-include -isystem
/usr/build/src-winsup/newlib/libc/include
-I/usr/build/src-winsup/winsup/cygwin/include -c conftest.c
1>&5
conftest.c:1: warning: excess elements in scalar initializer
conftest.c:1: warning: (near initialization for `x3')
conftest.c:1: warning: excess elements in scalar initializer
conftest.c:1: warning: (near initialization for `x3')
configure:21945: $? = 0
configure:21954: result: yes
configure:22030: updating cache ./config.cache
configure:22141: error: conditional "am__fastdepCXX" was never defined.
Usually this means the macro was only invoked conditionally.

Charles W. made some suggestions offlist which I'll try later, but I need to
concentrate on my day job right now :)

cheers,
DaveK
--
Can't think of a witty .sigline today....