[Bug bootstrap/14344] New: [3.3.3 Regression] MinGW Bootstrap Failure

[Bug bootstrap/14344] New: [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

MinGW gcc 3.3.3 fails to bootstrap.  This is a regression because I have been 
able to bootstrap previous 3.3.x releases.

I am working with MSYS (not Cygwin) and I am using the MinGW patches on top of 
the FSF sources. I have flex and bison. I work in /c/temp/gcc/build with the 
sources in /c/temp/gcc/src and the destination /c/temp/gcc/dest . I execute:

../src/configure --prefix=/c/temp/gcc/dest --enable-languages=c,c++ --enable-
sjlj-exceptions --enable-threads=win32 --disable-win32-registry --disable-
shared --without-newlib --disable-nls --disable-debug

Which succeeds.  Then I execute:

make "CFLAGS=-O3 -fomit-frame-pointer -ffast-math" "LDFLAGS=-s -Wl,--
stack=0x00800000" bootstrap

This fails with:
Bootstrapping the compiler
make[1]: Entering directory `/c/temp/gcc/build/gcc'
make AR_FOR_TARGET="ar" \
        RANLIB_FOR_TARGET="ranlib" \
        CC="gcc" libdir=/c/temp/gcc/dest/lib LANGUAGES="c " \
        CFLAGS="" MAKEINFO="makeinfo --no-split" \
        MAKEINFOFLAGS="" COVERAGE_FLAGS=
make[2]: Entering directory `/c/temp/gcc/build/gcc'
TM_DEFINES="" \
HEADERS="auto-host.h ansidecl.h  i386/xm-mingw32.h i386/cygming.h 
i386/mingw32.h defaults.h" XM_DEFINES="POSIX" \
TARGET_CPU_DEFAULT="(TARGET_CPU_DEFAULT_pentiumpro|TARGET_CPU_DEFAULT_pentiumpr
o)" \
/bin/sh ../../src/gcc/mkconfig.sh config.h
TM_DEFINES="" \
HEADERS="auto-host.h ansidecl.h  i386/xm-mingw32.h i386/cygming.h 
i386/mingw32.h defaults.h" XM_DEFINES="POSIX" \
TARGET_CPU_DEFAULT="(TARGET_CPU_DEFAULT_pentiumpro|TARGET_CPU_DEFAULT_pentiumpr
o)" \
/bin/sh ../../src/gcc/mkconfig.sh hconfig.h
make[2]: *** No rule to make target `../../src/gcc/config/i386/cygming.h', 
needed by `gengenrtl.o'.  Stop.
make[2]: Leaving directory `/c/temp/gcc/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/c/temp/gcc/build/gcc'
make: *** [bootstrap] Error 2

I see that cygming.h does not exist in that location. I have verified that the 
file is not present in the plain FSF gcc 3.3.3 sources (i.e. the MinGW patches 
do not remove it).

What's going on?

-- 
           Summary: [3.3.3 Regression] MinGW Bootstrap Failure
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: stl at caltech dot edu
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: mingw32
  GCC host triplet: mingw32
GCC target triplet: mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug bootstrap/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 16:20 -------
Subject: Re:  New: [3.3.3 Regression] MinGW Bootstrap Failure

"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

| MinGW gcc 3.3.3 fails to bootstrap.  This is a regression because I
| have been able to bootstrap previous 3.3.x releases.

Were you able to bootstrap the pre-releases?

[...]

| /bin/sh ../../src/gcc/mkconfig.sh config.h
| TM_DEFINES="" \
| HEADERS="auto-host.h ansidecl.h  i386/xm-mingw32.h i386/cygming.h 
| i386/mingw32.h defaults.h" XM_DEFINES="POSIX" \
| TARGET_CPU_DEFAULT="(TARGET_CPU_DEFAULT_pentiumpro|TARGET_CPU_DEFAULT_pentiumpr
| o)" \
| /bin/sh ../../src/gcc/mkconfig.sh hconfig.h
| make[2]: *** No rule to make target `../../src/gcc/config/i386/cygming.h', 
| needed by `gengenrtl.o'.  Stop.
| make[2]: Leaving directory `/c/temp/gcc/build/gcc'
| make[1]: *** [stage1_build] Error 2
| make[1]: Leaving directory `/c/temp/gcc/build/gcc'
| make: *** [bootstrap] Error 2
| 
| I see that cygming.h does not exist in that location. I have verified that the 
| file is not present in the plain FSF gcc 3.3.3 sources (i.e. the MinGW patches 
| do not remove it).
| 
| What's going on?

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|bootstrap                   |target
           Keywords|                            |build
   Target Milestone|---                         |3.3.4


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 16:56 -------
[Gabriel Dos Reis]
> Were you able to bootstrap the pre-releases?

I did not try to bootstrap the 3.3.3 prereleases.  Should I try to bootstrap 
them, or 3.3.2?

MinGW-patched 3.3.1 just bootstrapped for me.  I also bootstrapped 3.3 a while 
ago.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 17:09 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

| [Gabriel Dos Reis]
| > Were you able to bootstrap the pre-releases?
| 
| I did not try to bootstrap the 3.3.3 prereleases.  Should I try to bootstrap 
| them, or 3.3.2?

yes, please try both 3.3.3-prereleases (they are no longer on the ftp
server but you can grab them from CVS) and 3.3.2, thanks!

(This is sad, because one of the  reasons prereleases are made is for
preventing to discover this sort of problems after the fact)

-- gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 18:58 -------
FSF 3.3.2 fails with:

make[3]: Entering directory `/c/temp/gcc/build/gcc'
for d in libgcc; do \
  if [ -d $d ]; then true; else /bin/sh ../../src/gcc/mkinstalldirs $d; fi; \
done
mkdir libgcc
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
./xgcc -B./ -B/c/temp/gcc/dest/i686-pc-mingw32/bin/ -
isystem /c/temp/gcc/dest/i686-pc-mingw32/include -
isystem /c/temp/gcc/dest/i686-pc-mingw32/sys-include -O2 -
I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -
I../../src/gcc/../winsup/w32api/include -DIN_GCC    -W -Wall -Wwrite-strings -
Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g -
DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -
I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -
I../../src/gcc/../include -DL_chkstk -xassembler-with-cpp -
c ../../src/gcc/config/i386/cygwin.asm -o libgcc/./_chkstk.o
./xgcc -B./ -B/c/temp/gcc/dest/i686-pc-mingw32/bin/ -
isystem /c/temp/gcc/dest/i686-pc-mingw32/include -
isystem /c/temp/gcc/dest/i686-pc-mingw32/sys-include -O2 -
I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -
I../../src/gcc/../winsup/w32api/include -DIN_GCC    -W -Wall -Wwrite-strings -
Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g -
DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -
I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -
I../../src/gcc/../include  -DL_muldi3 -c ../../src/gcc/libgcc2.c -o 
libgcc/./_muldi3.o
In file included from ../../src/gcc/config/i386/mingw32.h:32,
                 from tconfig.h:17,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:30:19: stdio.h: No such file or directory
In file included from ../../src/gcc/config/i386/mingw32.h:32,
                 from tconfig.h:17,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:415: error: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:415: warning: function declaration isn't a 
prototype
../../src/gcc/config/i386/cygwin.h:417: error: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:417: warning: function declaration isn't a 
prototype
In file included from ../../src/gcc/libgcc2.c:37:
../../src/gcc/tsystem.h:72:19: stdio.h: No such file or directory
../../src/gcc/tsystem.h:75:23: sys/types.h: No such file or directory
../../src/gcc/tsystem.h:78:19: errno.h: No such file or directory
../../src/gcc/tsystem.h:85:20: string.h: No such file or directory
../../src/gcc/tsystem.h:89:20: stdlib.h: No such file or directory
../../src/gcc/tsystem.h:90:20: unistd.h: No such file or directory
In file included from include/limits.h:122,
                 from include/syslimits.h:7,
                 from include/limits.h:11,
                 from ../../src/gcc/tsystem.h:93,
                 from ../../src/gcc/libgcc2.c:37:
include/limits.h:122:75: no include path in which to find limits.h
In file included from ../../src/gcc/libgcc2.c:37:
../../src/gcc/tsystem.h:96:18: time.h: No such file or directory
make[3]: *** [libgcc/./_muldi3.o] Error 1
make[3]: Leaving directory `/c/temp/gcc/build/gcc'
make[2]: *** [libgcc.a] Error 2
make[2]: Leaving directory `/c/temp/gcc/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/c/temp/gcc/build/gcc'
make: *** [bootstrap] Error 2

Joy.  That's not even the same error.  (It seems to occur later in the build 
process, whereas the 3.3.3 error seems to happen early; thus, the error in 
3.3.2 may be present in 3.3.3.)  Should I bother with the 3.3.3 prereleases, 
and if so, how can I get them from CVS?  I know how to get the trunk CVS.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 19:32 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

