Skip Menu |

This queue is for tickets about the Perl-Dist-Strawberry CPAN distribution.

Report information
The Basics
Id: 52092
Status: resolved
Priority: 0/
Queue: Perl-Dist-Strawberry

People
Owner: Nobody in particular
Requestors: kmx [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: 64-bit gcc toolchain + related tools
Just for record, we currently have: 1) 64-bit gcc toolchain (gcc+binutils) provided by mingw-w64 projects: http://svn.ali.as/cpan/users/kmx/strawberry_gcc-toolchain/mingw64-w64-20091101.7z There are some issues to be solved - see README.TXT in the same directory 2) gnumake, dmake, pexports, patch I have build both 32-bit/64-bit versions from scratch: http://svn.ali.as/cpan/users/kmx/strawberry_packs/2010-January/ So IMHO we basically have all we need for building the first 64-bit strawberry beta. -- kmx
Just for record the current status of the new 32-bit/64-bit gcc4 toolchains provided by mingw-w64.sf.net project. There are 3 problems left that we need to be solved before we seriously use these toolchains for any strawberry release: 1) "include dir issue" http://sourceforge.net/tracker/?func=detail&aid=2886331&group_id=202880&atid=983354 2) "32-bit EXE not working well on XP" http://sourceforge.net/tracker/?func=detail&aid=2892010&group_id=202880&atid=983354 3) "libxml issue" http://sourceforge.net/projects/mingw-w64/forums/forum/723797/topic/3482477 #1 and #2 are for us currently blockers. -- kmx
Subject: Re: [rt.cpan.org #52092] 64-bit gcc toolchain + related tools
Date: Tue, 22 Dec 2009 21:26:55 +1100
To: bug-Perl-Dist-Strawberry [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
Will these prevent somewhat-useful beta releases entirely? Or just the production releases? Adam K 2009/12/22 kmx via RT <bug-Perl-Dist-Strawberry@rt.cpan.org>: Show quoted text
>       Queue: Perl-Dist-Strawberry >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=52092 > > > Just for record the current status of the new 32-bit/64-bit gcc4 > toolchains provided by mingw-w64.sf.net project. > > There are 3 problems left that we need to be solved before we seriously > use these toolchains for any strawberry release: > > 1) "include dir issue" > http://sourceforge.net/tracker/?func=detail&aid=2886331&group_id=202880&atid=983354 > > 2) "32-bit EXE not working well on XP" > http://sourceforge.net/tracker/?func=detail&aid=2892010&group_id=202880&atid=983354 > > 3) "libxml issue" > http://sourceforge.net/projects/mingw-w64/forums/forum/723797/topic/3482477 > > #1 and #2 are for us currently blockers. > > -- > kmx >
Subject: Re: [rt.cpan.org #52092] 64-bit gcc toolchain + related tools
Date: Tue, 22 Dec 2009 11:43:24 +0100
To: bug-Perl-Dist-Strawberry [...] rt.cpan.org
From: kmx <kmx [...] volny.cz>
Hi Adam, Show quoted text
> Will these prevent somewhat-useful beta releases entirely? Or just the > production releases? >
*) workaround for #1 is to set some env variables (which is IMHO quite OK for betatesting) *) workaround for #2 is to do 32-bit betatesting on Vista not on XP (ugly); this issue does not affect 64-bit version at all *) #3 could be ignored for now To sum up: - Working on 64-bit beta based on perl 5.11.3 (or higher) could be started right now - I would wait with new 32-bit strawberry based on the new gcc4 toolchain (we can stay on the old toolchain for a while) -- kmx
Show quoted text

This issue is fixed in the gcctoolchain marked "20091224" which I have just uploaded to:
http://svn.ali.as/cpan/users/kmx/strawberry_gcc-toolchain/
Thanks go to sezero (mingw-w64 guy) who has build these binaries.

I have tested the new gcc toolchain with perl 5.11.3 - seems to build without any troubles.

--
kmx
Show quoted text
> 1) "include dir issue"
This issue is fixed in the gcctoolchain marked "20100109" which I have just uploaded to: http://svn.ali.as/cpan/users/kmx/strawberry_gcc-toolchain/ NOW WE HAVE A TOOLCHAIN 100% READY FOR BUILDING 64BIT STRAWBERRY. -- kmx
Important note for those who will try to build perl with the new mingw-w64's gcc toolchains:

You need to set this variable in win32\makefile.mk
EXTRALIBDIRS    *= $(CCHOME)\x86_64-w64-mingw32\lib

use:
- "x86_64-w64-mingw32" for 64-bit toolchain
- "i686-w64-mingw32" for 32-bit toolchain

or get the right value by running: gcc -dumpmachine

My proof-of-concept 64bit build is available here:
http://svn.ali.as/cpan/users/kmx/strawberry_64bit-pre/
(once again I apologise to Alias for committing such a big file to his SVN)

