From: Kai Ruottu <kai.ruottu@luukku.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: karuottu@freenet.hut.fi, munroe@csworks.com,
crossgcc@sourceware.cygnus.com
Subject: Re: Trying to build a cross compiler from linux to netbsd...
Date: Wed, 03 Jan 2001 14:21:00 -0000 [thread overview]
Message-ID: <3A53A68E.AE42C58B@luukku.com> (raw)
In-Reply-To: <oritnw6cay.fsf@guarana.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
>
> On Jan 3, 2001, Kai Ruottu <kai.ruottu@luukku.com> wrote:
>
> > Doing like Sinuhe the Egyptian, I would ask "Why?"
>
> GCC needs the target headers to be able to compile anything for the
> target. It's not just about fixing, it's about having declarations,
> macro definitions, etc, that are compatible with the actual C library
> of the target system.
But why they must now be preinstalled into the 'sys-include', not into
the 'include' as done during the last ten or so years? Are all the 1000
or more cross-compilers I have built during all these years used the wrong
directory for the target headers?
Cheers, Kai
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Kai Ruottu <kai.ruottu@luukku.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: karuottu@freenet.hut.fi, munroe@csworks.com,
crossgcc@sourceware.cygnus.com
Subject: Re: Trying to build a cross compiler from linux to netbsd...
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <3A53A68E.AE42C58B@luukku.com> (raw)
Message-ID: <20010401000000.oY40jw_LoeF4i77rtNWgY-sIkU875ylaHkjtKJbWZB8@z> (raw)
In-Reply-To: <oritnw6cay.fsf@guarana.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
>
> On Jan 3, 2001, Kai Ruottu <kai.ruottu@luukku.com> wrote:
>
> > Doing like Sinuhe the Egyptian, I would ask "Why?"
>
> GCC needs the target headers to be able to compile anything for the
> target. It's not just about fixing, it's about having declarations,
> macro definitions, etc, that are compatible with the actual C library
> of the target system.
But why they must now be preinstalled into the 'sys-include', not into
the 'include' as done during the last ten or so years? Are all the 1000
or more cross-compilers I have built during all these years used the wrong
directory for the target headers?
Cheers, Kai
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2001-01-03 14:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 18:52 Dick Munroe
2001-01-02 18:57 ` Rod Stewart
2001-04-01 0:00 ` Rod Stewart
2001-01-02 19:37 ` Alexandre Oliva
2001-01-03 4:32 ` Kai Ruottu
2001-01-03 4:38 ` Alexandre Oliva
2001-01-03 14:21 ` Kai Ruottu [this message]
2001-01-03 14:48 ` Alexandre Oliva
2001-01-04 2:55 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Alexandre Oliva
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Alexandre Oliva
2001-04-01 0:00 ` Kai Ruottu
2001-01-03 8:33 ` Dick Munroe
2001-01-04 2:55 ` Kai Ruottu
2001-01-05 3:59 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Dick Munroe
2001-04-01 0:00 ` Alexandre Oliva
2001-01-03 4:33 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Dick Munroe
2001-01-04 4:22 David Korn
2001-04-01 0:00 ` David Korn
2001-01-04 4:25 David Korn
2001-04-01 0:00 ` David Korn
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=3A53A68E.AE42C58B@luukku.com \
--to=kai.ruottu@luukku.com \
--cc=aoliva@redhat.com \
--cc=crossgcc@sourceware.cygnus.com \
--cc=karuottu@freenet.hut.fi \
--cc=munroe@csworks.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).