Re: Failure in a complete build of current gcc snapshot

* Angelo Graziosi wrote on Tue, Jul 28, 2009 at 01:20:00AM CEST: > Ralf Wildenhues ha scritto: > >* Tom Tromey wrote on Mon, Jul 27, 2009 at 06:03:54PM CEST: > > > >>I think this patch qualifies as obvious. > > > >Alright. Installed. > > Shouldn't Makefile.in be rebuilt? D'oh. Fixed now. Thank

Re: Failure in a complete build of current gcc snapshot

Ralf Wildenhues ha scritto: * Tom Tromey wrote on Mon, Jul 27, 2009 at 06:03:54PM CEST: "Ralf" == Ralf Wildenhues writes: Ralf> OK to install this trivial patch if it passes the build I'm running Ralf> right now, as well as a normal and a DESTDIR install I'll be doing Ralf> afterwards? I th

Re: Failure in a complete build of current gcc snapshot

* Tom Tromey wrote on Mon, Jul 27, 2009 at 06:03:54PM CEST: > > "Ralf" == Ralf Wildenhues writes: > > Ralf> OK to install this trivial patch if it passes the build I'm running > Ralf> right now, as well as a normal and a DESTDIR install I'll be doing > Ralf> afterwards? > I think this patch

Re: Failure in a complete build of current gcc snapshot

> "Ralf" == Ralf Wildenhues writes: Ralf> OK to install this trivial patch if it passes the build I'm running Ralf> right now, as well as a normal and a DESTDIR install I'll be doing Ralf> afterwards? Ralf> AFAICS the python directory is new in trunk, so no stable releases Ralf> affected. O

Re: Failure in a complete build of current gcc snapshot

Ralf Wildenhues ha scritto: * Angelo Graziosi wrote on Sun, Jul 26, 2009 at 09:59:35AM CEST: Dave Korn ha scritto: Angelo Graziosi wrote: ...are the files with an '*' in their names, like libstdc++*-gdb.py, allowed on Cygwin? No, it's a glob match, the makefile expects there to be something

Re: Failure in a complete build of current gcc snapshot

* Angelo Graziosi wrote on Sun, Jul 26, 2009 at 09:59:35AM CEST: > Dave Korn ha scritto: > >Angelo Graziosi wrote: > > > >>...are the files with an '*' in their names, like libstdc++*-gdb.py, > >>allowed on Cygwin? > > > > No, it's a glob match, the makefile expects there to be something to match

Re: Failure in a complete build of current gcc snapshot

Dave Korn ha scritto: Angelo Graziosi wrote: ...are the files with an '*' in their names, like libstdc++*-gdb.py, allowed on Cygwin? No, it's a glob match, the makefile expects there to be something to match that pattern but there isn't so the shell returns it verbatim instead of expanding

Re: Failure in a complete build of current gcc snapshot

Adding gcc-patches and libstdc++; this is . * Ralf Wildenhues wrote on Sun, Jul 26, 2009 at 09:46:34AM CEST: > > The other bug (the one about libstdc++*) also seems within that rule, > but I don't see it yet. Never mind. The rest is just followup

Re: Failure in a complete build of current gcc snapshot

* Dave Korn wrote on Sun, Jul 26, 2009 at 02:26:05AM CEST: > Angelo Graziosi wrote: > >> make[4]: Nothing to be done for `install-exec-am'. > >> test -z "/usr/local/gfortran/share/gcc-4.5.0/python" || mkdir -p -- > >> "/tmp/inst/usr/local/gfortran/share/gcc-4.5.0/python" > >> /bin/sh: line 0: cd: /

Re: Failure in a complete build of current gcc snapshot

Angelo Graziosi wrote: > > ...are the files with an '*' in their names, like libstdc++*-gdb.py, > allowed on Cygwin? No, it's a glob match, the makefile expects there to be something to match that pattern but there isn't so the shell returns it verbatim instead of expanding it. The reason why

Re: Failure in a complete build of current gcc snapshot

OK, it seems that this failure happens *only* on Cygwin: I have tried on GNU/Linux Kubuntu 8.04 and it works... For what I have understood, this failure remembers, in some manner, what is discussed in this thread [1], and beside this... Dave, ...are the files with an '*' in their names, like