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: bootstrap failure with rev 130208

From: Jim Wilson <wilson at specifix dot com>
To: Thomas Koenig <tkoenig at netcologne dot de>
Cc: gcc at gcc dot gnu dot org
Date: Fri, 16 Nov 2007 14:20:05 -0800
Subject: Re: bootstrap failure with rev 130208
References: <1195162309.3202.4.camel@meiner.onlinehome.de> <473CF598.5040908@specifix.com> <1195196870.3201.12.camel@meiner.onlinehome.de>

Thomas Koenig wrote:

On Thu, 2007-11-15 at 17:42 -0800, Jim Wilson wrote:
Thomas Koenig wrote:
build/genmodes -h > tmp-modes.h
/bin/sh: build/genmodes: No such file or directory

Your problem is that you accidentally ran ../gcc/gcc/configure instead of ../gcc/configure. However, why it fails this way has me baffled. I can easily reproduce it though.

The rule to build genmodes by the way is build/gen%$(build_exeext): build/gen%.o $(BUILD_LIBDEPS) $(CC_FOR_BUILD) $(BUILD_CFLAGS) $(BUILD_LDFLAGS) -o $@ \

            $(filter-out $(BUILD_LIBDEPS), $^) $(BUILD_LIBS)
This is some GNU make magic.

For some reason, make finds this rule if gcc is correctly configured, but can't find it if gcc is incorrectly configured. I looked at make -d output; I didn't find it helpful. For some reason the search order for matching patterns is different, but I see no clue why. -- Jim Wilson, GNU Tools Support, http://www.specifix.com

References:
- bootstrap failure with rev 130208
  - From: Thomas Koenig
- Re: bootstrap failure with rev 130208
  - From: Jim Wilson
- Re: bootstrap failure with rev 130208
  - From: Thomas Koenig

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