[ATrpms-users] How do you build packages for i386 on x86_64?
Axel Thimm
Axel.Thimm at atrpms.net
Fri Feb 24 14:09:52 CET 2006
On Thu, Feb 02, 2006 at 12:58:09AM +0100, Joakim Verona wrote:
> Axel Thimm <Axel.Thimm at atrpms.net> writes:
>
> > On Tue, Jan 24, 2006 at 08:47:27PM +0100, Joakim Verona wrote:
> >> Axel Thimm <Axel.Thimm at atrpms.net> writes:
> >>
> >> > Since ccrma provides i386 and you need x86_64, why not build them
> >> > natively?
> >>
> >> Yes, that would be best, but it seems difficult.
> >> I tried recompiling just some things, and it took forever to figure
> >> out dependencies and compile them as well. So I gave up and decided to
> >> just build i386 packages.
> >>
> >> So, if you have some trick how to recompile all of ccrma id be very interested.
>
> Ok, what I meant was if you had some trick of compiling all the srpms
> of ccrma in the proper order, and also download whatever dependencies
> necesary for compiling, on x86_64. I understand I dont need a chroot
> for this.
No, no ordering trcik I know of, but since you have a dumb machine to
do that just try (pseudo code):
endless-loop
create repo out of built packages
foreach package try build package
Let this run a day or so and you'll have a larger part built.
> Thanks for your insights so far!
>
>
> >
> > Why recompile? You either want the x86_64 packages, which ccrma does
> > not provide, and for which you don't need a chroot, or failing that
> > you simply use the i386 packages. There is no need in recompiling the
> > i386 packages in a chroot on x86_64, the resulting packages will not
> > be better in any sense.
> >
> > Maybe you are not aware of x86_64 being able to simply use i386
> > binaries including packaged ones? I know Debian users are sometimes
> > shoked, because they haven't yet seen multilib.
>
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20060224/bd3bf7fb/attachment.bin
More information about the atrpms-users
mailing list