From: "Giovanni Bajo" <rasky@develer.com>
To: "Diggory Hardy" <diggory@aethersoft.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Succesful build GCC 3.4.3
Date: Tue, 23 Nov 2004 17:31:00 -0000 [thread overview]
Message-ID: <097a01c4d180$89771b80$f503030a@mimas> (raw)
In-Reply-To: <41A32351.4000508@aethersoft.com>
Diggory Hardy <diggory@aethersoft.com> wrote:
> Could more information on recommended settings for a
> general install be included in the install doc please?
Besides platform-specific quirks which are already listed on the site, the
recommended settings are usually the defaults. On an average x86-linux,
"./configure" with no options works wonderfully. Of course, you may want to
disable some languages you don't need with --disable/enable-languages,
and/or specifying a specific installation path with --prefix.
--
Giovanni Bajo
prev parent reply other threads:[~2004-11-23 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 11:50 Diggory Hardy
2004-11-23 17:31 ` Giovanni Bajo [this message]
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='097a01c4d180$89771b80$f503030a@mimas' \
--to=rasky@develer.com \
--cc=diggory@aethersoft.com \
--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).