#36147 closed defect (invalid)
upgrade of gcc46 fetches gcc47??
Reported by: | bcbarnes@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
Port: | gcc46 |
Description
I was upgrading outdated ports this morning and encountered the following:
$ port installed | grep gcc46 gcc46 @4.6.3_4 (active) $ sudo port -u -c upgrade gcc46 Password: ---> Computing dependencies for libstdcxx ---> Fetching distfiles for libstdcxx ---> Attempting to fetch gcc-4.7.1.tar.bz2 from ftp://ftp.gnu.org/gnu/gcc/gcc-4.7.1 ^C $ port info gcc46 gcc46 @4.6.3, Revision 7 (lang) $ port info libstdcxx libstdcxx @4.7.1, Revision 101 (lang)
I noticed the latest series of changes to the gcc46 port were libstdcxx related. Is this behavior expected? Downloading gcc 4.7 in order to upgrade the gcc 4.6 port? It seems...wrong. OS X 10.8.1, Xcode 4.4.1, etc.
Change History (2)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
We're using the "newest" runtime among stable gccs to provide a common libstdc++ runtime for all gccs. This allows one to mix code built with the different compilers (although you still can't mix code between these g++ compilers and clang++ / the system compilers).
Note: See
TracTickets for help on using
tickets.
The gcc46 port (and the other gcc ports) now require the libstdcxx port. The libstdcxx port currently uses a gcc47 distfile. So this is nothing to be alarmed about.