Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Vincent Lefevre
On 2009-07-25 18:57:25 -0700, Joe Buck wrote: > That's incorrect. The runtime library is GPLv3 or later, but with an > *exception* that permits linking not only with GPLv2 programs, but > also with proprietary programs. If the runtime library is GPLv3 or later, shouldn't programs linked with it s

Re: Failure in a complete build of current gcc snapshot

2009-07-26 Thread Ralf Wildenhues
* 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

2009-07-26 Thread Ralf Wildenhues
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

2009-07-26 Thread Angelo Graziosi
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

2009-07-26 Thread Ralf Wildenhues
* 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

2009-07-26 Thread Angelo Graziosi
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: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Arnaud Charlet
> Eh, this exception doesn't change that the GPLv2 program perceives the > GPLv3 as incompatible. Why would it? Is it GPLv2 or GPLv2+? If the latter (the license includes something like "either version 2 of the License, or (at your option) any later version"), then nothing prevents you from distr

Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Florian Weimer
* Arnaud Charlet: >> Eh, this exception doesn't change that the GPLv2 program perceives the >> GPLv3 as incompatible. Why would it? > > Is it GPLv2 or GPLv2+? GPLv2 (I tried to stress by writing "GPLv2-only"). > If the latter (the license includes something like "either version 2 > of the Licen

Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Arnaud Charlet
> GPLv2 (I tried to stress by writing "GPLv2-only"). Understood. > > If the latter (the license includes something like "either version 2 > > of the License, or (at your option) any later version"), then > > nothing prevents you from distributing the program under GPLv3+ > > instead of GPLv2+. >

Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Florian Weimer
* Arnaud Charlet: >> > If the latter (the license includes something like "either version 2 >> > of the License, or (at your option) any later version"), then >> > nothing prevents you from distributing the program under GPLv3+ >> > instead of GPLv2+. >> >> Right, but we've got some stuff which i

trunk bootstrap failure in libgfortran for i686-pc-cygwin

2009-07-26 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 if /bin/sh ./libtool --tag=CC --mode=compile /home/rainer/software/build/i686-pc-cygwin/gcc-4.5.0/gcc/./gcc/xgcc - -B/home/rainer/software/build/i686-pc-cygwin/gcc-4.5.0/gcc/./gcc/ - -B/opt/devel/gnu/gcc/gcc-4.5.0/i686-pc-cygwin/i686-pc-cygwin/bin/ - -

Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Joe Buck
> * Joe Buck: > On Sat, Jul 25, 2009 at 01:53:40PM -0700, Florian Weimer wrote: > >> Kalle Olavi Niemitalo discovered that as an operating system vendor, > >> you are not allowed to distribute GPL version 2 programs if they are > >> compiled with GCC 4.4. The run-time library is GPL version 3 or

gcc-4.3-20090726 is now available

2009-07-26 Thread gccadmin
Snapshot gcc-4.3-20090726 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20090726/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.3 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: Compiling programs licensed under the GPL version 2 with GCC 4.4

2009-07-26 Thread Florian Weimer
* Joe Buck: > Doesn't matter, because the runtime library is not under GPLv3. It's > under GPLv3 plus the runtime restriction. That combination is more > permissive than GPLv2 (because of the exceptions it makes). Therefore, > as far as I can tell, there is no conflict; the combined program has