This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: After some thought.....



> First: Checking environment variables is a *good* idea as it will save a
> lot of people a lot of time.

Well, yes.

> Second: Checking *all* variables may not be a stupid thing, because:-
>     1 - We don't know which one(s) cause(s) the problem(s).

Actually, we do.  Only those variables used as paths cause the problem;
the reason they cause the problem is that during the build process we
do a number of cd commands.  For that reason, your script as it is is
not a good idea.

> First: Why don't those of you who develop egcs compile it with egcs? Why
> have you chosen	pgcc? (That's 2 questions...oh well)

That's a very strange question indeed.  First, 'make bootstrap' always
builds the compiler with itself, so egcs is always compiled by egcs.
Second, what does pgcc have to do with anything?  The pgcc group is
merging with egcs patches -- is this what has confused you?

> Third: How can I switch between gcc, egcs (and pgcc when I get it. I
> figure you use it, so it must work...)? 

The egcs developers do not use pgcc.

You can have multiple compilers at once, if you build from source.  Just
set the --prefix argument to configure to a different position.  For
example, --prefix=/usr/local/egcs -- you can then have egcs's gcc be
/usr/local/egcs/bin/gcc.

> When I tried to switch from egcs
> back to GNU gcc, I ended up having to upgrade everything to gcc 2.8.1`to
> make it work again (which I did wrongly, but have fixed now...)

That's because you installed a binary release.  That represents a major
commitment.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]