public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6825: [Sun OS 4.1.4] gcc 3.1 fails to build Date: Thu, 05 Dec 2002 14:26:00 -0000 [thread overview] Message-ID: <20021205222601.13374.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6825; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: jason andrade <jason@dstc.edu.au> Cc: gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/6825: [Sun OS 4.1.4] gcc 3.1 fails to build Date: Thu, 5 Dec 2002 16:20:27 -0600 (CST) > well, i'm compiling it now. do you care about warnings ? there are > _lots_ of them. a gcc build for c/c++ usually takes a few hours on > the machine i have here (ss10 w/ dual 125Mhz hypersparc w/ 128M) so > my Thanks for your attempts. I think first priority would be to make the thing running. Warnings are not taken particularly important. > ./configure --prefix=/opt/local/stow/gcc-3.2.1 --enable-languages=c,c++ > and > make -j2 CFLAGS=-O2 LIBCFLAGS=-O2 LIBCXXFLAGS=-O2 -fno-implicit-templates bootstrap-lean First, since this failed, could you retry by building in a separate build-directory, as the installation instructions recommend? I.e., if gcc-3.2.1 is you src dir, then make a parallel directory build and call ../gcc-3.2.1/configure --... make bootstrap Also, what happens if you don't specify CFLAGS et al? As far as I know the stage2 build already uses optimization flags, so there is no need to also use them for the first two stages (apart from possibly tripping your bootstrapping compiler). Thanks Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-05 22:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-05 14:26 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 8:36 Dara Hazeghi 2002-12-05 15:26 Wolfgang Bangerth 2002-12-05 15:16 jason andrade 2002-12-02 4:56 David S. Miller 2002-12-02 4:46 jason andrade
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=20021205222601.13374.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).