RE: m68k-elf-ar setup problem?

["Ralf Doewich" <ralf dot doewich at cybercube dot com>]

> -----Original Message-----
> From: John M. Mills [mailto:jmills@tga.com]
> Sent: Fri, 7-April-2000 09:19
> To: Ralf Doewich
> Subject: Re: m68k-elf-ar setup problem?
>
> Assuming you've configured, built and installed the cross-binutils to the
> same combination of --prefix and --exec-prefix, this commonly means the
> new cross-assembler and its relatives weren't placed on your path.
>
> On Fri, 7 Apr 2000, Ralf Doewich wrote:
>
> > target=m68k-elf
> > prefix=/usr/local
> > ../bu0406/configure --target=$target --prefix=$prefix -v
> --exec-prefix=$prefix
> > [...stuff deleted...]
> > make all install
> > [...stuff deleted...]
> > ../gcc-2.95.2/configure --target=$target --enable-languages=c,c++
> --prefix=$pref
> > ix --exec-prefix=$prefix
> > [...stuff deleted...]
>
>
> >>-->> try here (given in syntax for 'bash'):
> % export PATH=$prefix/bin:$PATH
>
>
> > make all install
> > [...stuff deleted...]
> > cp ../../gcc-2.95.2/gcc/config/m68k/lb1sf68.asm libgcc1.S
> > for name in _mulsi3 _udivsi3 _divsi3 _umodsi3 _modsi3 _double
> > _float _floatex
> > _eqdf2 _nedf2 _gtdf2 _gedf2 _ltdf2 _ledf2 _eqsf2 _nesf2 _gtsf2 _gesf2 _ltsf2
> > _lesf2; \
> > do \
> >   echo ${name}; \
> > /usr/build-gcc/gcc/xgcc -B/usr/build-gcc/gcc/
> > -B/usr/local/m68k-elf/bin/ -I/usr/
> > local/m68k-elf/include -O2  -DCROSS_COMPILE -DIN_GCC     -g -O2
> > -I./include -g1
> >  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. -I../../gcc-2.95.2/gcc
> > -I../../gcc-
> > 2.95.2/gcc/config -I../../gcc-2.95.2/gcc/../include -c -DL${name}
> > libgcc1.S; \
> >   if [ $? -eq 0 ] ; then true; else exit 1; fi; \
> >   mv libgcc1.o ${name}.o; \
> >   m68k-elf-ar rc tmplibgcc1.a ${name}.o; \
> >   rm -f ${name}.o; \
> > done
> > _mulsi3
> > /bin/sh: m68k-elf-ar: command not found
> > _udivsi3
> > /bin/sh: m68k-elf-ar: command not found
> > [...stuff deleted...]
> > rm -f libgcc1.S
> > mv tmplibgcc1.a libgcc1-asm.a
> > mv: tmplibgcc1.a: No such file or directory
> > make[1]: *** [libgcc1-asm.a] Error 1
> > make[1]: Leaving directory `/usr/build-gcc/gcc'
> > make: *** [all-gcc] Error 2
>
> Hope that was the issue.

thanks, John! It cured that problem and left me immediately with another one. In
the next step, while trying to compile the libgcc2.c, I got error messages
indicating that some *.h files(unistd.h and stdlib.h) could not be found. I
fixed that by using a different configure setup:

../gcc-2.95.2/configure --target=$target --enable-languages=c,c++ --with-headers
=$hidir --prefix=$prefix --exec-prefix=$prefix

using hidir=../newlib-1.8.2/newlib/libc/include. This seemed to have fixed that
but now I get into this:

make[2]: Entering directory `/usr/build-gcc/m68k-elf/libiberty'
make[2]: *** No targets specified and no makefile found.  Stop.
make[2]: Leaving directory `/usr/build-gcc/m68k-elf/libiberty'
make[1]: *** [../libiberty/libiberty.a] Error 2
make[1]: Leaving directory `/usr/build-gcc/m68k-elf/libstdc++'
make: *** [all-target-libstdc++] Error 2
BASH.EXE-2.02$

Where do I find a quick overview explaining the use an scope of the different
libraries. After building the GCC, I intended to build the netlib library to
which I have to apply some m68k patches. How does libiberty fit in?

Ralf.
ralf.doewich@cybercube.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com