Re: amd64 packages for i386
Bastian Blank <waldi@debian.org> writes:
> On Mon, Apr 17, 2006 at 07:50:59PM +0200, Frederik Schueler wrote:
>> On Sun, Apr 16, 2006 at 02:32:12PM +0200, Bastian Blank wrote:
>> > There are two or so possibilities to do that:
>> > - Build them in the i386 build. This will raise the count of image by 4
>> > with 2.6.17.
>> If we implemented smp-alternatives with 2.6.17, we could drop the UP
>> flavours and add amd64 as subarch to i386, keeping the current count.
>
> Most subarches don't have up images.
>
>> > - Repackage the amd64 packages. This produces only network load.
>> Should be pretty simple to add at the end of the build process on amd64.
>> The old kernel-image-2.6-amd64 from sarge might contain code we could
>> recycle for this purpose.
The old sarge package did recompile the image as cross-compile with
extra x86_64-linux-* wrapers that added -m64.
With my make-kpkg patch in sid this gets simplified to "make-kpkg
--arch amd64 --cross-compile '-'" and no more wrapers.
> You want to upload amd64 and i386 packages from the amd64 buildd?
> Standard buildd will break as it expects only one entry in the
> Architecture line.
>
> Bastian
Wrong. You can perfectly well build and upload packages for multiple
archs (with the small dpkg-genchanges patch from BTS).
The problem here is the DAK: You can not upload i386 packages in 2
chunks, one from the i386 buildd, one from the amd64 buildd.
What you can do is have both i386 and amd64 build all images for both
i386 and amd64 and uploade them all together.
For maintainer uploads for i386 or amd64 this works perfectly and the
buildd would do nothing.
For maintainer uploads for other archs both i386 and amd64 buildd
would start building the kernels and one of them would get in, the
other gets aborted or rejected on upload.
MfG
Goswin
Reply to: