[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#747933: marked as done (libc6-dev: should enhance (not recommend) compiler)

Your message dated Sat, 16 Aug 2014 00:19:23 +0200
with message-id <20140815221923.GB22823@hall.aurel32.net>
and subject line Bug#747933: fixed in glibc 2.19-8
has caused the Debian Bug report #747933,
regarding libc6-dev: should enhance (not recommend) compiler
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
747933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747933
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-dev
Version: 2.18-4
Severity: normal

Hi. Currently the libc6-dev package is

 Recommends: gcc | c-compiler

This is fine with native compilers. However, if I'm on an amd64 host,
and I try to install libc6-dev:armel with intent to use it with a
cross-compiler that targets armel, this recommendation is wrong.

By default, apt wants to install the Recommends, so if using aptitude to
install libc6-dev:armel, aptitude will try to install gcc:armel, which
clashes with gcc:amd64, since gcc is not Multi-Arch:same. Aptitude then
really tries to make that work by proposing to remove gcc in various
ways. You have to resolve this manually. This is arguably a deficiency
in aptitude, but maybe this Recommends can be loosened.

I don't believe Debian has any way to specify a Multi-Arch:foreign
virtual package (so the cross-compiler can't satisfy the c-compiler part
of this). Can we downgrade this Recommends to a Suggests, or maybe
remove it entirely? The user who installs libc6-dev likely already has a
compiler, and doesn't really benefit from this Recommends.

--- End Message ---
--- Begin Message --- 
Source: glibc
Source-Version: 2.19-8

This bug has been closed in glibc version 2.19-8. Here is the full
changelog:

glibc (2.19-8) unstable; urgency=medium

  [ Helmut Grohne ]
  * debian/patches/build stage2 without selinux.  Closes: #742640.
  * Don't emit dependencies on libgcc when building stage2.  Closes: #755580.
  * Add a "nobiarch" build profile that inhibits all multilib packages from
    being built.  Closes: #745380.

  [ Aurelien Jarno ]
  * debian/patches/arm64/cvs-includes-cleanup.diff: new patch from upstream to
    clean sys/user.h and sys/procfs.h.  Closes: #755169.
  * debian/patches/s390/cvs-s390-abi-reversal.diff: new patch backported from
    upstream to revert the S/390 jmp_buf/ucontext_t ABI change.
  * Update Turkish debconf translation, by Mert Dirik.  Closes: #757495.
  * Remove ia64 support.  Closes: #756095.
  * Update debian/copyright with the libidn/punycode.{c,h} license.  Closes: 
    #754731.
  * debian/control/libc: drop Recommends on: gcc | c-compiler.  Closes:
    #747933.

 -- Aurelien Jarno <aurel32@debian.org>  Thu, 14 Aug 2014 15:54:09 +0200

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: