From: kaih@khms.westfalen.de (Kai Henningsen)
To: gcc@gcc.gnu.org
Subject: Re: trouble building gcc-3.2 --target=m68k-linux from scratch
Date: Tue, 20 Aug 2002 00:13:00 -0000 [thread overview]
Message-ID: <8VEAF8yXw-B@khms.westfalen.de> (raw)
In-Reply-To: <200208191724.g7JHOoS19048@hyper.wm.sps.mot.com>
pbarada@mail.wm.sps.mot.com (Peter Barada) wrote on 19.08.02 in < 200208191724.g7JHOoS19048@hyper.wm.sps.mot.com >:
> Since a stock linux source doesn't have pthread.h in its headers, and
That should be completely irrelevant. User programs (such as gcc) aren't
supposed to include the raw kernel headers, they're supposed to - if
anything - use copies provided by libc. (And no, /usr/include/linux is
*NOT* supposed to be a symlink. That was a design error in ancient history
that has been fixed *years* ago.)
> glibc hasn't been built yet, there's no pthread.h that can be used at
> this time.
That, OTOH, is of course completely relevant.
> If I add --disable-threads to the configure for the bootstrap, it
> completes.
I believe 3.2 does include the change that made pthreads default on
practically every variant of Linux, so as to get everyone on a common ABI.
MfG Kai
next prev parent reply other threads:[~2002-08-20 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 10:24 Peter Barada
2002-08-19 15:32 ` Loren James Rittle
2002-08-19 15:46 ` Peter Barada
2002-08-19 16:14 ` Loren James Rittle
2002-08-19 21:12 ` Dan Kegel
2002-08-20 6:53 ` Peter Barada
2002-08-20 0:13 ` Kai Henningsen [this message]
2002-08-20 1:05 ` Richard Zidlicky
2002-08-20 7:27 ` Peter Barada
2002-08-21 3:59 ` Richard Zidlicky
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=8VEAF8yXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=gcc@gcc.gnu.org \
/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).