From: Earnie B. <ea...@us...> - 2013-08-08 13:02:40
Attachments:
mingw-dist-mingw32-gcc4-lessthan-4.8.patch
|
I'm trying to get ready for gcc-4.8.1 with WSL-4.0 release. I want to ensure that gcc less than 4.8.1 uses mingwrt and w32api less than the 4.0 release. Will the attached patch accomplish what I want with the already released GCC? I've not added 4.8.1 data to it yet, just getting the file ready in mingw-dist. ~~~~~ diff --git a/mingw32/mingw32-gcc4.xml b/mingw32/mingw32-gcc4.xml index a8f3e13..b8e3eb8 100644 --- a/mingw32/mingw32-gcc4.xml +++ b/mingw32/mingw32-gcc4.xml @@ -35,22 +35,42 @@ <component class="bin"> <release tarname="gcc-core-4.5.2-1-mingw32-bin.tar.lzma"> <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> + <requires le="w32api-3.17-2-mingw32-dev.tar" /> </release> <release tarname="gcc-core-4.6.1-2-mingw32-bin.tar.lzma"> <requires eq="libquadmath-%-mingw32-dll-0.tar" /> <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> + <requires le="w32api-3.17-2-mingw32-dev.tar" /> </release> <release tarname="gcc-core-4.6.2-1-mingw32-bin.tar.lzma"> <requires eq="libquadmath-%-mingw32-dll-0.tar" /> <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> + <requires le="w32api-3.17-2-mingw32-dev.tar" /> </release> <release tarname="gcc-core-4.7.0-1-mingw32-bin.tar.lzma"> <requires eq="libquadmath-%-mingw32-dll-0.tar" /> <requires ge="mingwrt-3.20-2-mingw32-dev.tar" /> + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> + <requires le="w32api-3.17-2-mingw32-dev.tar" /> </release> <release tarname="gcc-core-4.7.2-1-mingw32-bin.tar.lzma"> <requires eq="libquadmath-%-mingw32-dll-0.tar" /> <requires ge="mingwrt-3.20-2-mingw32-dev.tar" /> + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> + <requires le="w32api-3.17-2-mingw32-dev.tar" /> </release> <!-- Requirements common to all of the above releases --> @@ -58,10 +78,6 @@ <requires eq="libgcc-%-mingw32-dll-1.tar" /> <requires eq="libssp-%-mingw32-dll-0.tar" /> <requires eq="libgomp-%-mingw32-dll-1.tar" /> - <requires eq="libmpc-*-mingw32-dll-2.tar" /> - <requires eq="pthreads-w32-*-mingw32-dev.tar" /> - <requires eq="binutils-*-mingw32-bin.tar" /> - <requires eq="w32api-*-mingw32-dev.tar" /> </component> <component class="doc"> ~~~~~ -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Earnie B. <ea...@us...> - 2013-08-19 15:33:13
|
Ping, any input on this? On Thu, Aug 8, 2013 at 9:02 AM, Earnie Boyd wrote: > I'm trying to get ready for gcc-4.8.1 with WSL-4.0 release. I want to > ensure that gcc less than 4.8.1 uses mingwrt and w32api less than the > 4.0 release. Will the attached patch accomplish what I want with the > already released GCC? I've not added 4.8.1 data to it yet, just > getting the file ready in mingw-dist. > > ~~~~~ > diff --git a/mingw32/mingw32-gcc4.xml b/mingw32/mingw32-gcc4.xml > index a8f3e13..b8e3eb8 100644 > --- a/mingw32/mingw32-gcc4.xml > +++ b/mingw32/mingw32-gcc4.xml > @@ -35,22 +35,42 @@ > <component class="bin"> > <release tarname="gcc-core-4.5.2-1-mingw32-bin.tar.lzma"> > <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> > + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> > + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> > + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> > + <requires le="w32api-3.17-2-mingw32-dev.tar" /> > </release> > <release tarname="gcc-core-4.6.1-2-mingw32-bin.tar.lzma"> > <requires eq="libquadmath-%-mingw32-dll-0.tar" /> > <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> > + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> > + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> > + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> > + <requires le="w32api-3.17-2-mingw32-dev.tar" /> > </release> > <release tarname="gcc-core-4.6.2-1-mingw32-bin.tar.lzma"> > <requires eq="libquadmath-%-mingw32-dll-0.tar" /> > <requires lt="mingwrt-3.20-2-mingw32-dev.tar" /> > + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> > + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> > + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> > + <requires le="w32api-3.17-2-mingw32-dev.tar" /> > </release> > <release tarname="gcc-core-4.7.0-1-mingw32-bin.tar.lzma"> > <requires eq="libquadmath-%-mingw32-dll-0.tar" /> > <requires ge="mingwrt-3.20-2-mingw32-dev.tar" /> > + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> > + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> > + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> > + <requires le="w32api-3.17-2-mingw32-dev.tar" /> > </release> > <release tarname="gcc-core-4.7.2-1-mingw32-bin.tar.lzma"> > <requires eq="libquadmath-%-mingw32-dll-0.tar" /> > <requires ge="mingwrt-3.20-2-mingw32-dev.tar" /> > + <requires le="libmpc-0.8.1-1-mingw32-dll-2.tar" /> > + <requires le="pthreads-w32-2.9.0-mingw32-*-dev.tar" /> > + <requires le="binutils-2.23.1-1-mingw32-bin.tar" /> > + <requires le="w32api-3.17-2-mingw32-dev.tar" /> > </release> > > <!-- Requirements common to all of the above releases --> > @@ -58,10 +78,6 @@ > <requires eq="libgcc-%-mingw32-dll-1.tar" /> > <requires eq="libssp-%-mingw32-dll-0.tar" /> > <requires eq="libgomp-%-mingw32-dll-1.tar" /> > - <requires eq="libmpc-*-mingw32-dll-2.tar" /> > - <requires eq="pthreads-w32-*-mingw32-dev.tar" /> > - <requires eq="binutils-*-mingw32-bin.tar" /> > - <requires eq="w32api-*-mingw32-dev.tar" /> > </component> > > <component class="doc"> > ~~~~~ > > -- > Earnie > -- https://sites.google.com/site/earnieboyd -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Keith M. <kei...@us...> - 2013-08-21 20:16:28
|
On 19/08/13 16:33, Earnie Boyd wrote: > Ping, any input on this? > > On Thu, Aug 8, 2013 at 9:02 AM, Earnie Boyd wrote: >> I'm trying to get ready for gcc-4.8.1 with WSL-4.0 release. I want to >> ensure that gcc less than 4.8.1 uses mingwrt and w32api less than the >> 4.0 release. Will the attached patch accomplish what I want with the >> already released GCC? I've not added 4.8.1 data to it yet, just >> getting the file ready in mingw-dist. Your XML looks okay, but why preclude the use of mingwrt-4.x and w32api-4.x with earlier GCC? I'm using, and indeed am dependent on both of them, (or rather on wsl-4.0, to be precise), for mingw-get, yet I'm still building with GCC-3.4.5. This WJFFM. -- Regards, Keith. |
From: Earnie B. <ea...@us...> - 2013-08-22 11:13:19
|
On Wed, Aug 21, 2013 at 10:25 AM, Keith Marshall <kei...@us...> wrote: > > On 19/08/13 16:33, Earnie Boyd wrote: > > Ping, any input on this? > > > > On Thu, Aug 8, 2013 at 9:02 AM, Earnie Boyd wrote: > >> I'm trying to get ready for gcc-4.8.1 with WSL-4.0 release. I want to > >> ensure that gcc less than 4.8.1 uses mingwrt and w32api less than the > >> 4.0 release. Will the attached patch accomplish what I want with the > >> already released GCC? I've not added 4.8.1 data to it yet, just > >> getting the file ready in mingw-dist. > > Your XML looks okay, but why preclude the use of mingwrt-4.x and > w32api-4.x with earlier GCC? I'm using, and indeed am dependent on > both of them, (or rather on wsl-4.0, to be precise), for mingw-get, > yet I'm still building with GCC-3.4.5. This WJFFM. The released versions will be built with gcc-4.8.1 and we have a stated ABI change. I could just limit the new releases of gcc, binutils and dependents to the runtime and API 4.0. Do you feel that is enough? -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Keith M. <kei...@us...> - 2013-08-22 19:44:21
|
On 22/08/13 12:13, Earnie Boyd wrote: >> ... why preclude the use of mingwrt-4.x and w32api-4.x with >> earlier GCC? I'm using, and indeed am dependent on both of them, >> (or rather on wsl-4.0, to be precise), for mingw-get, yet I'm >> still building with GCC-3.4.5. This WJFFM. > > The released versions will be built with gcc-4.8.1 and we have a > stated ABI change. Do you mean the change in internal layout of the (supposedly opaque) dirent struct? That really shouldn't cause a problem, unless one such struct is created on one side of, and manipulated on the other side of a module (e.g. DLL) boundary, with differing ABI versions on either side. > I could just limit the new releases of gcc, binutils and dependents > to the runtime and API 4.0. Do you feel that is enough? I think so; possibly even that is more than is necessary. -- Regards, Keith. |