make failure in building GCC CVS

make failure in building GCC CVS

[David Starner]

It fails pretty quickly into the build.

make[1]: Leaving directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/zlib'
make[1]: Entering directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/gcc'
Makefile:973: *** multiple target patterns.  Stop.
make[1]: Leaving directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/gcc'
make: *** [all-gcc] Error 2

Line 973 is

native: config.status auto-host.h intl.all $(LANGUAGES) \
	$(EXTRA_PASSES) $(EXTRA_PROGRAMS) $(USE_COLLECT2)

It's make 3.79.1 as patched for Debian, running on i686-pc-linux-gnu.

Is this a local problem, or is someone else seeing it too?

-- 
David Starner - dstarner98@aasaa.ofe.org
http://dvdeug.dhis.org
As centuries of pulp novels and late-night Christian broadcasting have taught 
us, anything we don't understand can be used for the purposes of Evil.
	-- Kenneth Hite, Suppressed Transmissions

Re: make failure in building GCC CVS

[Gerald Pfeifer]

On Tue, 14 Nov 2000, David Starner wrote:
> make[1]: Leaving directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/zlib'
> make[1]: Entering directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/gcc'
> Makefile:973: *** multiple target patterns.  Stop.
> make[1]: Leaving directory `/home/dvdeug/Code/GCC/gcc-cvs/gcc_build/gcc'
> make: *** [all-gcc] Error 2
>
> Line 973 is
>
> native: config.status auto-host.h intl.all $(LANGUAGES) \
> 	$(EXTRA_PASSES) $(EXTRA_PROGRAMS) $(USE_COLLECT2)
>
> It's make 3.79.1 as patched for Debian, running on i686-pc-linux-gnu.
>
> Is this a local problem, or is someone else seeing it too?

This is definitely *not* a local problem! I am seeing it on a SuSE 7.0
box (i686-pc-linux-gnu) as well, albeit slightly different:

  gmake[5]: Entering directory `/tmp/OBJ-1114-10:33/i686-pc-linux-gnu/libstdc++-v3/src'
  Makefile:374: *** multiple target patterns.  Stop.

And i686-pc-linux-gnu/libstdc++-v3/src/Makefile lines 374ff are:

  Makefile: $(srcdir)/Makefile.in  $(top_builddir)/config.status
        cd $(top_builddir) \
          && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status

That is, this is a direct result of the libstdc++-v3 integration. I guess
it might be related to autoconf et al. not being installed on this system.

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