Opened 5 months ago
Closed 5 months ago
#70264 closed defect (fixed)
gcc49 @4.9.4_6 +universal: invalid command name "compiler_blacklist_versions._version_matches"
Reported by: | ar-an-ribe | Owned by: | jmroot (Joshua Root) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | Cc: | ||
Port: | gcc49 |
Description
I currently have gcc49 @4.9.4_5+universal
installed on Mavericks, and I’m trying to build gcc49 @4.9.4_6+universal
. During its configuration step, the following error is emitted:
:debug:configure Preferred compilers: clang macports-clang-16 macports-clang-15 macports-clang-14 macports-clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports-clang-9.0 macports-clang-8.0 macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 macports-clang-3.7 macports-clang-3.4 macports-gcc-13 macports-gcc-12 macports-gcc-11 macports-gcc-10 macports-gcc-9 macports-gcc-8 macports-gcc-7 macports-gcc-6 macports-gcc-5 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Executing proc-pre-org.macports.configure-configure-1 :error:configure Failed to configure gcc49: invalid command name "compiler_blacklist_versions._version_matches" :debug:configure Error code: NONE :debug:configure Backtrace: invalid command name "compiler_blacklist_versions._version_matches" :debug:configure while executing :debug:configure "$pre $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/gcc49/main.log for details.
Is this because the gcc49
compiler has been blacklisted by MacPorts, despite the presence of a newer patch? Or is this due to a problem in the Portfile
of gcc49
?
Attachments (1)
Change History (3)
Changed 5 months ago by ar-an-ribe
comment:1 Changed 5 months ago by jmroot (Joshua Root)
Looks like it's using a private procedure that used to exist in the compiler_blacklist_versions portgroup. So yes, it's a problem with the gcc49 Portfile.
comment:2 Changed 5 months ago by jmroot (Joshua Root)
Owner: | set to jmroot |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
main.log for gcc49 @4.9.4_6 +universal