--
kmx
Subject: Re: [rt.cpan.org #52092] 64-bit gcc toolchain + related tools
Date: Fri, 22 Jan 2010 11:53:06 +1100
To: bug-Perl-Dist-Strawberry [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
Please stop. Even if you delete the file later, that 50 meg is still going to be consumed on the server, and any requests that process history will need to keep scanning it. If you don't have the login for the strawberryperl website, so you can stuff things in the package/downloads directory, ask and you shall recieve. Adam K 2010/1/22 kmx via RT <bug-Perl-Dist-Strawberry@rt.cpan.org>: Show quoted text
>       Queue: Perl-Dist-Strawberry >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=52092 > > > Important note for those who will try to build perl with the new mingw-w64's > gcc toolchains: > > You need to set this variable in win32\makefile.mk > EXTRALIBDIRS *= $(CCHOME)\x86_64-w64-mingw32\lib > > use: > - "x86_64-w64-mingw32" for 64-bit toolchain > - "i686-w64-mingw32" for 32-bit toolchain > > or get the right value by running: gcc -dumpmachine > > My proof-of-concept 64bit build is available here: > http://svn.ali.as/cpan/users/kmx/strawberry_64bit-pre/ > (once again I apologise to Alias for committing such a big file to his SVN) > > -- > kmx > >
Subject: Re: [rt.cpan.org #52092] 64-bit gcc toolchain + related tools
Date: Fri, 22 Jan 2010 01:21:24 -0700
To: "Reserved Local Account via RT" <bug-Perl-Dist-Strawberry [...] rt.cpan.org>
From: "Curtis Jewell" <perl [...] csjewell.fastmail.us>
On Thu, 21 Jan 2010 19:53 -0500, "Reserved Local Account via RT" <bug-Perl-Dist-Strawberry@rt.cpan.org> wrote: Show quoted text
> Queue: Perl-Dist-Strawberry > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=52092 > > > Please stop. > > Even if you delete the file later, that 50 meg is still going to be > consumed on the server, and any requests that process history will > need to keep scanning it. > > If you don't have the login for the strawberryperl website, so you can > stuff things in the package/downloads directory, ask and you shall > recieve.
Which as far as I know, he doesn't. The one problem is, I often have to jiggle the packages around, or repack them [so I can have them unpacked with the same code, into the same places, for example], so when kmx does get the login, it'd be a good idea if he puts the new packages into a "to-be-considered" directory, and I can polish them up for use. We should have been using subdirectories of the "package" directory to arrange things long ago. I'm starting to do it now - with the need to keep track of 3 package chains. (no insult intended by the third-person...) --Curtis -- Curtis Jewell csjewell@cpan.org http://csjewell.dreamwidth.org/ perl@csjewell.fastmail.us http://csjewell.comyr.org/perl/ "Your random numbers are not that random" -- perl-5.10.1.tar.gz/util.c Strawberry Perl for Windows betas: http://strawberryperl.com/beta/
Show quoted text
> Please stop.

OK.

I am sorry for troubles I have caused but building ext libraries and arranging the working gcc toolchain is simply disk space consuming. I know that SVN is not a good technology for storing binary packages but I have currently no other place where to upload them.

I'll be happy if you can arrange for some access to some dedicated directory on strawberryperl website - I do not need access to package/downloads used for building strawberry releases, something like package/downloads/kmx would be more than sufficient.

I am gonna keep all the newly build packages on my PC till we find a better place for them.

--
kmx
Toolchain binaries moved from svn.ali.as to:
http://strawberryperl.com/package/kmx/

The gcc toolchains (32/64bit) marked 20100123 are IMHO in "release quality" - no critical problems I am aware of.

--
kmx
Adding to a tracking bug - I plan on doing some more this within the next week or two.
Hi Curtis,

FYI - I have just uploaded slightly updated gcc4 toolchains:

http://strawberryperl.com/package/kmx/32_gcctoolchain/mingw64-w32-20100123-kmx-v2.zip
http://strawberryperl.com/package/kmx/32_gcctoolchain/mingw64-w32-20100123-kmx-v2-lic.zip

http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2.zip
http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2-lic.zip

I have done just minor fixes:
1/ updated DirectX related headers
2/ added some extra OpenGL related headers

All gcc and binutils binaries are exactly the same (so I do not expect any regression bugs related to gcc toolchain).

From my point of view this is what I propose to use for the first 5.11/5.12 release of strawberry.

--
kmx
On Mon Mar 08 09:37:42 2010, KMX wrote: Show quoted text
> Hi Curtis, > > FYI - I have just uploaded slightly updated gcc4 toolchains: > > http://strawberryperl.com/package/kmx/32_gcctoolchain/mingw64-w32- > 20100123-kmx-v2.zip > http://strawberryperl.com/package/kmx/32_gcctoolchain/mingw64-w32- > 20100123-kmx-v2-lic.zip > > http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64- > 20100123-kmx-v2.zip > http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64- > 20100123-kmx-v2-lic.zip > > I have done just minor fixes: > 1/ updated DirectX related headers > 2/ added some extra OpenGL related headers > > All gcc and binutils binaries are exactly the same (so I do not expect > any > regression bugs related to gcc toolchain). > > From my point of view this is what I propose to use for the first > 5.11/5.12 > release of strawberry.
We're using these toolchains - 'patched'.