public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: reader@newsguy.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: Confused about build proceedure srcdir vs objdir
Date: Sat, 27 Oct 2001 08:08:00 -0000	[thread overview]
Message-ID: <3BDACD91.B63F3204@unitus.it> (raw)

Hi Harry,

>Oh, thanks Paolo.  I already posted another `amateur hour' message
before seeing your post.
>What is the significance of `bootstrap'? I didn't notice anything about
that at the config help page.
>Now looking at the `build' instructions ... maybe in there.

Do you know the novel "THE ADVENTURES OF BARON MUNCHHAUSEN"?
"Bootstrap" has to do with lifting yourself in the air by pulling your
own boot-straps!

So, for compilers, you have the problem that after your un-tar you have
to compile your own compiler?!? How to do it? Well, you cannot really do
what MUNCHHAUSEN does in the novel (i.e., you *need* a basic working C
compiler to begin with!) but then, after having built a new C compiler,
the boostrap process uses it to build the others (C++, Fortran, Java,
...). In the meanwhile it is also carried out a sanity check of the
system (this is for another time ;-)

I suggest you to always use "make bootstrap" even if you are confident
that you installed compiler could be used right away to build the new
suite (plain "make" does this). This should be also explained in the
docs.

Cheers,
Paolo.


             reply	other threads:[~2001-10-27  8:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27  8:08 Paolo Carlini [this message]
     [not found] <3BDA7B75.119F779D@unitus.it>
2001-10-27  4:10 ` Harry Putnam
  -- strict thread matches above, loose matches on Subject: below --
2001-10-26 22:30 Harry Putnam
2001-10-27  2:14 ` Florian Weimer
2001-10-27 15:10   ` Harry Putnam
2001-10-28  1:13     ` Florian Weimer
2001-10-28  7:25       ` Harry Putnam
2001-10-28  7:37         ` Florian Weimer
2001-10-28  8:05           ` Harry Putnam
2001-10-28  8:58             ` lange92
2001-10-28  8:07           ` John Levon
2001-10-29  9:25             ` Florian Weimer
2001-10-29  4:59         ` John Love-Jensen
2001-10-29 10:10           ` Harry Putnam

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=3BDACD91.B63F3204@unitus.it \
    --to=pcarlini@unitus.it \
    --cc=gcc-help@gcc.gnu.org \
    --cc=reader@newsguy.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).