Re: Bulding cross-toolchains in the archive
- To: Jonathan Nieder <email@example.com>
- Cc: firstname.lastname@example.org, DrEagle <email@example.com>, firstname.lastname@example.org
- Subject: Re: Bulding cross-toolchains in the archive
- From: Goswin von Brederlow <email@example.com>
- Date: Thu, 09 Feb 2012 15:26:48 +0100
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <20120131203024.GZ10922@dream.aleph1.co.uk> (email@example.com's message of "Tue, 31 Jan 2012 20:30:24 +0000")
- References: <20120119121028.GF10922@dream.aleph1.co.uk> <CAKTje6G3QhjPpsC2Hnai2t06Z6e-WYX3440=4ewr4jsskdhV9w@mail.gmail.com> <20120123152844.GX10922@dream.aleph1.co.uk> <4F200A6B.firstname.lastname@example.org> <20120131182852.GB6128@dream.aleph1.co.uk> <20120131185534.GB12443@burratino> <20120131203024.GZ10922@dream.aleph1.co.uk>
Wookey <email@example.com> writes:
> Things are complicated in the compiler case by the continuing need for
> bi-arch toolchains for the time being. AIUI making bi-arch toolchains
> and multiarch toolchains from the same packaging is painful.
But do we actualy need them in wheezy?
I agree that we should still support "gcc -m32" but maybe that could be
done in some way that would allow using multiarch gcc / binutils with
some wrappers instead of bi-arch (multilib).
Has anyone looked into what it would take to do that?