public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Kirkham <Robin.Kirkham@mlb.dmt.csiro.au>
To: egcs@cygnus.com
Subject: Re: Building 971008 cross m68k-coff on sparc-sun-solaris2.5.1 -- help!
Date: Wed, 15 Oct 1997 11:12:00 -0000	[thread overview]
Message-ID: <19971015153724.13868.qmail@ragnarok.mlb.dmt.csiro.au> (raw)
In-Reply-To: <9710151322.AA24749@kona.>

On Wed, 15 Oct 1997, Paul Koning wrote:

>  Robin> Would someone knowledgeable about the egcs cross-build
>  Robin> procedure please have a quick look at this---I can't even work
>  Robin> out which bit of the makefile is going wrong.
> 
>  Robin> The build fails while trying to make the subtarget
>  Robin> "stmp-f2c.h" in the Fortran run-time. It seems to have decided
>  Robin> that the xgcc it made does not work, yet it seemed to build
>  Robin> the libgcc libraries OK. I had the same error in building
>  Robin> egcs-970929.
> 
>  Robin> Is this a reasonable configuration?  Am I doing something else
>  Robin> wrong?  I also tried specifying LANGUAGES="c c++" to make
>  Robin> (with a fresh distribution) to avoid building f77, but it
>  Robin> seemed to make no difference.
> >...
> 
> I ran into this some time ago and proposed a patch (that was for the
> 0922 snapshot, but the relevant file is the same in the current
> snapshot).  Give it a try...  This is to gcc/f/Make-lang.in.
> ..

I applied Paul's patch and it solves the problem whereby LANGUAGES is not
honoured, at least in this configuration. So if I type make LANGUAGES="c c++"
the build completes sucessfully (by skipping f77 and objc) and the resulting
c compiler seems to work (at least on a quick test, not a proper testsuite).
So I think this patch should be accepted (and thanks, Paul).

However, if you don't skip f77, the build still fails in the same spot. 
It looks as if gcc/f/runtime/configure still believes the compiler does not
work (or invokes it incorrectly) and gives up. Is the f77 runtime actually
supported in m68k-coff configuration? (I don't actually need it).

There is a minor installation bug: it seems --program-prefix is not honoured,
and the compiler is installed as m68k-coff-g++ and so on (I asked for m68k-g++).
Further, gcc is not installed at all.

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

  reply	other threads:[~1997-10-15 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-14 22:48 Robin Kirkham
1997-10-15  7:41 ` Joel Sherrill
1997-10-15  8:25 ` Paul Koning
1997-10-15 11:12   ` Robin Kirkham [this message]
1997-10-15 14:33     ` Jim Wilson
1997-10-15 20:16       ` Robin Kirkham
1997-10-16  1:07   ` Jeffrey A Law
1997-10-15  8:53 ` 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=19971015153724.13868.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).