[...]

| Joy.  That's not even the same error.  (It seems to occur later in the build 
| process, whereas the 3.3.3 error seems to happen early; thus, the error in 
| 3.3.2 may be present in 3.3.3.)  Should I bother with the 3.3.3 prereleases, 
| and if so, how can I get them from CVS?  I know how to get the trunk CVS.

Thanks for taking the time to bootstrap previous release.  I don't
think it is necessary to test the prereleases (unless you have spare
cycles ;-)).  The immediate conclusion I can draw is that there is no
active maintainers for the MinGW port.  CGF and DJ are listed as
mingw maintainers, but I also recall CFG saying he is no longer
maintaining that port.  CGF, is that right?

If noone wants to maintain the MinGW port, I'm afraid I can't help
you.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 19:45 -------
[Gabriel Dos Reis]
> Thanks for taking the time to bootstrap previous release.  I don't
> think it is necessary to test the prereleases (unless you have spare
> cycles ;-)).

Okay.  Each bootstrap certainly takes a long time.

> The immediate conclusion I can draw is that there is no active maintainers
> for the MinGW port.

>From what I understand, people do actively maintain MinGW (one person you 
didn't mention is Danny Smith, who released the 3.3.3 MinGW patch set and has 
been active in my 3.4 bootstrap failure bug, PR12974), but the critical thing 
that they don't do is bootstrap MinGW routinely on MSYS, as I do.  Instead 
they use Cygwin.

