Dave Korn <dave.korn.cyg...@googlemail.com> wrote > Eric House wrote: > > Danny wrote: > >> Could you apply this patch to src/binutils/configure.ac : > >> [...] > >> +AC_CHECK_HEADERS(iconv.h) > >> [...] > >> and then run > >> autoreconf > >> in the src/binutils directory. > > > > eeho...@debian:~/src/cegcc-0.55/src/binutils$ autoreconf > > configure.ac:26: error: Please use exactly Autoconf 2.59 instead of 2.61. > > config/override.m4:24: _GCC_AUTOCONF_VERSION_CHECK is expanded from... > > configure.ac:26: the top level > > autom4te: /usr/bin/m4 failed with exit status: 1 > > aclocal: autom4te failed with exit status: 1 > > autoreconf: aclocal failed with exit status: 1 > > > > This is on Debian stable (lenny). I'll try building and installing > > 2.59 and see how that does. What system is cegcc normally built on > > that still has 2.59 installed? > > When just building gcc for normal use, you don't need to run autoconf or > automake, so it doesn't matter. It's only people doing actual development > work on gcc that involves patching the configure-related or Makefiles who ever > have to deal with this problem. For such purposes keeping a clean build of > autoconf-2.59 and automake-1.9.6 installed to a separate $prefix from their > regular autoconf/automake installations is a common trick.
And having installed that autoconf with, say, --prefix=$HOME/usr/local, I'd then run it like this: eeho...@debian:~/src/cegcc-0.55/src/binutils$ PATH=$HOME/bin:$PATH autoreconf --version autoreconf (GNU Autoconf) 2.59 ... eeho...@debian:~/src/cegcc-0.55/src/binutils$ PATH=$HOME/bin:$PATH autoreconf -v autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /home/eehouse/usr/local/bin/autoconf autoreconf: configure.ac: not using Autoheader autoreconf: configure.ac: not using Automake autoreconf: Leaving directory `.' This results in changes to the svn-controlled file "configure" in the same directory as my modified configure.ac, but code in child directories protected by #ifdef HAVE_ICONV_H is not getting compiled. I'm doing the best I can to force a clean build: nuking the contents of my build directory. Is there significance to the message "not using Autoheader"? Google isn't helpful searching for that message. As Danny noted, there was work ongoing in this particular area (binutils/winduni.c) at the time cegcc grabbed the trunk of binutils. Unfortunately, current mingw doesn't build on my Linux systems -- comments suggest this is a known problem and that they're waiting for gcc 4.4 dust to settle -- so I can't tell if this autoconf/iconv problem has been fixed on the trunk. Thanks, --Eric -- ****************************************************************************** * From the desktop of: Eric House, xwo...@eehouse.org * * Crosswords 4.2 for MS Smartphone and PocketPC is OUT: xwords.sf.net * ****************************************************************************** ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
