From: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
To: egcs@cygnus.com
Subject: Building 971008 cross m68k-coff on sparc-sun-solaris2.5.1
Date: Fri, 10 Oct 1997 08:51:00 -0000 [thread overview]
Message-ID: <19971010081312.12799.qmail@ragnarok.mlb.dmt.csiro.au> (raw)
The build fails while trying to make the subtarget "stmp-f2c.h" in the Fortran
run-time. I had the same problem in building 970929.
Is this a reasonable configuration? Am I doing something else wrong? I also
tried specifying LANGUAGES="c c++" to make to avoid building f77, but it
didn't help.
My procedure and results were as follows:
% gtar xfz egcs-971008.tar.gz
% cd egcs-971008
% ./configure --target=m68k-coff --with-gnu-as --with-gnu-ld --prefix=/opt/embedded --program-prefix=m68k- -verbose
Configuring for a sparc-sun-solaris2.5.1 host.
... much deleted
% make
... much deleted (builds libgcc ok, apparently)
...
gcc -c -DCROSS_COMPILE -DIN_GCC -DSVR4 -g -O2 -DHAVE_CONFIG_H -I. -I. -I./config ./cp/g++spec.c
gcc -DCROSS_COMPILE -DIN_GCC -DSVR4 -g -O2 -DHAVE_CONFIG_H -o g++ g++.o g++spec.o version.o \
choose-temp.o pexecute.o obstack.o ` case "gcc" in "cc") echo "alloca.o" ;; esac `
rm -f g++-cross
cp g++ g++-cross
rm -f cxxmain.c
ln -s ./cplus-dem.c cxxmain.c
gcc -c -DMAIN -DCROSS_COMPILE -DIN_GCC -DSVR4 -g -O2 -DHAVE_CONFIG_H -I. -I. -I./config \
-DVERSION=\"egcs-2.90.12\" cxxmain.c
rm -f cxxmain.c
gcc -DCROSS_COMPILE -DIN_GCC -DSVR4 -g -O2 -DHAVE_CONFIG_H obstack.o ` case "gcc" in "cc") echo "alloca.o" ;; esac ` -o c++filt \
cxxmain.o underscore.o getopt.o getopt1.o
case 'c proto gcov c++ f77 objc' in \
*f77*) \
gcc -DCROSS_COMPILE -DIN_GCC -DSVR4 -g -O2 -DHAVE_CONFIG_H -I. -I. -I./config \
-DGCC_NAME=\"`t='-e s,^,m68k-coff-,'; echo gcc | sed $t`\" \
-o g77-cross ./f/g77.c ./f/version.c obstack.o ` case "gcc" in "cc") echo "alloca.o" ;; esac ` ;; \
esac
rm -f stmp-f2c.h
top=`pwd`; \
src=`cd .; pwd`; \
cd f/runtime; \
CC="`case '/opt/embedded/src/egcs-971008/gcc/xgcc -B/opt/embedded/src/egcs-971008/gcc/' in \
'./xgcc -B./') echo ${top}/xgcc -B${top}/;; \
*) echo '/opt/embedded/src/egcs-971008/gcc/xgcc -B/opt/embedded/src/egcs-971008/gcc/';; esac`" \
G_SITE=/dev/null /bin/sh \
${src}/f/runtime/configure --srcdir=${src}/f/runtime
loading site script /dev/null
creating cache ./config.cache
checking for gcc... /opt/embedded/src/egcs-971008/gcc/xgcc -B/opt/embedded/src/egcs-971008/gcc/
checking whether the C compiler (/opt/embedded/src/egcs-971008/gcc/xgcc -B/opt/embedded/src/egcs-971008/gcc/ -g -O2 ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
gmake[1]: *** [stmp-f2c.h] Error 1
gmake[1]: Leaving directory `/opt/embedded/src/egcs-971008/gcc'
gmake: *** [all-gcc] Error 2
Thanks,
Robin Kirkham CSIRO Manufacturing Science and Technology
Project Engineer Locked Bag 9, Preston 3072, Australia
robin.kirkham@mlb.dmt.csiro.au Phone: +61 3 9662-7756 Fax: +61 3 9662-7851
next reply other threads:[~1997-10-10 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-10 8:51 Robin Kirkham [this message]
1997-10-16 1:07 ` Jeffrey A Law
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=19971010081312.12799.qmail@ragnarok.mlb.dmt.csiro.au \
--to=robin.kirkham@mlb.dmt.csiro.au \
--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).