[Bug 992217] Re: command-not-found suggests gcc-mingw-w64 instead of the correct g++-mingw-w64-i686 to provide the "i686-w64-mingw32-g++" command

Stephen Kitt steve at sk2.org
Thu May 3 04:37:16 UTC 2012


Micah, that's more or less what I'm thinking, not a separate
transitional binary package since gcc-mingw-w64 still exists, but making
gcc-mingw-w64 recommend the various other compiler packages which used
to be part of it (so g++-mingw-w64, gfortran-mingw-w64 and gnat-
mingw-w64). Would that be sufficient? I'd rather avoid having a strong
dependency since the whole point of the split was to allow users to only
install the compilers they actually want...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/992217

Title:
  command-not-found suggests gcc-mingw-w64 instead of the correct
  g++-mingw-w64-i686 to provide the "i686-w64-mingw32-g++" command

Status in “command-not-found” package in Ubuntu:
  New
Status in “gcc-mingw-w64” package in Ubuntu:
  New

Bug description:
  In 64bit oneiric was present 32 mingw-w64 C++ compiler (binary
  i686-w64-mingw32-g++) in package gcc-mingw-w64. But in precise is
  32bit cross compiler missing. What happened? Why was C++ compiler
  removed? Can you add it back? Note that both 32 and 64 bit versions of
  C compiler is included in precise (i686-w64-mingw32-gcc and
  x86_64-w64-mingw32-gcc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/992217/+subscriptions




More information about the foundations-bugs mailing list