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

Bug#666743: marked as done (gcc-4.6: please provide a multiarch:foreign compiler interface)

Your message dated Fri, 21 Aug 2015 13:43:08 +0000
with message-id <[🔎] E1ZSmb6-0004jv-26@franck.debian.org>
and subject line Bug#796274: Removed package(s) from unstable
has caused the Debian Bug report #666743,
regarding gcc-4.6: please provide a multiarch:foreign compiler interface
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.)


-- 
666743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666743
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcc-4.6
Version: 4.6.3-1
Severity: wishlist

Dear gcc maintainers,

Motivation
~~~~~~~~~~
I would like to install ghc:i386 and gcc:amd64. Currently this is not
possible, because ghc depends on gcc and gcc is not multiarch:foreign
(which is correct of course). So can this work at all? I believe yes.
What ghc:i386 really wants is a C compiler producing i386 binaries and
such a compiler exists (gcc -m32).

Solution
~~~~~~~~
The gcc -m32 syntax is in no way generic (like /lib32 wasn't), but there
exists a generic syntax employing architecture triplets. For instance
gcc can be invoked as x86_64-linux-gnu-gcc on amd64. Other flavours such
as x86_64-w64-mingw32-gcc (gcc-mingw-w64) already exist. It would only
be natural to provide i386-linux-gnu-gcc (on amd64) as well. There would
have to be a multiarch:foreign package that can be depended upon (maybe
called gcc-i386?). With n architectures this would result in n^2 binary
packages (one for each host and target architecture combination).
ghc:$host would have to switch its dependency to gcc-$host. In addition
this change should make cross compilation radically easier.

I am aware that this task is huge. Is this feature worth the effort? Is
the drafted solution applicable? Are there other prerequisites needed
before changes to the gcc packages can be done?

Thanks for considering

Helmut

--- End Message ---
--- Begin Message --- 
Version: 4.6.4-7+rm

Dear submitter,

as the package gcc-4.6 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/796274

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: