public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10902: comparing doubles is not consistent in gcc 3.3 (SuSE version) Date: Wed, 21 May 2003 14:46:00 -0000 [thread overview] Message-ID: <20030521144601.21306.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10902; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: Jos van den Oever <jos@vandenoever.info> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/10902: comparing doubles is not consistent in gcc 3.3 (SuSE version) Date: Wed, 21 May 2003 09:41:09 -0500 (CDT) > I'd like to install the released version of gcc 3.3, but as this is a > production system I'm working on, I prefer to install rpms from SuSE. If you use ../gcc-3.3/configure --prefix=/some/local/path make bootstrap make install it will install gcc into /some/local/path, which could be a scratch directory in your homedir, or in /tmp. It won't overwrite any preinstalled files in /usr/... That's a safe way not to compromise the integrity of a production system. You can then run the compiler by setting PATH and LD_LIBRARY_PATH just for once in a shell window. > If there are any (SuSE or other reliable) rpms with gcc 3.3 I'm willing to > test. I have no clue. I'd think that SuSE might have one, but don't know. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-21 14:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-21 14:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 14:56 Jos van den Oever 2003-05-21 14:36 Jos van den Oever 2003-05-21 14:14 bangerth 2003-05-21 12:36 Jos van den Oever 2003-05-21 11:36 Jos van den Oever 2003-05-21 10:33 jos
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=20030521144601.21306.qmail@sources.redhat.com \ --to=bangerth@ices.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).