On Wed, 2008-02-06 at 23:02 +0000, Bryce wrote:
> Just playing around with a miniature version of koji at home, building
> off my own box (i386/x86_64) using koji-1.2.5
>
> Issue 1. The kernel, because my build host is defined as arch i386,
> x86_64 when I pass a kernel build in, it passes "--target i386" which
> leads to the usual train wreck of no i386 config
> how do I pass in i686 specifically for the kernel?

You need to set the "extra arches" that a package gets built for, in
addition to the arches defined for that tag. Use:

koji set-pkg-arches "i686" dist-foo-build kernel

In Fedora Koji the i386 build builds a kernel-headers package. If
that's not working for you, you can avoid the i386 build altogether by
putting "ExcludeArch: i386" into the spec file.

> Issue 2. One of the fun items in xen is that when you're building the
> 64bit version there is an odd dependency on pulling in a 32bit
> glibc-devel by adding /usr/include/gnu/stubs-32.h to the dependency
> list, when building in x86_64 that dependancy cannot get satisfied. How
> can I beat the tag into realizing it can pull from the i386 repo to
> fulfill that requirement?

Fedora uses the glibc32 and glibc64 packages to provide these
dependencies. A bit of a hack, but it works:

http://cvs.fedoraproject.org/viewcvs/rpms/glibc32/devel/
http://cvs.fedoraproject.org/viewcvs/rpms/glibc64/devel/

Koji won't let you pull i386 packages into a x86_64 build environment,
or vice versa. The build environments are single-arch only.


--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Bryce wrote:

Issue 1. The kernel, because my build host is defined as arch i386,
x86_64 when I pass a kernel build in, it passes "--target i386" which
leads to the usual train wreck of no i386 config
how do I pass in i686 specifically for the kernel?


The arches of your host are not directly passed to mock as you suggest.

The build task will trigger builds for the arches in the archlist for
the tag that the buildroot is based on (the build tag of the target).
This list is modified in various ways.


First any extra arches for package are added. You can control extra
arches on a per-tag basis with the 'koji set-pkg-arches' command. This
is probably the solution you are looking for.


Secondly, the buildarchs, exclusivearch, and excludearch macros of the
srpm are factored in. Note that the buildarchs macro is allowed to
override the archlist, including expanding it.


Thirdly, for scratch builds, the --arch-override option to the build
command can override the arch list.


For each arch in the resulting list, a buildArch subtask is created.
This is where the arch list of a host comes into play. Note that the
arch of the task is the canonicalized, so an i686 build is an i386 task.
Hence your host with an archlist of 'i386 x86_64' will accept an i686
buildArch task.



Issue 2. One of the fun items in xen is that when you're building the
64bit version there is an odd dependency on pulling in a 32bit
glibc-devel by adding /usr/include/gnu/stubs-32.h to the dependency
list, when building in x86_64 that dependancy cannot get satisfied. How
can I beat the tag into realizing it can pull from the i386 repo to
fulfill that requirement?


Koji does not support multilib buildroots. Doing so /sanely/ is not
nearly as simple as some would suggest.


The way this is currently handled is to include a 64bit rpm that
contains this needed 32bit content. This package may need to be added to
the base install so that packages do not need to explicity require it.


$ koji latest-pkg --quiet dist-f9-build glibc32
glibc32-2.4.90-13 dist-fc6-build jkeating


--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list