[arch-multilib] Developer tools

[Pierre Schmitz]

On Wed, 25 Aug 2010 22:56:33 +0200, Jan Steffens
<jan.steffens at gmail.com> wrote:
> On Wed, Aug 25, 2010 at 7:13 PM, Rémy Oudompheng
> <remyoudompheng at gmail.com> wrote:
>> May I suggest the following changes ? They make more sense for
>> using multilib-build. For example, packages from [multilib] should
>> be installed when available, not packages from [community]
>> (multilib must come first in pacman.conf).
> 
> I already talked to Pierre about this. Should be irrelevant, since
> there's no intersection between [community] and [multilib] (once we
> remove the lib32 stuff from [community].
> 
> gcc-multilib should of course be installed into the multilib root. I
> support that. :)

I'll release a new devtools package soon. If your package needs the
multilib gcc to be build it should be put into makedepends. (Or create a
group like base-devel-multilib which I could install into the chroot in
addition to base and base-devel; though I don't know if pacman can
handle the conflict between gcc and gcc-multilib.

-- 
Pierre Schmitz, https://users.archlinux.de/~pierre