From: Stefan Petters <Stefan.Petters@lpr.e-technik.tu-muenchen.de>
To: egcs@cygnus.com
Subject: configuration error
Date: Tue, 12 May 1998 15:25:00 -0000 [thread overview]
Message-ID: <199805121754.TAA19456@fozzie.lpr.e-technik.tu-muenchen.de> (raw)
Hi,
I'm new to this list, but have looked into the archives without finding
a solution to my problem. I'm trying to make cross development toolset
for m68k-coff (no OS). I made several before (gcc-2.7.2 and binutils-2.6
and 2.7) but had not these problems.
I followed the guidlines in the faq and made my binutils this way:
cd /somewhere/
gtar -xvzf /pub/.../binutils-2.8.1.tgz
mkdir binutils
cd binutils
../binutils-2.8.1/configure --target=m68k-coff --with-gnu-as \
--with-gnu-ld --with-targets=all \
--prefix=/usr/local/m68k-coff/binutils-2.8.1
now I have various symlinks pointing to my cross-binaries which are
accessable via my PATH--variable:
m68k-coff-{as|ar|...}
{as|ar|...}-new
Now I have tried to make egcs
cd /somewhere/
gtar -xvzf /pub/.../egcs-1.0.2.tar.gz
mkdir egcs
cd egcs
../egcs-1.0.2/configure --target=m68k-coff --with-gnu-as --with-gnu-ld
I have tried some prefix values as well, but wanted to keep this
before I started configure new I cleaned up by making ``rm -rf *''
and each time I started a new make I made ``make clean'' before.
BTW: Yes my make is GNU--Make (Linux--box :)
now I tried
make
this left me
----------------------------SNIP--------------------------
gcc -DCROSS_COMPILE -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I.
-I../../egcs-1.0.2/gcc -I../../egcs-1.0.2/gcc/config \
-DTARGET_MACHINE=\"m68k-coff\" \
-c `echo ../../egcs-1.0.2/gcc/collect2.c | sed 's,^\./,,'`
as: unrecognized option `-c68020'
make[1]: *** [collect2.o] Error 1
make[1]: Leaving directory `/a/batian/dist2/prakt/m68k-coff/tools/egcs/gcc'
make: *** [all-gcc] Error 2
----------------------------SNAP--------------------------
the I tried something out of the FAQ
make cross
this is what I got last:
-----------------------------SNIP-------------------------
/DIST/prakt/m68k-coff/tools/egcs/gcc/xgcc
-B/DIST/prakt/m68k-coff/tools/egcs/gcc/ -O2 -DCROSS_COMPILE -DIN_GCC
-g -O2 -I./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-fexceptions -m5200 -I. -I../../egcs-1.0.2/gcc
-I../../egcs-1.0.2/gcc/config -c -DL${name} \
../../egcs-1.0.2/gcc/libgcc2.c -o ${name}.o; \
if [ $? -eq 0 ] ; then true; else exit 1; fi; \
m68k-coff-ar rc tmplibgcc2.a ${name}.o; \
rm -f ${name}.o; \
done
_muldi3
[... about 40 lines of these]
_new_handler
_op_delete
_bb
/var/tmp/cca30883.s: Assembler messages:
/var/tmp/cca30883.s:2106: Error: operands mismatch -- statement `move.b
#0,%a1' ignored
/var/tmp/cca30883.s:2107: Error: operands mismatch -- statement `move.b
%a1,(%a3,%a0.l)' ignored
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory `/a/batian/dist2/prakt/m68k-coff/tools/egcs/gcc'
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory `/a/batian/dist2/prakt/m68k-coff/tools/egcs/gcc'
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory `/a/batian/dist2/prakt/m68k-coff/tools/egcs/gcc'
make: *** [cross] Error 2
-----------------------------SNAP-------------------------
I think it's a pilot error, so this goes to egcs instead of egcs-bugs.
Is anyone there knowing what's going wrong?
Thanks in advance.
Regards,
Stefan.
--
----------------------------------------------------------------------
Stefan M. Petters Laboratory for Process Control and Realtime Systems -ooo
Arcisstr. 21 Technische Universitaet Muenchen --oooo
80290 Muenchen Tel: ++49/89-2892-3556 Fax: ++49/89-2892-3555 ----oo
Germany EMail: petters@ei.tum.de ---o
----------------------------------------------------------------------
next reply other threads:[~1998-05-12 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-12 15:25 Stefan Petters [this message]
1998-05-13 16:55 ` Philippe De Muyter
1998-05-18 2:09 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199805121754.TAA19456@fozzie.lpr.e-technik.tu-muenchen.de \
--to=stefan.petters@lpr.e-technik.tu-muenchen.de \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).