RE: gcc 4.3.0 -- program search path issue

4 msg	Extracting all functions from C++ source code
2 msg	Force GCC to unroll a loop?
5 msg	Syslog fixes a bug?
2 msg	gcc 4.2.x large file support
2 msg	Windows DEP problem with nested functions
8 msg	Porting GCC to 8051 Microcontroller
2 msg	Cleanup for thread local storage?
3 msg	GCC 4.3.2 Install into Cygwin
4 msg	gcno file doesn't include uncalled member funct...
3 msg	GCC 4.3.0 configure failure: libgcc
2 msg	lex/yacc
1 msg	Building trunk -- error msg instrucitons not qu...
2 msg	MIPS atomic builtins
3 msg	Enabling loop unrolling in small sections of code.
1 msg	#pragma warning
2 msg	Problems building gcc 4.3

gcc 4.3.0 -- program search path issue
\ Toufique, Imam (5 May 2008)
. \ Tom Browder (6 May 2008)
. . \ Toufique, Imam (6 May 2008)
. . . \ Tom Browder (6 May 2008)
. . . . \ Toufique, Imam (6 May 2008)
. . . . . \ Tom Browder (6 May 2008)
. . . . . . \ Toufique, Imam (6 May 2008)
. . . . . . . \ Tom Browder (7 May 2008)

1 msg	Re: WELCOME to gcc
2 msg	Include paths for cpp/g++ (gcc 4.3.0)
2 msg	Linking a library and source file into another ...

Subject:	RE: gcc 4.3.0 -- program search path issue
Group:	Gcc-help
From:	Toufique, Imam
Date:	6 May 2008

Hi Tom,

I have tried the way that you have about building gcc in a build
directory, but no luck. I am not sure what's causing this issue.
Couple of months ago I built gcc 4.2.2 without any issues.

Is there any other places I should do anything or/and make changes?

-Imam

-----Original Message-----
From: Tom Browder [mailto:tom.browder]
Sent: Tuesday, May 06, 2008 4:25 PM
To: Toufique, Imam
Cc: gcc-help
Subject: Re: gcc 4.3.0 -- program search path issue

On Tue, May 6, 2008 at 10:37 AM, Toufique, Imam
<imam.toufique> wrote:
> Hi there Tom,
>
> Did you built gcc 4.3.0 with this method that you have described? Was
> the install successful?

Yes, Imam, many times. I have had as many as four versions of
gcc-x.y.z working in addition to the stock gcc that came with the
distribution at the time.

But I have to confess that I can't remember ever ever using the older
versions. I have pretty good control over the software I use and
haven't had many problems with old source not working with new gcc
versions. (Now gcc 4.3 is a different story--that was a pain with
some packages, including the Loki library.)

I always try to have the latest gcc release on hand--mainly due to the
better and better C++ handling (as well as FORTRAN).

-Tom