problem building binutils host=linux target=m68k-coff

Brian Cuthie
Wed Feb 4 18:22:00 GMT 1998

I've seen the same kinds of things.  The problem is likely that you have
to do a 'make all' before the 'make install'.  Incredibly, some of the
makefiles will try to install things that haven't been built.


>-----Original Message-----
>From:	Robert J. Brown []
>Sent:	Wednesday, February 04, 1998 5:26 PM
>Subject:	problem building binutils host=linux target=m68k-coff
>I ftp-ed the binutils-2.7.tar.gz from, and
>binutils-2.6-obj-coff.patch from, unpacked the tar and
>applied the patches as directed by the FAQ from
>/, and did the make all.  This
>worked fine, but when I did the make install, I got the following:
>    make[2]: Entering directory `/away/zen/gnu/build-binutils/libiberty'
>    make[2]: Leaving directory `/away/zen/gnu/build-binutils/libiberty'
>    /away/zen/gnu/binutils-2.7/ -c -m 644 libiberty.a
>    ( cd m68k/lib ; ranlib m68k/lib/libiberty.a.n )
>    ranlib: m68k/lib/libiberty.a.n: No such file or directory
>    make[1]: *** [install_to_libdir] Error 9
>    make[1]: Leaving directory `/away/zen/gnu/build-binutils/libiberty'
>    make: *** [install-libiberty] Error 2
>The cd on the 4th line looks like it is trying to cd to the m68k/lib
>directory, but then tries to run ranlib on m68k/lib/libiberty.a.n,
>when it looks to me like it should have been just libiberty.a.n, since 
>it already did the cd m68k/lib.  
>Am I just dense, or is the make install scrogged?
>Also, the FAQ seems to refer to versions older than current for the
>gnu tolls binutils and gcc.  Should I be using the latest versions, or 
>is there a real reason to stay with the older ones?
>--------  "And there came a writing to him from Elijah"  [2Ch 21:12]
>Robert Jay Brown III 1 847
>Elijah Laboratories Inc.;  37 South Greenwood Avenue;  Palatine, IL
>-----  M o d e l i n g   t h e   M e t h o d s   o f   t h e   M i n d

More information about the crossgcc mailing list