Bug#667023: src:eglibc: please provide a binary package for the x32 sub architecture on amd64

2012-04-03 Thread Helmut Grohne
Package: src:eglibc
Version: 2.13-27
Severity: normal
Tags: upstream
Blocks: 667005

gcc-4.7 and binutils (2.22) already provide support for the x32 abi. The
missing piece to producing x32 binaries is a c library. Patches are
available at git://github.com/hjl-tools/glibc.git. An aspect that makes
supporting x32 more difficult is that glibc is currently compiled using
gcc-4.4 whereas the x32 abi requires at least gcc-4.7. Switching
compiler version is not a lightly taken decision and especially not this
late in the freeze process. I estimate the diff between 2.13 and
2.13+x32 to be around 202 files changed, 3967 insertions, 218 deletions,
and 568 modifications.

Due to the ongoing multiarch transition another question should be
asked: Should the new package be libc6-x32:amd64 or libc6:x32?

Helmut



-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120403130210.GA17099@localhost



Bug#667023: src:eglibc: please provide a binary package for the x32 sub architecture on amd64

2012-04-03 Thread Aurelien Jarno
Le 03/04/2012 15:02, Helmut Grohne a écrit :
 Package: src:eglibc
 Version: 2.13-27
 Severity: normal
 Tags: upstream
 Blocks: 667005
 
 gcc-4.7 and binutils (2.22) already provide support for the x32 abi. The
 missing piece to producing x32 binaries is a c library. Patches are
 available at git://github.com/hjl-tools/glibc.git. An aspect that makes
 supporting x32 more difficult is that glibc is currently compiled using
 gcc-4.4 whereas the x32 abi requires at least gcc-4.7. Switching
 compiler version is not a lightly taken decision and especially not this
 late in the freeze process. I estimate the diff between 2.13 and
 2.13+x32 to be around 202 files changed, 3967 insertions, 218 deletions,
 and 568 modifications.

This is not possible until gcc provide libgcc in x32 version. There is
kind of a deadlock there.

 Due to the ongoing multiarch transition another question should be
 asked: Should the new package be libc6-x32:amd64 or libc6:x32?

I don't think we should add yet another bi-arch package, but go for a
new architecture, so libc6:x32. Anyway /lib32 is already taken by i386
on amd64, so it's not possible to install x32 in this directory.

The best way to have that is therefore to start a new x32 architecture,
but that's clearly too late for wheezy.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net



-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f7afaa2.4070...@aurel32.net