Re: Issues with trying to build Debian x32 gcc with multilib support
On 21.08.2012 06:51, Daniel Schepler wrote:
> OK, I've gotten it working now. The issue was that I hadn't added x32
> to biarch64 or biarch32, so biarch_multidir_names was never being set.
> (I also added x32 to the multilib dirs that get filtered in
> ml-config.diff, since that's what pointed me to the problem.)
>
> On Mon, Aug 20, 2012 at 5:36 AM, Matthias Klose <doko@debian.org> wrote:
>> On 17.08.2012 18:12, Daniel Schepler wrote:
>>> On a side note, instead of adding libx32gcc1 etc.,
>>
>> I don't like the idea of having to cros-build-depend on other architectures, so
>> as a first step, I'd like to see these packages built.
>
> Neither do I -- but I also don't like the idea of [e]glibc having to
> keep cross-building libraries purely for the use of gcc builds.
No. the multilib configurations are used for more than that. No, not for package
builds.
> And IMO all other Debian package uses of gcc-multilib and libc6-dev-*
> should go away during the next release cycle in favor of multiarch (at
> least I can't think of anything else where it's justified).
No. They should stay, to build a multilib'ed compiler. And I won't apply any
local patch to the gcc package to lookup header and o files in other places, so
if you want to improve the situation, work with upstream to get this into the
next GCC release.
Matthias
Reply to: