From: Frank Schafer <frank.schafer@setuza.cz>
To: gcc-help@gcc.gnu.org
Subject: Building gcc
Date: Wed, 10 Oct 2001 00:20:00 -0000 [thread overview]
Message-ID: <3BC3FA5B.EA741FEF@setuza.cz> (raw)
Hi there,
I'm building a complete GNU/Linux system from scratch. The first turn,
building everything needed statically linked went fine. Now I'll need to
make the static build.
During the static build there were already several include files
installed. The glibc docs say to remove everything in ``/usr/include''.
Can I remove this ( or better initialize it containing only the kernel
headers ) before the build, if everything is static?
What are theese ``usr/include/g++-v3/'' and
``/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include'' -things. Can ( or
should ) I remove theese too?
Oh, before I forget ... will I be able to build everything with 3.0.x?
It is reported, that ( at least glibc ) things cannot be built with it.
I got a reply, that there is a patch for 2.95.3 to proper compile glibc,
but nobody can tell me WHERE it is.
Thanks for any help
Frank
next reply other threads:[~2001-10-10 0:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 0:20 Frank Schafer [this message]
2001-10-10 19:24 ` Curtis R Anderson
2001-10-10 21:07 ` Frank Schafer
2001-10-11 1:40 ` gcc 3.0.1 on Tru64 Unix 5.1A anyone? Paul Reilly
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 6:52 building gcc Myhuong Nguyen
2007-10-19 10:08 ` Kai Ruottu
2006-06-02 19:40 Building GCC Flop Bucket
2005-06-13 8:13 Frank Schafer
2005-06-13 9:02 ` Nathan Sidwell
2004-02-05 3:30 Help needed in compiling SSE2 asm code ganesh.yadav
2004-02-05 7:11 ` building gcc Dave Murphy
2001-09-26 8:50 Govind Vinjamuri
2001-09-28 17:49 ` Alexandre Oliva
2000-09-14 5:43 Building GCC Michael J. McGillick
2000-09-14 11:22 ` Alexandre Oliva
1999-10-22 23:00 Immanuel Andrew
1999-10-22 23:21 ` Tim Prince
1999-10-31 13:57 ` Tim Prince
1999-10-31 13:57 ` Immanuel Andrew
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=3BC3FA5B.EA741FEF@setuza.cz \
--to=frank.schafer@setuza.cz \
--cc=gcc-help@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).