Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#59089 closed defect (fixed)

don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"

Reported by: rmottola (Riccardo) Owned by: jmroot (Joshua Root)
Priority: Normal Milestone: MacPorts 2.6.1
Component: base Version:
Keywords: leopard Cc:
Port:

Description

After upgrading macports to 2.6.0 on Leopard 10.5, I do run an upgrade... and it breaks

$ sudo port -v upgrade outdated
Error: Unable to open port: can't read "configure.compiler": can't read "compiler.fallback": don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Change History (11)

comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: macports removed
Summary: [macports] unable to open port compiler detection issuecompiler_blacklist_versions portgroup: don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"

The error is coming from the compiler_blacklist_versions portgroup, but that portgroup is used by many ports. Maybe a port is using it improperly. If you use the -d flag instead of the -v flag, we might get enough context to learn which port triggered this error.

comment:2 Changed 5 years ago by jmroot (Joshua Root)

Component: portsbase
Summary: compiler_blacklist_versions portgroup: don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"

comment:3 Changed 5 years ago by jmroot (Joshua Root)

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In a3a71b5b1b1f83e8cf35d45038a564906dcea8f0/macports-base (master):

Don't check the version of apple-gcc-4.2

It's provided by a port and so can be assumed to be the latest version.

Fixes: #59089

comment:4 Changed 5 years ago by jmroot (Joshua Root)

Component: baseports
Milestone: MacPorts 2.6.1

comment:5 Changed 5 years ago by rmottola (Riccardo)

I just run

port selfupdate

but the problem still appears. Does it take time or more action on my side to get your fix?

for the record:

$ sudo port -d upgrade outdated
DEBUG: epoch: in tree: 0 installed: 0
DEBUG: ccache 3.7.4_0 exists in the ports tree
DEBUG: ccache 3.7.2_0  is the latest installed
DEBUG: ccache 3.7.2_0  is active
DEBUG: Merging existing variants '' into variants
DEBUG: new fully merged portvariants: 
DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ccache
DEBUG: OS darwin/9.8.0 (macOS 10.5) arch i386
DEBUG: Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
DEBUG: Re-registering default for livecheck.regex
DEBUG: don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"
    invoked from within
"get_compiler_version ${cc}"
    (procedure "compiler.command_line_tools_version" line 3)
    invoked from within
"compiler.command_line_tools_version $c"
    (procedure "portconfigure::get_compiler_fallback" line 19)
    invoked from within
"portconfigure::get_compiler_fallback"
    invoked from within
"subst {[portconfigure::get_compiler_fallback]}"
    invoked from within
"set compiler.fallback [subst {[portconfigure::get_compiler_fallback]}]"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]"
    (procedure "default_check" line 10)
    invoked from within
"default_check compiler.fallback {} read"
    (read trace on "compiler.fallback")
    invoked from within
"set $option"
    (procedure "option" line 10)
    invoked from within
"option compiler.fallback"
    (procedure "portconfigure::configure_get_default_compiler" line 10)
    invoked from within
"portconfigure::configure_get_default_compiler"
    invoked from within
"subst {[portconfigure::configure_get_default_compiler]}"
    invoked from within
"set configure.compiler [subst {[portconfigure::configure_get_default_compiler]}]"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]"
    (procedure "default_check" line 10)
    invoked from within
"default_check configure.compiler {} read"
    (read trace on "configure.compiler")
    invoked from within
"set $option"
    (procedure "option" line 10)
    invoked from within
"option configure.compiler"
    (procedure "universal_setup" line 12)
    invoked from within
"universal_setup"
    invoked from within
"$workername eval {universal_setup}"
    (procedure "mportopen" line 54)
    invoked from within
"mportopen $porturl [array get interp_options] [array get variations]"
Error: Unable to open port: can't read "configure.compiler": can't read "compiler.fallback": don't know how to determine build number of compiler "/opt/local/bin/gcc-apple-4.2"

comment:6 Changed 5 years ago by jmroot (Joshua Root)

A new release will take a while. You could apply the change in the referenced commit to /opt/local/libexec/macports/lib/port1.0/portconfigure.tcl locally.

comment:7 Changed 5 years ago by jmroot (Joshua Root)

Component: portsbase

comment:8 Changed 5 years ago by rmottola (Riccardo)

Seems to work! I then run into other issues, but I suppose they are unrelated, I asked on the mailing list.

comment:9 in reply to:  6 Changed 5 years ago by ballapete (Peter "Pete" Dyballa)

Replying to jmroot:

A new release will take a while. You could apply the change in the referenced commit to /opt/local/libexec/macports/lib/port1.0/portconfigure.tcl locally.

What is this change? I cannot find it, or cannot that some text describes such a change.

comment:10 Changed 5 years ago by kencu (Ken)

Peter, you're enough of a hacker to know how to apply this <https://github.com/macports/macports-base/commit/a3a71b5b1b1f83e8cf35d45038a564906dcea8f0>!

comment:11 in reply to:  10 Changed 5 years ago by ballapete (Peter "Pete" Dyballa)

Replying to kencu:

Thank you, Ken! Port is building again.

Note: See TracTickets for help on using tickets.