public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Currie <bcurrie@tssc.co.nz>
To: John Breen <jab3@hotmail.com>
Cc: egcs@cygnus.com
Subject: Re: Getting closer (was Re: cross-compiler build: can't find stdio.h)
Date: Thu, 24 Sep 1998 19:32:00 -0000	[thread overview]
Message-ID: <360B00C4.7C8C@tssc.co.nz> (raw)
In-Reply-To: <19980924135128.1788.qmail@hotmail.com>

John Breen wrote:
> So you were close: it's crt0.o that's missing.  Obviously I don't have a
> crt0.o, since I don't have a compiler yet (to answer your previous
> question, this is for an in-house developed embedded system; all I have
> for headers and libs is what comes in egcs or newlib).

Doh! forgot about crt0.o.  That was my first problem (libc.a came next,
I think), but I provided my own as the mtos crt0.o was very suboptimal.

> I could copy over the m68k crt0.S from newlib and see if I can assemble
> it myself with what's there, but should I really have to do things like
> that?

No, get the cross-FAQ (look in the egcs faq under cross compiling for
it's location).  It will tell you how to do a full tool-chain (including
libs) build.  Here's the relevant section (don't worry about the version
numbers and I recomment grabbing the dirs common between binutils and
egcs from egcs):

---

3.2 One Pass Installation

Is there an easier way?  Yes!
If you study the top-level Makefile that comes with binutils-2.7,
newlib-1.7.1, or gdb-4.16, you'll see that they're all quite similar
(not surprising since they're essentially the same file).

You'll also discover that it is capable of building and installing the
entire toolchain in one pass.  The catch is that is assumes a directory
layout different than what would normally appear when you unpack the
sources.

You will need to apply the Cygnus crossgcc-gcc-2.7.2.1.patch.

What we now need to do is turn this directory layout

./binutils-2.7/
               bfd/
               binutils/
               config/
               gas/
               include/
               ld/
               libiberty/
               opcodes/
               texinfo/
./gcc-2.7.2.1/
./newlib-1.7.1/
               config/
               libgloss/
               newlib/
               texinfo/

into

./src/
      bfd/
      binutils/
      config/
      gas/
      gcc/
      include/
      ld/
      libgloss/
      libiberty/
      newlib/
      opcodes/
      texinfo/

-- 
Leave others their otherness

  reply	other threads:[~1998-09-24 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-24 11:27 John Breen
1998-09-24 19:32 ` Bill Currie [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-09-23 14:48 John Breen
1998-09-23 20:53 ` Bill Currie

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=360B00C4.7C8C@tssc.co.nz \
    --to=bcurrie@tssc.co.nz \
    --cc=egcs@cygnus.com \
    --cc=jab3@hotmail.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).