mingw April 2011

mingw@lists.fedoraproject.org

8 participants
84 discussions

[Bug 673784] Rename Request: mingw32-filesystem -> mingw-filesystem - Cross compiler base filesystem and environment
by Red Hat Bugzilla 10 Apr '11

10 Apr '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=673784 --- Comment #20 from Richard W.M. Jones <rjones(a)redhat.com> 2011-04-10 12:33:25 EDT --- Agreed Tim's analysis is correct. It is (was) a provides that was accidentally dropped. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

Re: Announcing the Cross Compiler Framework (Win32+Win64)
by Erik van Pienbroek 10 Apr '11

10 Apr '11

R P Herrold schreef op do 07-04-2011 om 13:20 [-0400]: > On Mon, 3 Jan 2011, Erik van Pienbroek wrote: > > > My plan is to get all the packages belonging to the cross compiler > > framework in Fedora 15, rebuild all current mingw32 packages and > > rename/port various packages in order to have win32/win64 support. On > > The wiki page was last updated 4 Feb, and I do not think I > have missed any update on the mailing list ... . How is this > coming? [actually reading more closely, I see F16 as a target > in the wiki]. Also, zlib, and openssl exceptions seem > material, as they are either so widely used, or so necessary > > My thought was build on your foundation to use a cross-compile > chain for building toward the ARM based: > http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx > which obviously is not presently a target arch, but I was > going to poke at solving the needed diff's. > > It is not clear to me that this is a better approach than a > pure GCC one, but it seemed to me that for some reason Fedora > has resisted having a set of cross-compile tools in mainline > to that effect. I may be totally wrong here, and am aware of > the native arm build project on such hardware out there, but > being able to cross-build on faster commodity hardware [and > hopefully being able to use a 'dist-cc' or such] seemed useful > > best regards > > -- Russ herrold Hi Russ, We're still working on getting support for mingw-w64 in Fedora 16. Right now we're waiting on approval of the updated packaging guidelines [1] from the Fedora Packaging Committee [2]. We're also waiting on getting clearance from Fedora/Red Hat legal for the mingw-w64 headers and crt. My initial plan with the cross compiler framework was to provide a generic method to build for multiple targets. However, I have the impression that there's a strong resistance to such a framework. The most probable reason behind this is that every target has it's own characteristics (like desktop vs. embedded) which can't be mixed in something generic. The proposal we've put up for review is only for support of the Win32 and Win64 targets. The Mac OS X target was initially also there, but it was refused (as there are also legal issues involved with that target). However, the packages which are currently in the testing repository (the 'cross-*' packages) can be quite easily changed to have support for the ARM target. Basically it comes down to these steps: - Add RPM macros for the target in the cross-filesystem package - Update the cross-binutils package to also build compiler tools for the target - Update the cross-gcc package to also build a compiler for the target - Add a package containing the target's standard headers and libraries (glibc?) - Try to get everything bootstrapped Now for every package you want to compile against this new toolchain, you have to add the line '%global _cross_build_mytarget 1' to the .spec file and some other small additions (as can be seen at [3]). After that you should have binary RPMS for your target. This may look quite difficult, but it's mostly a copy/paste of already existing lines. If you really want to continue with this, feel free to drop any questions you might have on the fedora-mingw mailing list. If we can get something working, perhaps we can convince the Fedora Packaging Committee to approve a generic cross compiler framework. Kind regards, Erik van Pienbroek [1]: https://fedoraproject.org/wiki/PackagingDrafts/MinGWCrossCompiler [2]: https://fedorahosted.org/fpc/ticket/71 [3]: https://fedoraproject.org/wiki/MinGW/CrossCompilerFramework#Porting_guide

1 0

[Bug 673784] Rename Request: mingw32-filesystem -> mingw-filesystem - Cross compiler base filesystem and environment
by Red Hat Bugzilla 10 Apr '11

10 Apr '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=673784 --- Comment #19 from Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> 2011-04-10 06:25:58 EDT --- Thanks for spotting this. I've just published an updated package: Spec URL: http://svn.openftd.org/svn/fedora_cross/mingw-filesystem/mingw-filesystem.s… SRPM URL: http://ftd4linux.nl/contrib/mingw-filesystem-67-1.fc15.src.rpm * Sun Apr 10 2011 Erik van Pienbroek <epienbro(a)fedoraproject.org> - 67-1 - Merged the provides list from the Fedora mingw32-filesystem package Somehow various entries got lost -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 673784] Rename Request: mingw32-filesystem -> mingw-filesystem - Cross compiler base filesystem and environment
by Red Hat Bugzilla 10 Apr '11

10 Apr '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=673784 Tim Mayberry <mojofunk(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mojofunk(a)gmail.com --- Comment #18 from Tim Mayberry <mojofunk(a)gmail.com> 2011-04-10 02:36:14 EDT --- (In reply to comment #17) > After discussion with some members of the Fedora MinGW SIG we decided to drop > the 'cross-*' prefix for now and stick with 'mingw-*' as prefix. Support for > Mac OS X may take a long while to get ready (possible even never because of the > legal issues), so we can use 'mingw-*' for now. We've also filed a ticket at > the Fedora Packaging Committee with a request to approve the (updated) draft > guidelines: https://fedorahosted.org/fpc/ticket/71 > > Updated package: > Spec URL: > http://svn.openftd.org/svn/fedora_cross/mingw-filesystem/mingw-filesystem.s… > SRPM URL: > http://ftd4linux.nl/contrib/mingw-filesystem-66-1.fc15.src.rpm > Hi, I've been trying out the new cross compiler framework from the repository located at: http://build1.openftd.org/fedora-cross/fedora-cross.repo on Fedora 14 I got an error when trying to install mingw32-curl saying there was a missing provides(wldap32.dll). So I added Provides: mingw32(wldap32.dll) to the mingw32-filesystem package(and similarly for the mingw64-filesystem package) and after rebuilding, curl would install fine. Looking at the changelog: * Thu Nov 13 2008 Richard Jones <rjones(a)redhat.com> - 35-1 - Added mingw32(wldap32.dll) pseudo-provides. So it seems like it was there at some point but nothing in the changelog indicating why it is no longer. Anyway, hope this is relevant and helps. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

mingw April 2011