Perhaps you could help figure out when and where cygming.h, which 3.3.3 seems 
to want, disappeared from the 3.3 branch.  I looked at the CVS web interface, 
which didn't say anything about cygming.h being removed.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-29 19:55 -------
Are you sure that this is 3.3.x as there is no references to cygming.h in 3.3.x's sources at all, it is new 
for 3.4.x?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 20:00 -------
[Andrew Pinski]
> Are you sure that this is 3.3.x as there is no references to cygming.h in
> 3.3.x's sources at all, it is new for 3.4.x?

Quite sure.  To summarize:

MinGW 3.3.3: Fails. (The first error given in the comments.)
FSF 3.3.2: Fails. (The second error given in the comments.)
MinGW 3.3.1: Succeeds. (Just built it an hour ago.)
MinGW 3.3: Succeeds. (Built it long ago and am using it now; building it again 
right now.)

I am not sure whether FSF 3.3.3 works.  Shall I bootstrap that next?  It may 
be that a 3.4 patch referring to cygming.h was incorrectly backported to the 
3.3.3 MinGW patches.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 20:04 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

| > The immediate conclusion I can draw is that there is no active maintainers
| > for the MinGW port.
| 
| From what I understand, people do actively maintain MinGW (one person you 
| didn't mention is Danny Smith, who released the 3.3.3 MinGW patch
| set and has been active in my 3.4 bootstrap failure bug, PR12974),
| but the critical thing that they don't do is bootstrap MinGW
| routinely on MSYS, as I do.  Instead they use Cygwin.

OK. The people I mentioned were those listed in $GCC/MAINTAINERS file.
Danny Smith is listed in the write-after-approval section with no
particular mention of his focus -- I could not have figured out he
maintains mingw.

Anyway, if he does actively main MinGW (and that is good news) I would
suggest he announces so on gcc@gcc.gnu.org so that the SC can
officially appoint him.

You reported that he produced a 3.3.3 MinGW patch set, then presumably
he was able to bootstrap?

| Perhaps you could help figure out when and where cygming.h, which
| 3.3.3 seems to want, disappeared from the 3.3 branch.  I looked at
| the CVS web interface,  which didn't say anything about cygming.h
| being removed. 

I don't think that file did disappear in gcc-3.3-branch time frame.
Rather it *appeared* in gcc-3.4.x with

2003-03-21  Christopher Faylor  <cgf@redhat.com>
        [...]
        * config/i386/cygming.h: New file, containing definitions
        common to mingw32 and cygwin.


What I do not understand though, is why it is referenced in the build
process of gcc-3_3. 

-- Gaby


 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 20:08 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

| [Andrew Pinski]
| > Are you sure that this is 3.3.x as there is no references to cygming.h in
| > 3.3.x's sources at all, it is new for 3.4.x?
| 
| Quite sure.  To summarize:
| 
| MinGW 3.3.3: Fails. (The first error given in the comments.)
| FSF 3.3.2: Fails. (The second error given in the comments.)
| MinGW 3.3.1: Succeeds. (Just built it an hour ago.)
| MinGW 3.3: Succeeds. (Built it long ago and am using it now; building it again 
| right now.)
| 
| I am not sure whether FSF 3.3.3 works.  Shall I bootstrap that next?  It may 

