[opensuse-packaging] mingw cross-toolchain
Hello! I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
Robert Schiele wrote:
I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/.
That's nice. Would you mind putting that into the build service? Does it also work with C++? Last time I tried I only got C working which was sufficient for qstat and quake3. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, Jan 11, 2007 at 03:42:20PM +0100, Ludwig Nussel wrote:
Robert Schiele wrote:
I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/.
That's nice. Would you mind putting that into the build service?
I can make a copy there if this is desired. Just suggest a project name.
Does it also work with C++? Last time I tried I only got C working
It should. I have initially packaged this more than 3 years ago and it worked for me since then.
which was sufficient for qstat and quake3.
If you see problems just drop me a note. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Thu, Jan 11, 2007 at 07:40:32PM +0100, Robert Schiele wrote:
On Thu, Jan 11, 2007 at 03:42:20PM +0100, Ludwig Nussel wrote:
Robert Schiele wrote:
I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/.
That's nice. Would you mind putting that into the build service?
I can make a copy there if this is desired. Just suggest a project name.
Since no project name was suggested for 6 weeks I just took CrossToolchain:mingw. Unfortunately a linker crash occurred for all 10.0 or newer distributions that cannot be reproduced on the respective systems locally. Thus binaries for these distributions are not available in the build service but have to be fetched from the URL above. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On 2007-02-23 19:14:34 +0100, Robert Schiele wrote:
On Thu, Jan 11, 2007 at 07:40:32PM +0100, Robert Schiele wrote:
On Thu, Jan 11, 2007 at 03:42:20PM +0100, Ludwig Nussel wrote:
Robert Schiele wrote:
I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/.
That's nice. Would you mind putting that into the build service?
I can make a copy there if this is desired. Just suggest a project name.
Since no project name was suggested for 6 weeks I just took CrossToolchain:mingw. Unfortunately a linker crash occurred for all 10.0 or newer distributions that cannot be reproduced on the respective systems locally. Thus binaries for these distributions are not available in the build service but have to be fetched from the URL above.
maybe a xen issue? does osc build work locally? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Feb 23, 2007 at 07:22:46PM +0100, Marcus Rueckert wrote:
On 2007-02-23 19:14:34 +0100, Robert Schiele wrote:
Since no project name was suggested for 6 weeks I just took CrossToolchain:mingw. Unfortunately a linker crash occurred for all 10.0 or newer distributions that cannot be reproduced on the respective systems locally. Thus binaries for these distributions are not available in the build service but have to be fetched from the URL above.
maybe a xen issue?
No, I found that I mixed up a version when uploading to the build service. Fixed now. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Fri, 23 Feb 2007, Robert Schiele wrote:
On Thu, Jan 11, 2007 at 07:40:32PM +0100, Robert Schiele wrote:
On Thu, Jan 11, 2007 at 03:42:20PM +0100, Ludwig Nussel wrote:
Robert Schiele wrote:
I have packaged a cross-toolchain for Windows machines based on the latest releases of the mingw gcc port. You can find everything at http://pi3.informatik.uni-mannheim.de/~schiele/suse/.
That's nice. Would you mind putting that into the build service?
I can make a copy there if this is desired. Just suggest a project name.
Since no project name was suggested for 6 weeks I just took CrossToolchain:mingw. Unfortunately a linker crash occurred for all 10.0 or newer distributions that cannot be reproduced on the respective systems locally. Thus binaries for these distributions are not available in the build service but have to be fetched from the URL above.
I see we now have several versions of gcc and binutils sources in the
CrossToolchain subpackages. Can we somehow consolidate some of them
in CrossToolchain:(binutils|gcc)-$ver packages you can link from? Also
as the number of cross targets increase I wonder if its worth putting
up a wiki page on opensuse.org for them.
Versions used are:
binutils gcc
avr: Factory Factory
m68k-noos: 2.16 4.1.1
mingw: 2.16.91 3.4.5-20060117-1
msp340: 2.17 3.2.3
sh4: Factory Factory
Richard.
--
Richard Guenther
On Sun, Feb 25, 2007 at 04:14:17PM +0100, Richard Guenther wrote:
I see we now have several versions of gcc and binutils sources in the CrossToolchain subpackages. Can we somehow consolidate some of them in CrossToolchain:(binutils|gcc)-$ver packages you can link from? Also as the number of cross targets increase I wonder if its worth putting up a wiki page on opensuse.org for them.
A wiki page to do what?
Versions used are:
binutils gcc avr: Factory Factory m68k-noos: 2.16 4.1.1 mingw: 2.16.91 3.4.5-20060117-1 msp340: 2.17 3.2.3
Unfortunately the platforms I have put there (mingw and msp430) currently have a major bug or no support in the binutils/gcc versions as present in Factory. Thus as long as I don't find the time to fix/port to these versions an extra version is needed anyway. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Sun, Feb 25, 2007 at 05:29:47PM +0100, Robert Schiele wrote:
On Sun, Feb 25, 2007 at 04:14:17PM +0100, Richard Guenther wrote:
Versions used are:
binutils gcc avr: Factory Factory m68k-noos: 2.16 4.1.1 mingw: 2.16.91 3.4.5-20060117-1 msp340: 2.17 3.2.3
Unfortunately the platforms I have put there (mingw and msp430) currently have a major bug or no support in the binutils/gcc versions as present in Factory. Thus as long as I don't find the time to fix/port to these versions an extra version is needed anyway.
Ok, for msp430-binutils I have a solution: The problem is the broken fix for http://sourceware.org/bugzilla/show_bug.cgi?id=2623. If you add the patch from http://build.opensuse.org/package/show?package=cross-msp430-binutils&project=CrossToolchain%3Amsp430%3Atest to your binutils package, add msp430 to the set of built cross packages and also mark msp430 as a non-linux patches similar to avr then I could drop my own version of the package and just link to the factory package. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Sun, Feb 25, 2007 at 09:20:33PM +0100, Robert Schiele wrote:
On Sun, Feb 25, 2007 at 05:29:47PM +0100, Robert Schiele wrote:
On Sun, Feb 25, 2007 at 04:14:17PM +0100, Richard Guenther wrote:
Versions used are:
binutils gcc avr: Factory Factory m68k-noos: 2.16 4.1.1 mingw: 2.16.91 3.4.5-20060117-1 msp340: 2.17 3.2.3
Unfortunately the platforms I have put there (mingw and msp430) currently have a major bug or no support in the binutils/gcc versions as present in Factory. Thus as long as I don't find the time to fix/port to these versions an extra version is needed anyway.
Ok, for msp430-binutils I have a solution: The problem is the broken fix for http://sourceware.org/bugzilla/show_bug.cgi?id=2623. If you add the patch from http://build.opensuse.org/package/show?package=cross-msp430-binutils&project=CrossToolchain%3Amsp430%3Atest to your binutils package, add msp430 to the set of built cross packages and also mark msp430 as a non-linux patches similar to avr then I could drop my own version of the package and just link to the factory package.
If you also incorporate the changes I did to the spec file in http://build.opensuse.org/package/show?package=cross-mingw-binutils&project=CrossToolchain%3Amingw%3Atest and also add mingw to the set of built cross packages I could drop my own version of binutils for mingw as well and link to the factory package. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Sun, Feb 25, 2007 at 04:14:17PM +0100, Richard Guenther wrote:
I see we now have several versions of gcc and binutils sources in the CrossToolchain subpackages. Can we somehow consolidate some of them in CrossToolchain:(binutils|gcc)-$ver packages you can link from? Also
Hello? If you really want to consolidate that stuff then why don't you answer to my mails regarding that topic I sent to you and the list more than two weeks ago? Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
On Tue, 13 Mar 2007, Robert Schiele wrote:
On Sun, Feb 25, 2007 at 04:14:17PM +0100, Richard Guenther wrote:
I see we now have several versions of gcc and binutils sources in the CrossToolchain subpackages. Can we somehow consolidate some of them in CrossToolchain:(binutils|gcc)-$ver packages you can link from? Also
Hello? If you really want to consolidate that stuff then why don't you answer to my mails regarding that topic I sent to you and the list more than two weeks ago?
Because we had some discussions on what would be the right thing to do
here and I got side-tracked by other stuff. Basically the question is
how to make it easy to, for example, use the Factory binutils sources
and build a cross package for an architecture not included in the
Factory variant. This requires that a .spec file in the cross project
can easily re-use the prep section from the Factory binutils spec file
so it doesn't require manual updating on every package update in the
Factory tree. (Note that I believe that stuffing everything back
to Factory is not the way to go) The only reasonable way to do this
seems to be to follow the trick the rpm-python spec file is using,
including a part of the rpm spec file. I wanted to try this on
avr binutils and avr gcc to see if it works out before proposing this.
For reference, rpm-python.spec looks like
Name: rpm-python
BuildRequires: python-devel
License: GNU General Public License (GPL)
Group: System/Packages
Summary: Python Bindings for Manipulating RPM Packages
Version: 4.4.2
Release: 88
Requires: rpm = %{version}
%py_requires
Source99: rpm.spec
%{expand:%(sed -n -e '/^Source:/,/^BuildRoot:/p' <%_sourcedir/rpm.spec)}
%description
...
%prep
%{expand:%(sed -n -e '/^%%prep/,/^%%install/p' <%_sourcedir/rpm.spec | sed
-e '1d' -e '$d')}
%install
...
Richard.
--
Richard Guenther
participants (5)
-
Bernhard Walle -
Ludwig Nussel -
Marcus Rueckert -
Richard Guenther -
Robert Schiele