From: Jan Reimers <janr@molienergy.com>
To: 'Mack Lobell' <macklobell@hotmail.com>, dje@watson.ibm.com
Cc: gcc@gcc.gnu.org
Subject: RE: 3.0.4 cross build fails on i686-pc-cygwin.
Date: Fri, 22 Feb 2002 13:00:00 -0000 [thread overview]
Message-ID: <3002691ACB39D51180FC004854506BCA22CEBC@mailserv.molienergy.bc.ca> (raw)
Tell gcc where the newlib headers are, build cross-gcc, then use cross-gcc
to make the lib.
> -----Original Message-----
> From: Mack Lobell [mailto:macklobell@hotmail.com]
> Sent: Friday, February 22, 2002 10:34 AM
> To: dje@watson.ibm.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
>
>
> How do i do that?
>
> The last time i built a cross compiler i didn't have to add
> anything to the
> build process.
> I have read a few how-tos on how to build a cross compiler
> and none of them
> give any examples, so i appreciate any help i can get.
>
> I'm planing to use newlib instead of glibc. But to build
> newlib i need a
> cross compiler, right?
>
> Regards.
>
>
> >From: David Edelsohn <dje@watson.ibm.com>
> >To: "Mack Lobell" <macklobell@hotmail.com>
> >CC: gcc@gcc.gnu.org
> >Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> >Date: Fri, 22 Feb 2002 12:52:09 -0500
> >
> > You need to supply the cross-target headers and tell
> GCC where to
> >find them. This can be glibc or libgloss or your own, but
> it needs to be
> >something.
> >
> >David
>
>
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
next reply other threads:[~2002-02-22 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 13:00 Jan Reimers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 14:50 Mack Lobell
2002-02-22 10:59 Mack Lobell
2002-02-22 11:02 ` Stephano Mariani
2002-02-22 9:52 Mack Lobell
2002-02-22 9:53 ` Stephano Mariani
2002-02-22 9:55 ` David Edelsohn
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=3002691ACB39D51180FC004854506BCA22CEBC@mailserv.molienergy.bc.ca \
--to=janr@molienergy.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=macklobell@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).