Aaaaaaaarggh, I'm much more interested in *FSF* 3.3.3 than anything else.
Please, oh yes, try that one.

| be that a 3.4 patch referring to cygming.h was incorrectly backported to the 
| 3.3.3 MinGW patches.

that is plausible too.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[dannysmith at gcc dot gnu dot org]

------- Additional Comments From dannysmith at gcc dot gnu dot org  2004-02-29 20:10 -------
The config/i386/cygming.h in the mingw distribution of gcc-3.3.3 is a backport 
from gcc-3.4.  It does not exist in FSF sources of 3.3.3.  

I am confused as to what sources you are using.  If you are using the FSF 
sources and have applied some of the mingw32-local patches but failed to add 
cygming.h than you would get the errors you see.

Can you try with either
(1) pristine FSF sources
(2) the sources as distributed by mingw.org 

The latter will have this in version.c:
const char version_string[] = "3.3.3 (mingw special)";
and 
const char bug_report_url[] = "<URL:http://www.mingw.org/bugs.shtml>";


FWIW, the pristine sources as well as the modified sources both bootstrap 
(host=build=target-mingw32) within a cygwin bash shell (with mounts and path 
set approproiately to hide the cygwin build of gcc) and cygwin autotools and 
dejagnu

There is a sysroot-related bug that apppeared just before 3.3.3 was released, 
but that does not affect bootstap if everything is on same drive.  It only 
affects relocatabilty of toolset across disk volumes.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 20:18 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"dannysmith at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

[...]

Thanks for all those information.

Are you interested in maintaining the MinGW port of FSF GCC?

| FWIW, the pristine sources as well as the modified sources both bootstrap 
| (host=build=target-mingw32) within a cygwin bash shell (with mounts and path 
| set approproiately to hide the cygwin build of gcc) and cygwin autotools and 
| dejagnu
| 
| There is a sysroot-related bug that apppeared just before 3.3.3 was released, 
| but that does not affect bootstap if everything is on same drive.  It only 
| affects relocatabilty of toolset across disk volumes.

Did you happen to have a patch for that?  Was it fixed in gcc-3_4-branch?

Thanks,

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 20:31 -------
[Gabriel Dos Reis]
> You reported that he produced a 3.3.3 MinGW patch set, then presumably
> he was able to bootstrap?

Yes, with Cygwin.

> I don't think that file did disappear in gcc-3.3-branch time frame.
> Rather it *appeared* in gcc-3.4.x with

Ok, that's what I guessed.

> Aaaaaaaarggh, I'm much more interested in *FSF* 3.3.3 than anything else.
> Please, oh yes, try that one.

Okay.

[Danny Smith]
> The config/i386/cygming.h in the mingw distribution of gcc-3.3.3 is a 
backport
> from gcc-3.4.  It does not exist in FSF sources of 3.3.3.  
> I am confused as to what sources you are using.  If you are using the FSF
> sources and have applied some of the mingw32-local patches but failed to add
> cygming.h than you would get the errors you see.

Above I have been using FSF sources from gcc.gnu.org patched with the MinGW 
patches from mingw.org.  This works for 3.3.1 but not for 3.3.3.

I will try using the components provided from mingw.org for 3.3.3 as well as
the pristine FSF sources.

> There is a sysroot-related bug that apppeared just before 3.3.3 was released,
> but that does not affect bootstap if everything is on same drive.  It only
> affects relocatabilty of toolset across disk volumes.

I work with C: only.

--

A couple of other issues:

