[Again] 3.1-branch build problem

[Again] 3.1-branch build problem

[Christian Thalinger]

Just got the new branch and configured with:

If already posted this in gcc-help, but no response.

./configure --prefix=/usr/gcc-3.1 --with-gnu-as --with-gnu-ld
--enable-threads=posix

Then it bails out:

make[2]: Entering directory
`/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
make[2]: *** No rule to make target `../gcc/version.c', needed by
`config.status'.  Stop.
make[2]: Leaving directory
`/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
make[1]: *** [all-unilib] Error 2
make[1]: Leaving directory
`/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
make: *** [all-target-libf2c] Error 2

Is this a problem with gcc_version_trigger?

Regards.

Re: [Again] 3.1-branch build problem

[Andreas Jaeger]

Christian Thalinger <e9625286@student.tuwien.ac.at> writes:

> Just got the new branch and configured with:
>
> If already posted this in gcc-help, but no response.
>
> ./configure --prefix=/usr/gcc-3.1 --with-gnu-as --with-gnu-ld
> --enable-threads=posix

Please do not build directly in the source directory, try a separate
build directory.  If that still fails, please tell us again.

Andreas

> Then it bails out:
>
> make[2]: Entering directory
> `/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
> make[2]: *** No rule to make target `../gcc/version.c', needed by
> `config.status'.  Stop.
> make[2]: Leaving directory
> `/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
> make[1]: *** [all-unilib] Error 2
> make[1]: Leaving directory
> `/usr/src/gcc-3.1-cvs/i686-pc-linux-gnu/libf2c'
> make: *** [all-target-libf2c] Error 2
>
> Is this a problem with gcc_version_trigger?
>
> Regards.
>

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: [Again] 3.1-branch build problem

[Gerald Pfeifer]

On Fri, 12 Apr 2002, Andreas Jaeger wrote:
> Please do not build directly in the source directory, try a separate
> build directory.  If that still fails, please tell us again.

Ahem, building directly in the source directory is not recommended,
but it has been working ever since I first used gcc, and if it does
not work, this still is a bug.

Unless we explicitely decide (and document) that it should not work,
that is.

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

Re: [Again] 3.1-branch build problem

[Loren James Rittle]

>> Just got the new branch and configured with:

>> ./configure --prefix=/usr/gcc-3.1 --with-gnu-as --with-gnu-ld
>> --enable-threads=posix

> Please do not build directly in the source directory, try a separate
> build directory.  If that still fails, please tell us again.

If developers want to take AJ's attitude (and I'm *completely* happy
with it since it makes our lives much easier), THEN WE ABSOLUTELY MUST
APPLY THIS PATCH, OR A REASONABLE ALTERNATE, BEFORE THE 3.1 RELEASE:

http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00102.html

It is NOT fair to tell users in our documentation that something works
but then yell at them when they try it and it is broken.

OTOH, here is the patch for the exact report from Christian:

http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00101.html

Neither has been approved for mainline or 3.1 branch.

Regards,
Loren
-- 
Loren J. Rittle
Senior Staff Software Engineer, Distributed Object Technology Lab
Networks and Infrastructure Research Lab (IL02/2240), Motorola Labs
rittle@rsch.comm.mot.com, KeyID: 2048/ADCE34A5, FDC0292446937F2A240BC07D42763672

Re: [Again] 3.1-branch build problem

[DJ Delorie]

> OTOH, here is the patch for the exact report from Christian:
> 
> http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00101.html
> 
> Neither has been approved for mainline or 3.1 branch.

I don't know how I missed that one, but... approved for both.

Re: [Again] 3.1-branch build problem

[Mark Mitchell]

--On Friday, April 12, 2002 05:18:19 PM -0500 Loren James Rittle 
<rittle@latour.rsch.comm.mot.com> wrote:

>>> Just got the new branch and configured with:
>
>>> ./configure --prefix=/usr/gcc-3.1 --with-gnu-as --with-gnu-ld
>>> --enable-threads=posix
>
>> Please do not build directly in the source directory, try a separate
>> build directory.  If that still fails, please tell us again.
>
> If developers want to take AJ's attitude (and I'm *completely* happy
> with it since it makes our lives much easier), THEN WE ABSOLUTELY MUST
> APPLY THIS PATCH, OR A REASONABLE ALTERNATE, BEFORE THE 3.1 RELEASE:
>
> http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00102.html

I'm hereby approving this patch.  Please check it in.

We have a plan (as you mention in your mail) to make "./configure; make"
turn into something like "mkdir objdir; cd objdir; ../configure; make",
but we haven't don't it.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

Re: [Again] 3.1-branch build problem

[Christian Thalinger]

On Fri, 2002-04-12 at 19:23, Gerald Pfeifer wrote:
> On Fri, 12 Apr 2002, Andreas Jaeger wrote:
> > Please do not build directly in the source directory, try a separate
> > build directory.  If that still fails, please tell us again.

It seems to work now, at least it did for cvs head.

> 
> Ahem, building directly in the source directory is not recommended,
> but it has been working ever since I first used gcc, and if it does
> not work, this still is a bug.

Also always worked for me.

> 
> Unless we explicitely decide (and document) that it should not work,
> that is.
> 
> Gerald
> -- 
> Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

PS @ jerry: Es ist nett mal ein bekanntes gesicht aus einer vorlesung im
netz zu treffen. Bis naechstes mal! dbvo pruefung steht bei mir eh noch
an ;-)