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

Bug#712044: marked as done (gcc-4.7: multiarch : provide cross toolchain)



Your message dated Fri, 14 Jun 2013 12:58:40 +0200
with message-id <51BAF760.40501@debian.org>
and subject line Re: Bug#712044: gcc-4.7: multiarch : provide cross toolchain
has caused the Debian Bug report #712044,
regarding gcc-4.7: multiarch : provide cross toolchain
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.)


-- 
712044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.7
Version: 4.7.3-4
Severity: wishlist

Dear Maintainer,

could it be possible to provide a gcc-amd64 (and other arch) ?
This package will install gcc under x86_64-linux-gnu-gcc (and same for
binutils).

Today there is multilib, but it is a mess with multiarch, lib are duplicated

$ dpkg -S libgcc.a
lib64gcc-4.7-dev: /usr/lib/gcc/i486-linux-gnu/4.7/64/libgcc.a
libgcc-4.8-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc.a
libgcc-4.7-dev:i386: /usr/lib/gcc/i486-linux-gnu/4.7/libgcc.a
libx32gcc-4.7-dev: /usr/lib/gcc/i486-linux-gnu/4.7/x32/libgcc.a

$ dpkg -S libc-2.17.so             
libc6:i386: /lib/i386-linux-gnu/libc-2.17.so
libc6-amd64: /lib64/libc-2.17.so
libc6-x32: /libx32/libc-2.17.so
libc6:amd64: /lib/x86_64-linux-gnu/libc-2.17.so

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.7 depends on:
ii  binutils        2.22-8
ii  cpp-4.7         4.7.3-4
ii  gcc-4.7-base    4.7.3-4
ii  libc6           2.17-5
ii  libcloog-ppl1   0.16.1-2
ii  libgcc-4.7-dev  4.7.3-4
ii  libgmp10        2:5.1.2+dfsg-1
ii  libgmpxx4ldbl   2:5.1.2+dfsg-1
ii  libmpc3         1.0.1-1
ii  libmpfr4        3.1.1-1
ii  libppl-c4       1:1.0-7
ii  libppl12        1:1.0-7
ii  zlib1g          1:1.2.8.dfsg-1

Versions of packages gcc-4.7 recommends:
ii  libc6-dev  2.17-5

Versions of packages gcc-4.7 suggests:
pn  binutils-gold        <none>
ii  gcc-4.7-doc          4.7.3-1
pn  gcc-4.7-locales      <none>
ii  gcc-4.7-multilib     4.7.3-4
pn  libgcc1-dbg          <none>
pn  libgomp1-dbg         <none>
pn  libitm1-dbg          <none>
pn  libmudflap0-4.7-dev  <none>
pn  libmudflap0-dbg      <none>
pn  libquadmath0-dbg     <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Control: tags -1 + moreinfo
thanks

Am 12.06.2013 15:18, schrieb Matthieu CASTET:
> Package: gcc-4.7
> Version: 4.7.3-4
> Severity: wishlist
> 
> Dear Maintainer,
> 
> could it be possible to provide a gcc-amd64 (and other arch) ?
> This package will install gcc under x86_64-linux-gnu-gcc (and same for
> binutils).
> 
> Today there is multilib, but it is a mess with multiarch, lib are duplicated
> 
> $ dpkg -S libgcc.a
> lib64gcc-4.7-dev: /usr/lib/gcc/i486-linux-gnu/4.7/64/libgcc.a
> libgcc-4.8-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc.a
> libgcc-4.7-dev:i386: /usr/lib/gcc/i486-linux-gnu/4.7/libgcc.a
> libx32gcc-4.7-dev: /usr/lib/gcc/i486-linux-gnu/4.7/x32/libgcc.a
> 
> $ dpkg -S libc-2.17.so             
> libc6:i386: /lib/i386-linux-gnu/libc-2.17.so
> libc6-amd64: /lib64/libc-2.17.so
> libc6-x32: /libx32/libc-2.17.so
> libc6:amd64: /lib/x86_64-linux-gnu/libc-2.17.so

there is no mess.  there is some lack of understanding on your side.  the
compiler needs to be built without any build dependencies on a foreign architecture.

Closing this issue, please see the recent discussion on debian-devel for any
additional topics and/or questions.

--- End Message ---

Reply to: