Re: Bug#246547: amd64 support for glibc 2.3.2.ds1-14
Hi Andreas,
At Mon, 5 Jul 2004 13:31:38 +0200,
Andreas Jochens wrote:
> The attached patch does the following:
>
> * Add amd64 at the appropriate places in debian/control,
> debian/rules.d/control.mk and debian/control.in/libc6.
> Add debian/patches/amd64-lib.dpatch to disable the biarch
> lib64 dir on amd64 and enable this patch in debian/patches/00list.
> (Closes: #246547)
> * Add a new file debian/sysdeps/amd64.mk with GLIBC_PASSES += nptl
> (Closes: #248192)
Cool. I'll put them into cvs. I succesfully built it. But I
unfortunatelly have no chroot on amd64, so I didn't test it yet.
Please test this version:
http://www.gotom.jp/~gotom/debian/glibc/amd64
The result of log-test-x86_64-linux-libc failed at two: grp/testgrp,
posix/annexc. But it's environment setting problem, not glibc
problem. However one test in log-test-x86_64-linux-nptl failed at:
elf/tst-tls10. I'm investigating it.
BTW, is this dpatch written by only you? I need to describe the
appropriate changelog entry with author's name.
> * Modify debian/rules to use gcc instead of gcc-3.3 on amd64.
It should be put into amd64.mk instead of debian/rules. I modified
debian/sysdeps/amd64.mk like:
CC = gcc
BUILD_CC = gcc
GLIBC_PASSES += nptl
> Add [!amd64] to the Build-Depends on gcc-3.3 in debian/control.
> This will make it possible to build glibc with gcc-3.4
> when gcc-3.4 becomes the default on amd64 without changing glibc again.
> (The amd64 archive will likely be recompiled with gcc-3.4 entirely
> and gcc-3.4 will become the default on amd64
> because gcc-3.4 has much better support for amd64.)
We need to avoid using gcc-3.2 and below because it does not support
TLS and so on. I know amd64 does not have gcc-3.2, but I think adding
Build-Depends: gcc-3.3 | gcc-3.4 is appropriate for future
development. I put this modification to debian/control.in/main. I
also updated debian/control.
> I am also working on building a 32bit i386-libc package on amd64
> (by adding an 'i386' pass to GLIBC_PASSES in debian/sysdeps/amd64.mk)
> to make it possible to build a gcc with multilib support and to allow
> the easy compilation of 32bit programs using '-m32' on amd64.
It looks nice.
> However, this will need an updated linux-kernel-headers package
> which includes the i386 kernel headers (see #252720) and some
> changes in the gcc package which have not been sufficiently tested yet.
Updating linux-kernel-headers is no problem. We're ready to put it
into sid/sarge anytime.
BTW, I concerned gcc multilib + gcc 3.4 support. This may be not
happened in sarge. I wait to put the modification of #252720 until
the request is come. If we want to release sarge soon, and if we want
to put amd64 into sarge, then it's good idea to keep gcc 3.3, IMHO.
What's the merit of pushing gcc 3.4 into sarge on amd64?
Regards,
-- gotom
Reply to: