[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Building dual-arch RPMs



On Mon, 2006-03-06 at 21:37 +0100, Jos Vos wrote:
> On Mon, Mar 06, 2006 at 01:44:08PM -0500, Ralph Smith wrote:
> 
> > For some reason the target option of rpmbuild does not correctly set
> > all of the rpm macros correctly.  I have found that some packages like
> > this can be built (on an x86_64 system for i386 target, presumably
> > similar to your case) if a line
> > 
> > %define _lib lib
> > 
> > is inserted near the top of the spec file.  (_lib is set to lib64
> > on 64-bit systems even when building 32-bit.) That should fix the
> > particular error you found for "target ppc".  Perhaps an RPM guru
> > can tell us (and redhat) where this really should be set.
> 
> Is building i386 RPMs on x86_64 (for example) supported at all?
> Won't for example several configure scripts work incorrectly anyway?

The only way I see this work correctly is to have a chroot (or virtual
machine) that is i386 only on an X86_64 machine.  You can then use it to
build i386 packages, if you use the "setarch i386" and have only i386
packages in the chroot.

> 
> The other way around, even building "just" x86_64 on x86_64 fails in
> several cases when multiple instances (i386 and x86_64) of some lib
> packages are installed.
> 

Also true, the only i[3,4,5,6]86 packages that should be installed to
build good x86_64 packages are glibc.i686 and glibc-devel.i386 ... only
x86_64 packages other than those 2 should be installed.

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]