On Fri, Feb 04, 2005 at 04:14:55PM +0100, Toralf Lund wrote: > Jeff Johnson wrote: > > >On Mon, Jan 31, 2005 at 02:53:08PM -0700, Bryan Stillwell wrote: > > > > > >>Is there any way to have a spec file build an rpm for two separate > >>architectures with just the `rpmbuild -bb` command? > >> > >>As an example, if I had a helloworld program written in C, and wanted it > >>to build on x86_64 on i386, how would I do that? > >> > >>I figure in the build section I would have to build it twice with these > >>two commands: > >> > >> x86_64: gcc helloworld.c -o bin64/helloworld > >> i386: gcc -m32 helloworld.c -o bin32/helloworld > >> > >>What I'm imagining is the build would take place, then the final lines > >>would look like: > >> > >>Wrote: /home/build/rpm/RPMS/x86_64/helloworld-1.0-1.x86_64.rpm > >>Wrote: /home/build/rpm/RPMS/i386/helloworld-1.0-1.i386.rpm > >>Wrote: /home/build/rpm/RPMS/noarch/helloworld-docs-1.0-1.noarch.rpm > >> > >>Any ideas on how to make this happen? > >> > >> > > > >Add --target arch1,arch2,arch3,arch4 > > > >Note that these are sequential builds, not multiple arches in one build. > > > >The design goal in rpm is > > One value of arch is static throughout a build. > > > > > So, to repeat one of my questions from elsewhere on this branch: Does > that mean there is no way to ask for more than one output architecture > via spec file tags or macros instead of command line options? I wouldn't > want those to give multiple archs in one build, either, but rather > request multiple builds from within, of you know what I mean. Yes, no way, by design: Only one static arch value per build. Loop on the build, either external to rpmbuild, or with --target if you must. External loop is perhaps more flexibly configured than the internal --target loop. 73 de Jeff -- Jeff Johnson ARS N3NPQ jbj@xxxxxxxxxx (jbj@xxxxxxx) Chapel Hill, NC _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
