* the qmake tool (part of QT) thinks s390x and ppc64 are of "linux-g++-64" type while x86_64 is "linux-g++" type

* the qmake tool (part of QT) thinks s390x and ppc64 are of "linux-g++-64" type while x86_64 is "linux-g++" type

−

== Please make sure to build into the correct target, don't mix dist-f14 and dist-f14-updates ==

+

== Submitting builds ==

+

There should be no need for a maintainer to do a regular build, they are automagically processed through the koji-shadow script that reads all builds from primary koji and rebuilds them in proper order.

To test a build for your specific package for s390x do this:

To test a build for your specific package for s390x do this:

−

After running <code>fedora-packager-setup</code> from the <code>fedora-packager</code> rpm

+

After running <code>fedora-packager-setup</code> from the <code>fedora-packager</code> rpm do

−

+

−

<code>s390-koji build --scratch dist-f14 yourpkg.src.rpm</code>

+

−

To build a package which should end up in the F-14 tree, the package needs to be commited in dist-git and then be built with:

History

FUDcon 2008 was an excellent event. During the conference, a session on secondary arches was presented and there was an excellent effort made to reach out to new arches.

After several months of bootstrapping as of June 2009 we've reached a state where we have most packages built from current Fedora rawhide CVS. There are still around ~500 failures, most of which are related to java and ocaml dependencies (ocaml is not available on s390x).

News of September 2010: We're now getting really close to Rawhide and we have a working install tree available thats basically based on current Fedora 14. Previously we only provided a hercules images as well as a tarball from a root FS as installs weren't possible. We still provide those, but now you can do your own installs again, too!

For those interested in trying it out you access everything needed from here:

size_t is alias for unsigned long on s390, so the assumption size_t == unsigned int fails here, seen in C++ code using templates

s390 (31-bit) arch has 2 GB address space and it can be too small when building large C++ applications with debug information enabled, such builds can fail in the final link with errors like "Final link failed: exhausted memory" => the workaround is to disable debug information (remove -g from CXXFLAGS)

xmlto needs w3m to fullfil the dependency on text-www-browser instead of lynx, otherwise it fails on empty file (seen in libXest, libSM, libXtst)

sometimes wrong package is selected to fulfill a BuildRequires when multiple packages provide the name

the qmake tool (part of QT) thinks s390x and ppc64 are of "linux-g++-64" type while x86_64 is "linux-g++" type

Submitting builds

There should be no need for a maintainer to do a regular build, they are automagically processed through the koji-shadow script that reads all builds from primary koji and rebuilds them in proper order.

To test a build for your specific package for s390x do this:

After running fedora-packager-setup from the fedora-packager rpm do

* s390-koji build --scratch f21-candidate yourpkg.src.rpm

If you are unsure what do do, please contact the team.

Tracker Bugs

If excluding s390/s390x architectures you need to make the bug block F-ExcludeArch-s390x