Re: cross-tools, m68k build, libgcc2 build throws bad assembler code

Doing it with the TARGET=mvme68k yileds the same results (failure) at the same point in the build as seen below: - ./xgcc -B./ -I/usr/cross/mvme68k/usr/include -O2 -I/usr/src/gnu/usr.bin/gcc/../../lib/libiberty/include -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -

Re: cross-tools, m68k build, libgcc2 build throws bad assembler code

Randy Lewis wrote: > While building 'cross-tools' on i386 host, OpenBSD 3.7 (with current > patches.) > Environment var: TARGET=m68k > From /usr/src > Command: make cross-tools (TARGET=m68k already defined in ENV ) > ... > Goes well for m68k build (always) until it gets into the

cross-tools, m68k build, libgcc2 build throws bad assembler code

While building 'cross-tools' on i386 host, OpenBSD 3.7 (with current patches.) Environment var: TARGET=m68k From /usr/src Command: make cross-tools (TARGET=m68k already defined in ENV ) ... Goes well for m68k build (always) until it gets into the 'libgcc2' floating point func