Opened 6 years ago
Closed 3 years ago
#57098 closed defect (fixed)
problem upgrading ast
Reported by: | mfacorcoran | Owned by: | lpsinger (Leo Singer) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | ast |
Description
I get the following error at the configure stage when trying to upgrade ast:
[% sudo port upgrade ast Password: ---> Computing dependencies for ast ---> Configuring ast Error: Failed to configure ast, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_science_ast/ast/work/ast-8.6.2/config.log Error: Failed to configure ast: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_github.com_macports_macports-ports_science_ast/ast/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug.
I've attached the log file. I've got
ast @8.6.1_0+gcc6 (active)
and I believe the upgrade is to ast @8.6.2
cheers
Mike
Attachments (2)
Change History (6)
Changed 6 years ago by mfacorcoran
Attachment: | config.log added |
---|
comment:1 Changed 6 years ago by mf2k (Frank Schima)
Cc: | leo.singer@… removed |
---|---|
Owner: | set to lpsinger |
Port: | ast added; astropy removed |
Status: | new → assigned |
comment:2 follow-up: 3 Changed 6 years ago by mf2k (Frank Schima)
Changed 6 years ago by mfacorcoran
comment:3 Changed 6 years ago by mfacorcoran
comment:4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Years have passed, and we currently have successful builds of ast @9.0.1 on our automated build system on all macOS versions from 10.6 through 12 inclusive with whatever the default gcc variant is on each OS version, so I am assuming and hoping the problem you experienced got fixed somewhere along the way. If you still see the problem, please reopen the ticket and let us know.
Note: See
TracTickets for help on using
tickets.
Please attach the main.log file so we can see the error.