On Oct 7, 2010, at 9:51 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Oct 7, 2010 at 10:00 PM, Brad Fanella <bradfanella@archlinux.us
wrote: On Tue, Oct 5, 2010 at 7:39 PM, Eric Bélanger <snowmaniscool@gmail.co m> wrote:
I believe he wants you to add x86_64 support to the chuck PKGBUILD in community. See how it's done for skype. Just commit the change to the PKGBUILD in trunk and he'll build it (I guess).
Eric
That doesn't seem right... If anyone wants a working PKGBUILD, simply use bin32-chuck PKGBUILD that SpepS was nice enough to write up. [1].
I don't understand how we can add x86_64 support to chuck as both lib32-gcc-libs and lib32-libsndfile are dependencies.
[1] http://aur.pastebin.com/TdDUYhD4
Truly sorry if I am missing something here.
Thanks a ton, Brad
Did you checked how it's done for skype or wine? Use conditional statements:
if [[ $CARCH == i686 ]]; then depends=('gcc-libs' 'libsndfile') else depends=('lib32-gcc-libs' 'lib32-libsndfile') fi
and so on.
_______________________________________________ arch-multilib mailing list arch-multilib@archlinux.org http://mailman.archlinux.org/mailman/listinfo/arch-multilib
_______________________________________________ arch-multilib mailing list arch-multilib@archlinux.org http://mailman.archlinux.org/mailman/listinfo/arch-multilib
Yep. That's exactly how I did it. Sorry 'bout that. I wasn't thinking straight. I took a look at the lib32 dependencies and automatically assumed that it needed to be placed into multilib' completely disregarding the fact that they are simply build-time dependencies. Thanks, Brad