When I take the FSF 3.3 sources and patch them with Danny Smith's 3.3 patch 
(sent
to a mailing list but never available from mingw.org), the bootstrap fails with
some message about stdio.h.  I remember fixing this somehow (certainly I did,
since I'm using a 3.3 I built myself right now), but I can't recall how.

I tried searching mailing list archives for this issue, since I recall it 
affecting
other people, but couldn't find anything. And this was only in May. Argh.

This wouldn't matter in the first place since I can build 3.3.1, except that 
3.3.1's
libstdc++.a is ten times the size of 3.3's!  That's approximately 9 MB versus 
900 KB.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[dannysmith at gcc dot gnu dot org]

------- Additional Comments From dannysmith at gcc dot gnu dot org  2004-02-29 20:53 -------
Gaby wrote:

> Are you interested in maintaining the MinGW port of FSF GCC?

I am interested in maintaining the mingw port, if OK with CGF. I have been de 
facto maintainer for awhile now.  Most of the patches I have submitted affect 
both cygwin and mingw.


>> There is a sysroot-related bug that apppeared just before 3.3.3 was 
released, 
>> but that does not affect bootstap if everything is on same drive.  It only 
>> affects relocatabilty of toolset across disk volumes.

> Did you happen to have a patch for that?  Was it fixed in gcc-3_4-branch?

I have a patch for 3.3.4 and will submit shortly.  gcc-3.4 barnch and trunk are
ok because of slightly different logic.


STL wrote:
> When I take the FSF 3.3 sources and patch them with Danny Smith's 3.3 patch 
> (sent
> to a mailing list but never available from mingw.org), the bootstrap fails 
with
> some message about stdio.h.

The (complete) patchset and sources (as well as prebuilt binaries)
are available from www.mingw.org.  Follow the link that says 
'Candidate: GCC-3.3.3' under News.

Danny

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 21:04 -------
[Stephan T. Lavavej]
> When I take the FSF 3.3 sources and patch them with Danny Smith's 3.3 patch
> (sent to a mailing list but never available from mingw.org), the bootstrap
> fails with some message about stdio.h.

[Danny Smith]
> The (complete) patchset and sources (as well as prebuilt binaries)
> are available from www.mingw.org.  Follow the link that says
> 'Candidate: GCC-3.3.3' under News.

Note that there I was talking about 3.3[.0].

I did SOMETHING to bootstrap it with MSYS.  I remember rejoicing when I 
finally got it, since before I had been tediously crossing it over from 
GNU/Linux.  I think maybe I had to put mingw-runtime and w32api in the 
destination directory, whereas that is not necessary for 3.3.1.

I'm currently rebuilding 3.3.1 because I did something bad to my directories. 
After that I'll build FSF 3.3.3 and "real" MinGW 3.3.3, and then I'll see if I 
can get 3.3[.0] to build again, to see if the increase in libstdc++.a size is 
actually occuring, or is caused by some change between my forgotten old build 
process and the one I'm using right now.

Actually, looking at it, the error I just got with 3.3[.0] seems to have been 
identical to the FSF 3.3.2 error I mentioned above.

What do the MinGW-local patches "do", anyways?  If I only care about gcc/g++ 
and not other languages, do they do anything for me?  It's all very confusing.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 21:39 -------
Pure FSF 3.3.3 fails with:

if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
./xgcc -B./ -B/c/temp/gcc/dest/i686-pc-mingw32/bin/ -
isystem /c/temp/gcc/dest/i686-pc-mingw32/include -
isystem /c/temp/gcc/dest/i686-pc-mingw32/sys-include -O2 -
I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -
I../../src/gcc/../winsup/w32api/include -DIN_GCC    -W -Wall -Wwrite-strings -
Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g -
DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -
I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -
I../../src/gcc/../include -DL_chkstk -xassembler-with-cpp -
c ../../src/gcc/config/i386/cygwin.asm -o libgcc/./_chkstk.o
./xgcc -B./ -B/c/temp/gcc/dest/i686-pc-mingw32/bin/ -
isystem /c/temp/gcc/dest/i686-pc-mingw32/include -
isystem /c/temp/gcc/dest/i686-pc-mingw32/sys-include -O2 -
I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -
I../../src/gcc/../winsup/w32api/include -DIN_GCC    -W -Wall -Wwrite-strings -
Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g -
DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -
I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -
I../../src/gcc/../include  -DL_muldi3 -c ../../src/gcc/libgcc2.c -o 
libgcc/./_muldi3.o
In file included from ../../src/gcc/config/i386/mingw32.h:32,
                 from tconfig.h:17,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:30:19: stdio.h: No such file or directory
In file included from ../../src/gcc/config/i386/mingw32.h:32,
                 from tconfig.h:17,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:415: error: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:415: warning: function declaration isn't a 
prototype
../../src/gcc/config/i386/cygwin.h:417: error: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:417: warning: function declaration isn't a 
prototype
In file included from ../../src/gcc/libgcc2.c:37:
../../src/gcc/tsystem.h:72:19: stdio.h: No such file or directory
../../src/gcc/tsystem.h:75:23: sys/types.h: No such file or directory
../../src/gcc/tsystem.h:78:19: errno.h: No such file or directory
../../src/gcc/tsystem.h:85:20: string.h: No such file or directory
../../src/gcc/tsystem.h:89:20: stdlib.h: No such file or directory
../../src/gcc/tsystem.h:90:20: unistd.h: No such file or directory
In file included from include/limits.h:122,
                 from include/syslimits.h:7,
                 from include/limits.h:11,
                 from ../../src/gcc/tsystem.h:93,
                 from ../../src/gcc/libgcc2.c:37:
include/limits.h:122:75: no include path in which to find limits.h
In file included from ../../src/gcc/libgcc2.c:37:
../../src/gcc/tsystem.h:96:18: time.h: No such file or directory
make[3]: *** [libgcc/./_muldi3.o] Error 1
make[3]: Leaving directory `/c/temp/gcc/build/gcc'
make[2]: *** [libgcc.a] Error 2
make[2]: Leaving directory `/c/temp/gcc/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/c/temp/gcc/build/gcc'
make: *** [bootstrap] Error 2

Still not sure if this is caused by not putting w32api and mingw-runtime in 
dest (but my patched 3.3.1 doesn't need it!).  Testing the "real" MinGW 3.3.3 
now.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[cgf at redhat dot com]

------- Additional Comments From cgf at redhat dot com  2004-02-29 21:57 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

On Sun, Feb 29, 2004 at 08:23:29PM +0100, Gabriel Dos Reis wrote:
>"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:
>[...]
>
>| Joy.  That's not even the same error.  (It seems to occur later in the build 
>| process, whereas the 3.3.3 error seems to happen early; thus, the error in 
>| 3.3.2 may be present in 3.3.3.)  Should I bother with the 3.3.3 prereleases, 
>| and if so, how can I get them from CVS?  I know how to get the trunk CVS.
>
>Thanks for taking the time to bootstrap previous release.  I don't
>think it is necessary to test the prereleases (unless you have spare
>cycles ;-)).  The immediate conclusion I can draw is that there is no
>active maintainers for the MinGW port.  CGF and DJ are listed as
>mingw maintainers, but I also recall CFG saying he is no longer
>maintaining that port.  CGF, is that right?

