On Thu, Jun 9, 2011 at 10:52 PM, Martin Langhoff <[email protected]> wrote: > Hi Daniel, Peter, list > > I am wondering how we can teach imgcreator about our ARM arch, so that > it can build an image with some arm5tel packages and some armv7l > packages (such as the kernel).
If we do something like run imgcreator as armv7l it should just work, this might not work if its run on koji2/koji3 due to them only being v5tel > Today I discovered that rpm itself is complaining about installing a > kernel armv7l package -- in a lousy hack in a preimage script, > probably because uname reports that the (build)host is arm5tel. We'll > probably have to teach rpm about this as well. I've had issues like that in the past when we had issues with the XO-1 where I had to use --ignorearch but from mem it uses one of the args from uname -a to check arch. Although if your building it on koji2/koji3 which is arm5tel that might cause issues as well. > Do you know where and how rpm, yum and imgcreator keep track of arches > and subarches? rpm already knows about this, there's a series of inheritance that you setup. Its contained in the redhat-rpm-config package. In particular the /usr/lib/rpm/rpmrc file (search for arch_compat). But the arm section currently looks like this: arch_compat: armv4b: noarch arch_compat: armv7l: armv6l arch_compat: armv6l: armv5tejl arch_compat: armv5tejl: armv5tel arch_compat: armv5tel: armv4tl arch_compat: armv4tl: armv4l arch_compat: armv4l: armv3l arch_compat: armv3l: noarch Peter _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
