> -----Original Message----- > From: H.J. Lu [mailto:hjl.to...@gmail.com] > Sent: Tuesday, April 03, 2012 9:11 AM > To: Kamble, Nitin A > Cc: Helmut Grohne; 667...@bugs.debian.org; Debian Bug Tracking System > Subject: Re: Bug#667037: dpkg: please add x32 abi to triplettable > > On Tue, Apr 3, 2012 at 9:08 AM, Kamble, Nitin A > <nitin.a.kam...@intel.com> wrote: > >> -----Original Message----- > >> From: H.J. Lu [mailto:hjl.to...@gmail.com] > >> Sent: Tuesday, April 03, 2012 8:35 AM > >> To: Helmut Grohne; 667...@bugs.debian.org; Debian Bug Tracking > System > >> Cc: Kamble, Nitin A > >> Subject: Re: Bug#667037: dpkg: please add x32 abi to triplettable > >> > >> On Tue, Apr 3, 2012 at 7:56 AM, Helmut Grohne <hel...@subdivi.de> > >> wrote: > >> > Package: dpkg > >> > Version: 1.16.2 > >> > Severity: wishlist > >> > Block: 667023 > >> > > >> > Dear dpkg maintainers and H.J. Lu, > >> > > >> > H.J. Lu is pushing the x32 abi into tools. His work is already > part > >> of > >> > binutils 2.22 and gcc-4.7 in Debian sid. The next step to support > >> this > >> > architecture is bootstrapping it as a Debian port for wheezy+1. In > >> > order for this to happen it would be required to add a triplet to > >> dpkg now. > >> > > >> > Debian needs a unique triplet for x32 in order to install multiple > >> > versions of libraries at the same time. Libraries are placed in > >> > /lib/$triplet (and the /usr equivalent). So i386 and amd64 > >> > libraries can be installed at the same time as /lib/i386-linux-gnu > >> > and /lib/x86_64-linux-gnu. > >> > > >> > The bad news is that such a triplet is not yet well documented and > >> > maybe not even defined. I was unable to find it. Some discussion > >> > already happend on the autoconf mailinglist[1]. But no consensus > >> seems > >> > to be reached. In theory x86_64-linux-gnu should probably have > been > >> > called x86_64-linux-gnulp indicating long pointer usage. Then the > >> > x32 triplet would be x86_64-linux-gnu. Of course this is not to > change. > >> > Following the discussion the logical outcome seems to be the > >> following proposal. > >> > > >> > triplettable > >> > - Debian triplet: x86_64-linux-gnun32 > >> > - Debian arch: x32 > >> > > >> > However x32 would have to map to x86_64 in the cputable which > poses > >> > some kind of non-uniqueness. > >> > > >> > I therefore ask H.J. Lu and the dpkg maintainers to comment on > this > >> > issue to reach a consensus. > >> > > >> > Helmut > >> > > >> > [1] > >> > http://lists.gnu.org/archive/html/autoconf/2011-10/msg00001.html > >> > > >> > > >> > >> Nitin, can you share what you use for x32 Yocto? > >> > >> Thanks. > >> > >> -- > >> H.J. > > > > > > We have gone through the decision of selecting a proper triplet for > x32 with Yocto project already. We are using x86_64-linux-gnunx32 as > triplet for x32. This also marks that there is no change in the > architecture part of the triplet, and only OS part of the triplet is > changed to denote x32 abi support. With this we are building thousands > of packages for x32. > > > > Doesn't Yocto use "x86_64-linux-gnux32", not "x86_64-linux-gnunx32"? > > > -- > H.J.
HJ, Thanks for catching the typo. We use "x86_64-linux-gnux32" Nitin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