No.  I have never said anything like that.

With MinGW, I do take lots of guidance from Danny, however, and he
usually does step in to help with issues like this.

>If noone wants to maintain the MinGW port, I'm afraid I can't help
>you.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 22:03 -------
"True" MinGW 3.3.3 fails with:

if [ -f specs.ready ] ; then \
        true; \
else \
        echo timestamp > specs.ready; \
fi
(MAKE="make"; srcdir=`cd ../../src/gcc/fixinc && ${PWDCMD-pwd}` ; \
CC="gcc"; CFLAGS="   -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -
Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H -
DGENERATOR_FILE"; LDFLAGS="-s -Wl,--stack=0x00800000"; \
WARN_CFLAGS="-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -Wtraditional -pedantic -Wno-long-long "; 
LIBERTY=`pwd`/"../libiberty/libiberty.a"; \
export MAKE srcdir CC CFLAGS LDFLAGS WARN_CFLAGS LIBERTY; \
cd ./fixinc && \
/bin/sh ${srcdir}/mkfixinc.sh i686-pc-mingw32 i686-pc-mingw32)
constructing ../fixinc.sh for i686-pc-mingw32 to run on i686-pc-mingw32
The directory that should contain system headers does not exist:
  /c/temp/gcc/dest/include
make[2]: *** [stmp-fixinc] Error 1
make[2]: Leaving directory `/c/temp/gcc/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/c/temp/gcc/build/gcc'
make: *** [bootstrap] Error 2

This is perhaps the most intelligable error message I've ever seen from a gcc 
bootstrap, and I think it's telling me to dump mingw-runtime and w32api in 
dest. I'll do so and run it again.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[cgf at redhat dot com]

------- Additional Comments From cgf at redhat dot com  2004-02-29 22:29 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

On Sun, Feb 29, 2004 at 08:54:43PM +0100, Gabriel Dos Reis wrote:
>"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:
>
>| > The immediate conclusion I can draw is that there is no active maintainers
>| > for the MinGW port.
>| 
>| From what I understand, people do actively maintain MinGW (one person you 
>| didn't mention is Danny Smith, who released the 3.3.3 MinGW patch
>| set and has been active in my 3.4 bootstrap failure bug, PR12974),
>| but the critical thing that they don't do is bootstrap MinGW
>| routinely on MSYS, as I do.  Instead they use Cygwin.
>
>OK. The people I mentioned were those listed in $GCC/MAINTAINERS file.
>Danny Smith is listed in the write-after-approval section with no
>particular mention of his focus -- I could not have figured out he
>maintains mingw.
>
>Anyway, if he does actively main MinGW (and that is good news) I would
>suggest he announces so on gcc@gcc.gnu.org so that the SC can
>officially appoint him.
>
>You reported that he produced a 3.3.3 MinGW patch set, then presumably
>he was able to bootstrap?
>
>| Perhaps you could help figure out when and where cygming.h, which
>| 3.3.3 seems to want, disappeared from the 3.3 branch.  I looked at
>| the CVS web interface,  which didn't say anything about cygming.h
>| being removed. 
>
>I don't think that file did disappear in gcc-3.3-branch time frame.
>Rather it *appeared* in gcc-3.4.x with
>
>2003-03-21  Christopher Faylor  <cgf@redhat.com>
>        [...]
>        * config/i386/cygming.h: New file, containing definitions
>        common to mingw32 and cygwin.
>
>
>What I do not understand though, is why it is referenced in the build
>process of gcc-3_3. 

I don't really understand why we're discussing a patched version of gcc.
AFAICT, there are no references to cygming.h anywhere in the
gcc_3_3_3_release branch.  I have closed this bug since it is reported
against the patched mingw sources rather than the pure branch.

I'd suggest that a mingw mailing list would be the best place to get
questions answered about this.  I don't think there is any reason for
further speculation here.

cgf


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 22:44 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

Christopher Faylor <cgf@redhat.com> writes:

| On Sun, Feb 29, 2004 at 08:23:29PM +0100, Gabriel Dos Reis wrote:
| >"stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> writes:
| >[...]
| >
| >| Joy.  That's not even the same error.  (It seems to occur later in the build 
| >| process, whereas the 3.3.3 error seems to happen early; thus, the error in 
| >| 3.3.2 may be present in 3.3.3.)  Should I bother with the 3.3.3 prereleases, 
| >| and if so, how can I get them from CVS?  I know how to get the trunk CVS.
| >
| >Thanks for taking the time to bootstrap previous release.  I don't
| >think it is necessary to test the prereleases (unless you have spare
| >cycles ;-)).  The immediate conclusion I can draw is that there is no
| >active maintainers for the MinGW port.  CGF and DJ are listed as
| >mingw maintainers, but I also recall CFG saying he is no longer
| >maintaining that port.  CGF, is that right?
| 
| No.  I have never said anything like that.

OK, I must have confused with something else.  Sorry for the
misrecollection. 

| With MinGW, I do take lots of guidance from Danny, however, and he
| usually does step in to help with issues like this.

OK, would you "sponsor" his being appointed as Cygwin and MinGW
maintainer if I make such proposal to the SC?

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[cgf at redhat dot com]

------- Additional Comments From cgf at redhat dot com  2004-02-29 22:48 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

On Sun, Feb 29, 2004 at 11:34:40PM +0100, Gabriel Dos Reis wrote:
>| With MinGW, I do take lots of guidance from Danny, however, and he
>| usually does step in to help with issues like this.
>
>OK, would you "sponsor" his being appointed as Cygwin and MinGW
>maintainer if I make such proposal to the SC?

Danny has repeatedly said that he doesn't want that responsibility.

I'm beginning to think this should be in the FAQ or something...

Probably DJ's name should be removed from MAINTAINERS, though.  I
don't think he's interested in being a cygwin/mingw maintainer.

cgf


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 22:57 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

Christopher Faylor <cgf@redhat.com> writes:

| On Sun, Feb 29, 2004 at 11:34:40PM +0100, Gabriel Dos Reis wrote:
| >| With MinGW, I do take lots of guidance from Danny, however, and he
| >| usually does step in to help with issues like this.
| >
| >OK, would you "sponsor" his being appointed as Cygwin and MinGW
| >maintainer if I make such proposal to the SC?
| 
| Danny has repeatedly said that he doesn't want that responsibility.

I don't understand your statement.  It comment #14, Danny said:

  Gaby wrote:
  > Are you interested in maintaining the MinGW port of FSF GCC?

  I am interested in maintaining the mingw port, if OK with CGF. I
  have been de facto maintainer for awhile now.  Most of the patches
  I have submitted affect both cygwin and mingw.


| I'm beginning to think this should be in the FAQ or something...

I like FAQs, but in this case I don't know what it would be about, for
you're claiming something which contradicts what Danny just said.

| Probably DJ's name should be removed from MAINTAINERS, though.  I
| don't think he's interested in being a cygwin/mingw maintainer.

That is fine with me.  Now that you're mentioning that I think the
previous claim I attributed to you where actually DJ's.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[cgf at redhat dot com]

------- Additional Comments From cgf at redhat dot com  2004-02-29 23:36 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

On Sun, Feb 29, 2004 at 11:47:47PM +0100, Gabriel Dos Reis wrote:
>Christopher Faylor <cgf@redhat.com> writes:
>
>| On Sun, Feb 29, 2004 at 11:34:40PM +0100, Gabriel Dos Reis wrote:
>| >| With MinGW, I do take lots of guidance from Danny, however, and he
>| >| usually does step in to help with issues like this.
>| >
>| >OK, would you "sponsor" his being appointed as Cygwin and MinGW
>| >maintainer if I make such proposal to the SC?
>| 
>| Danny has repeatedly said that he doesn't want that responsibility.
>
>I don't understand your statement.  It comment #14, Danny said:
>
>  Gaby wrote:
>  > Are you interested in maintaining the MinGW port of FSF GCC?
>
>  I am interested in maintaining the mingw port, if OK with CGF. I
>  have been de facto maintainer for awhile now.  Most of the patches
>  I have submitted affect both cygwin and mingw.

I hadn't read that statement, obviously.

>| I'm beginning to think this should be in the FAQ or something...
>
>I like FAQs, but in this case I don't know what it would be about, for
>you're claiming something which contradicts what Danny just said.

I was representing what Danny had repeatedly asserted whenever I
asked him about this.  He's since changed his mind, apparently.

I have no problem whatsoever with adding him to the maintainership for
mingw/cygwin.  It's past due, IMO.

cgf


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[gdr at integrable-solutions dot net]

------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 23:41 -------
Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure

"cgf at redhat dot com" <gcc-bugzilla@gcc.gnu.org> writes:

| >| I'm beginning to think this should be in the FAQ or something...
| >
| >I like FAQs, but in this case I don't know what it would be about, for
| >you're claiming something which contradicts what Danny just said.
| 
| I was representing what Danny had repeatedly asserted whenever I
| asked him about this.  He's since changed his mind, apparently.
| 
| I have no problem whatsoever with adding him to the maintainership for
| mingw/cygwin.  It's past due, IMO.

Great!  I'm going to make the suggestion to SC, saying you're OK with
that.  Thanks!

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344

Re: [Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[Christopher Faylor]

[removing bugzilla from To:]
On Sun, Feb 29, 2004 at 11:41:16PM -0000, gdr at integrable-solutions dot net wrote:
>
>------- Additional Comments From gdr at integrable-solutions dot net  2004-02-29 23:41 -------
>Subject: Re:  [3.3.3 Regression] MinGW Bootstrap Failure
>
>"cgf at redhat dot com" <gcc-bugzilla@gcc.gnu.org> writes:
>
>| >| I'm beginning to think this should be in the FAQ or something...
>| >
>| >I like FAQs, but in this case I don't know what it would be about, for
>| >you're claiming something which contradicts what Danny just said.
>| 
>| I was representing what Danny had repeatedly asserted whenever I
>| asked him about this.  He's since changed his mind, apparently.
>| 
>| I have no problem whatsoever with adding him to the maintainership for
>| mingw/cygwin.  It's past due, IMO.
>
>Great!  I'm going to make the suggestion to SC, saying you're OK with
>that.  Thanks!

The only gotcha is that I'm not clear on whether Danny is ok with being
a cygwin/mingw maintainer.  I think he should be.  He's provided many
cygwin fixes as well.

cgf

[Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure

[stl at caltech dot edu]

------- Additional Comments From stl at caltech dot edu  2004-02-29 23:57 -------
The MinGW gcc 3.3.3 components as provided by mingw.org (rather than FSF 
sources with the mingw.org patches), when mingw-runtime-3.2 and w32api-2.5 are 
put into dest, bootstrap cleanly.

I have NO idea why 3.3.1 doesn't require mingw-runtime-3.2 and w32api-2.5, and 
I don't know why patching things manually doesn't work for 3.3.3 when it does 
work for 3.3.1, but I guess I shouldn't think too deeply about dark magicks.

I am marking this bug as INVALID because in the end it was My Fault.  
Congratulations to Danny Smith on his upcoming maintainership; I'm glad my 
silly bug report led to some real good.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344