Problems with installation of cross-compiler

Chris Ross cross+gcc@distal.com
Fri Jan 31 06:14:00 GMT 2003


   Hello there.  I've tried a bunch of different configurations and 
configure options,
but I seem to keep coming upon the same problem.  Hopefully someone here
can tell me if this is a bug in the build/install procedure (gcc 
3.2.1), or if there's
something I'm doing wrong...

   I've been working with gcc 3.2.1, building for a system I've just 
added support
for.  (m68k-bsdos).  I had previous built binutils with:

...../configure --prefix=/usr/local/m68k --target=m68k-bsdos

   And then would build and install, and it would work fine.  I would 
then configure
gcc as:

   ..../configure --prefix=/usr/local/m68k --target=m68k-bsdos

   And sans some build problems, it would also build working binaries, 
that it
was able to install.  This led to a whole bunch of binaries in 
/usr/local/m68k/bin
named:

/usr/local/m68k/bin/m68k-bsdos-addr2line
/usr/local/m68k/bin/m68k-bsdos-ar
/usr/local/m68k/bin/m68k-bsdos-as

   etc.  That was fine.  But, I later decided I'd rather have "arm68k" 
"asm68k", et al.
So, I rebuilt everything with the same configure lines as above, and 
added
--program-suffix=m68k to each of them.  This works just fine for 
binutils, and
all of the binaries are installed as you'd expect.  /usr/local/m68k/bin/
{addr2linem68k,arm68k,asm68k,...}.

   But, after building gcc (gmake cross), and installing it, (gmake 
install-cross),
/usr/local/m68k/bin contained quite a number of m68k-bsdos-* binaries.
The ls -l of that directory is enclosed here:

# ls -l /usr/local/m68k/bin/
total 34448
-rwxr-xr-x  1 root  wheel  2523226 Jan 31 00:36 addr2linem68k
-rwxr-xr-x  2 root  wheel  2598449 Jan 31 00:36 arm68k
-rwxr-xr-x  2 root  wheel  4523888 Jan 31 00:36 asm68k
-rwxr-xr-x  1 root  wheel   153739 Jan 31 00:36 c++filtm68k
-rwxr-xr-x  1 root  wheel    15576 Jan 31 01:11 gccbugm68k
-rwxr-xr-x  1 root  wheel   161014 Jan 31 01:12 grepjarm68k
-rwxr-xr-x  1 root  wheel   178828 Jan 31 01:12 jarm68k
-rwxr-xr-x  2 root  wheel  3432803 Jan 31 00:36 ldm68k
-rwxr-xr-x  2 root  wheel   209401 Jan 31 01:11 m68k-bsdos-c++
-rwxr-xr-x  1 root  wheel   152154 Jan 31 01:11 m68k-bsdos-c++filt
-rwxr-xr-x  1 root  wheel   209660 Jan 31 01:11 m68k-bsdos-cpp
-rwxr-xr-x  2 root  wheel   209401 Jan 31 01:11 m68k-bsdos-g++
-rwxr-xr-x  1 root  wheel   206765 Jan 31 01:12 m68k-bsdos-gcc
-rwxr-xr-x  1 root  wheel   215247 Jan 31 01:11 m68k-bsdos-gcj
-rwxr-xr-x  2 root  wheel  2568947 Jan 31 00:36 nmm68k
-rwxr-xr-x  1 root  wheel  3174573 Jan 31 00:36 objcopym68k
-rwxr-xr-x  1 root  wheel  3356816 Jan 31 00:36 objdumpm68k
-rwxr-xr-x  2 root  wheel  2598448 Jan 31 00:36 ranlibm68k
-rwxr-xr-x  1 root  wheel   569237 Jan 31 00:36 readelfm68k
-rwxr-xr-x  1 root  wheel  2406172 Jan 31 00:36 sizem68k
-rwxr-xr-x  1 root  wheel  2368970 Jan 31 00:36 stringsm68k
-rwxr-xr-x  2 root  wheel  3174572 Jan 31 00:36 stripm68k
#

   Does anyone know why this is?  Why do some of the gcc-3.2.1 binaries
get named as I've asked them to, but others have the $target- prefix 
style
name?  Have I missed a configure option somewhere?

   Thanks.  I appreciate your time in looking into this.  Any pointers 
to other
places for GCC cross-compiler issues would also be appreciated.



More information about the Gcc-help mailing list