From: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
To: egcs@cygnus.com
Subject: Re: m68k-unknown-coff cross failure
Date: Mon, 01 Dec 1997 18:55:00 -0000 [thread overview]
Message-ID: <19971202025445.4672.qmail@ragnarok.mlb.dmt.csiro.au> (raw)
In-Reply-To: <E0xccUx-0000Th-00@data.ctd.comsat.com>
On Mon, 01 Dec 1997, Neal Becker wrote:
> I just tried:
> ../../egcs-971127//configure --target=m68k-unknown-coff
> --prefix=/usr/local/m68k
> on hppa1.1-hp-hpux9 host.
> PATH=/usr/local/m68k/bin:$PATH make
> [....]
> rm -f g77-cross
> cp g77 g77-cross
> rm -f stmp-f2c.h
> ...
You are trying to build the Fortran runtime which is not supported for
the cross-compiler situation. You can avoid this by making just C and
C++ using:
make LANGUAGES="c gcov c++" all install
The approved way is to use
make cross
which does much the same thing. However, when you come to install the
cross-compiler, "make install" or "make cross install" will still try and
build the Fortran runtime, since target "install" depends on "all" (or
equivalent). So I just use the first method.
Jeff, maybe this minor problem (and a better fix, if there is one) could
be mentioned in the new ECGS install document/FAQ?
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 prev parent reply other threads:[~1997-12-01 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 12:31 Neal Becker
1997-12-01 17:20 ` Jeffrey A Law
1997-12-02 5:52 ` Neal Becker
1997-12-02 9:23 ` Jeffrey A Law
1997-12-03 5:46 ` Neal Becker
1997-12-05 8:53 ` Jeffrey A Law
1997-12-05 11:48 ` Neal Becker
1997-12-01 18:55 ` Robin Kirkham [this message]
1997-12-02 9:56 ` 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=19971202025445.4672.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).