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]
Other format: [Raw text]

Re: Configuring GCC build: doc patch


On Mon, Jul 19, 2004 at 03:04:34PM +0100, Dave Korn wrote:
> > -----Original Message-----
> > From: Hugh Sasse Staff Elec Eng [mailto:hgs@dmu.ac.uk] 
> > Sent: 19 July 2004 14:30
> 
> > On Mon, 19 Jul 2004, Dave Korn wrote:
> > 
> >    [my suggestion "Do not use a relative path for configure" elided]
> > >
> > >  Works fine for me.  I think it's only certain hosts that have this
> > > problem, isn't it?
> > 
> > My case was Solaris 9 sparc 
> 
>   Ah yes, that was the one: came up only a couple of weeks ago.
> 
> http://gcc.gnu.org/ml/gcc/2004-07/msg00025.html
> 
> > I don't know why it should fail in such a case. 
> 
>   Some kind of discrepancy between Solaris shell semantics and other
> systems, at a guess, but I don't know.

See PR 13993, and especially my comments in PR 15668.  This should not
be very hard to fix.

> "The Solaris 2 /bin/sh will often fail to configure libstdc++-v3, boehm-gc
> or libjava. We therefore recommend to use the following sequence of commands
> to bootstrap and install GCC: 
> 
>         % CONFIG_SHELL=/bin/ksh
>         % export CONFIG_SHELL
> 
> and then proceed as described in the build instructions, where we strongly
> recommend using GNU make and specifying an absolute path to invoke
> srcdir/configure. "

This is an unrelated problem.

-- 
Daniel Jacobowitz


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