From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Wilson To: Peter Barada Cc: egcs@cygnus.com, crosgcc@cygnus.com Subject: Re: Trying to build cross tool chain using egcs-980302 Date: Mon, 16 Mar 1998 20:25:00 -0000 Message-id: <199803162246.OAA13975@rtl.cygnus.com> References: <199803132304.SAA17195@miacomet.wavemark.com> X-SW-Source: 1998-03/msg00555.html As yet, we have not had time to fix all of the cross-compiler issues in EGCS, so it isn't as easy to build a cross compiler as it should be. There are a number of different problems that you ran into, but most of them seem to be version conflicts. When tyring to build for the RH-4.2, config.guess in egcs-980302 declares the system to be a i686-pc-linux-gnulibc1, and gdb-4.16 declares that an unsupported configuration: gdb-4.16 is two years old. Since then, there was a change to the configuration naming scheme which happens to affect your host. This was part of the support needed to handle glibc2 linux systems. You will not be able to use the same host name with gdb-4.16 and the current egcs sources. This will not be a problem with gdb-4.17 which is expected soon. I think there is no real advantage to trying to build gdb in the same source tree as the rest of the stuff. Just build it separately. $ ../gdb-4.16/configure --host=i686-unkown-linux Created "Makefile" in /usr/bigdisk/pbarada/src/gdb/objdir ../../gdb-4.16/bfd/../ltconfig: ../../gdb-4.16/bfd/../ltconfig: No such file or directory configure: error: libtool configure failed Configure in /usr/bigdisk/pbarada/src/gdb/objdir/bfd failed, exiting. I am guessing that you use the binutils copy of bfd. This was relatively recently modified to use libtool. libtool requires some scripts in the toplevel directory which are not distributed with EGCS. Just copy them from the binutils toplevel directory into the toplevel EGCS directory. I think that there are only two scripts involved here, both of which start with lt. Jim