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]

bootstrap broken on mingw (was: Re: AVR port broken on 4.3 20080215 snapshot)

From: FX Coudert <fxcoudert at gmail dot com>
To: Joerg Wunsch <j at uriah dot heep dot sax dot de>, GCC Development <gcc at gcc dot gnu dot org>
Cc: "Weddington, Eric" <eweddington at cso dot atmel dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Denis Chertykov <chertykov at gmail dot com>, Anatoly Sokolov <aesok at post dot ru>, "Lamo, Jo Inge" <jo-inge dot lamo at atmel dot com>
Date: Sun, 17 Feb 2008 11:41:45 +0000
Subject: bootstrap broken on mingw (was: Re: AVR port broken on 4.3 20080215 snapshot)

Hi all,

I also see this failure on a native build for i386-pc-mingw32, so this is probably a mingw issue. Since i686-pc-mingw32 is a seconday platform, this makes it a release blocker (I've marked it as such in bugzilla, and gave it P1 status; I hope that was the right thing to do).

The error here is the same:

../../trunk/gcc/doc//invoke.texi:1243: @include `/home/FX/ibin/ gcc/../../trunk/gcc/../libiberty/at-file.texi': No such file or sdirectory.

What's interesting is that the file actually exists:

$ wc -l /home/FX/ibin/gcc/../../trunk/gcc/../libiberty/at-file.texi
     15 /home/FX/ibin/gcc/../../trunk/gcc/../libiberty/at-file.texi

Thus, I suspect some sort of absolute vs. relative path issue, to which mingw (and especially the MSYS environment) is often very sensitive. For example, bootstrap only work if you use a relative path to configure.

FX

--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/

Follow-Ups:
- Re: bootstrap broken on mingw (was: Re: AVR port broken on 4.3 20080215 snapshot)
  - From: Richard Guenther

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