public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neal Becker <neal@ctd.comsat.com>
To: egcs@cygnus.com
Subject: egcs1.0.2 + libg++ cross build failure
Date: Tue, 31 Mar 1998 05:29:00 -0000	[thread overview]
Message-ID: <E0yK16Y-0005gD-00@spock.ctd.comsat.com> (raw)

I am trying to build egcs-1.0.2 + libg++-2.8.1 patch as cross with
host i686-pc-linux-gnu target m68k-unknown-coff.

I am building with newlib-1.8.0.

Problem 1) Headers aren't found.  Yes I've read the FAQ.  Headers
can't possibly be found, because you have to install the compiler
first, then you can install newlib.  My solution: I added
--with-headers=<path_to_newlib>/newlib/libc/include.  *Luckily* the
needed headers are all in this directory.

Problem 2) Configuring in m68k-unknown-coff/librx
creating cache ./config.cache
checking for gcc... /usr/local/src/m68k/egcs-1.0.2/gcc/xgcc -B/usr/local/src/m68k/egcs-1.0.2/gcc/
checking whether the C compiler (/usr/local/src/m68k/egcs-1.0.2/gcc/xgcc -B/usr/local/src/m68k/egcs-1.0.2/gcc/ -g -O2 ) works... no
configure: error: installation or configuration problem: C compiler
cannot create executables.

My solution: Go ahead and make -k install LANGUAGES="c c++".  Then
build and install newlib.  Then go back and build in egcs+libg++ again 
(now that crt0 is installed this last error will hopefully go away).


             reply	other threads:[~1998-03-31  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-31  5:29 Neal Becker [this message]
1998-04-01 17:05 ` Jim Wilson
1998-04-02  8:32   ` David Edelsohn
1998-04-03 21:52     ` Jim Wilson
1998-04-02  3:41 ` Joel Sherrill

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=E0yK16Y-0005gD-00@spock.ctd.comsat.com \
    --to=neal@ctd.comsat.com \
    --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).