From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16628 invoked by alias); 21 May 2003 14:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 16593 invoked by uid 71); 21 May 2003 14:56:01 -0000 Date: Wed, 21 May 2003 14:56:00 -0000 Message-ID: <20030521145601.16592.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Jos van den Oever Subject: Re: c++/10902: comparing doubles is not consistent in gcc 3.3 (SuSE version) Reply-To: Jos van den Oever X-SW-Source: 2003-05/txt/msg02300.txt.bz2 List-Id: The following reply was made to PR c++/10902; it has been noted by GNATS. From: Jos van den Oever To: Wolfgang Bangerth Cc: gcc-bugs@gcc.gnu.org, Subject: Re: c++/10902: comparing doubles is not consistent in gcc 3.3 (SuSE version) Date: Wed, 21 May 2003 16:54:19 +0200 On Wednesday 21 May 2003 16:41, you wrote: > 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. Ok, thanks for the instruction. It sounds safe to me, so I'll try it.