[arch-multilib] Addition of jack2-multilib and multilib push perms

Ray Rashif schiv at archlinux.org
Thu Dec 8 10:05:20 EST 2011

On 8 December 2011 08:44, speps <speps at gmx.com> wrote:
> On Wed, 07 Dec 2011 15:37:09 +0100
> Thomas Bächler <thomas at archlinux.org> wrote:
>> Still another idea to think about: What about going through the whole
>> build process including --mixed, but then only packaging the 32 bit
>> libraries? Will that work as well?
> In short, nope as you intend it.

Ahh, right. I forgot that came back to the root problem again.

On 8 December 2011 08:52, Thomas Bächler <thomas at archlinux.org> wrote:
> Am 08.12.2011 01:44, schrieb speps:
>> 1. jack2:          leave as it is now
>>    jack2-multilib: build with --mixed, provides and conflicts with
>>                    jack2 and lib32-jack2
>> 2. jack2:          build with --mixed for x86_64 ([ "$CARCH" = 'x86_64' ])
>>                    removing the generated 32 bit lib from the final package
>>    lib32-jack2:    build with --mixed, removing all but the 32 bit lib
> This wouldn't work, as a pure 64 bit package must be able to build with
> core/gcc - that compiler cannot build 32 bit binaries.
>> 3. jack2:          build with a patch that just adds the -DJACK_32_64
>>                    macro in the build process without building the 32 bit lib
>>    lib32-jack2:    build with a patch the builds just the 32 bit lib
> Patching build systems is a PITA.
>> I hope I made myself clear,
> Yes, this clarifies the problem a lot. Can we add this as a huge comment
> in the PKGBUILD, please?

That makes it clearer for me too. Will definitely add some notes on
this in there.

> Btw, I enabled Ray's multilib access. As nobody objected so far, I am
> giving him a green light to implement whatever solution he sees suitable.

Thanks, I'll go with the first option.


More information about the arch-multilib mailing list