Opened 7 weeks ago

Last modified 7 weeks ago

#59377 assigned defect

xorg-xorgproto @2019.2: Failed to configure on macOS 10.15

Reported by: haberg-1 Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: catalina Cc: cjones051073 (Chris Jones), jmroot (Joshua Root)
Port: xorg-xorgproto

Description (last modified by jmroot (Joshua Root))

MacOS 10.15:

Error: Failed to configure xorg-xorgproto, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_xorg-xorgproto/xorg-xorgproto/work/xorgproto-2019.2/config.log
Error: Failed to configure xorg-xorgproto: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_xorg-xorgproto/xorg-xorgproto/main.log for details.
Error: Unable to execute port: upgrade py37-pyqt5 failed

Attachments (1)

config.log (58.2 KB) - added by haberg-1 7 weeks ago.
config log

Download all attachments as: .zip

Change History (11)

Changed 7 weeks ago by haberg-1

Attachment: config.log added

config log

comment:1 Changed 7 weeks ago by jmroot (Joshua Root)

Cc: cjones051073 jmroot added
Description: modified (diff)
Owner: set to jeremyhu
Status: newassigned
Summary: MacOS 10.15: Failed to configure xorg-xorgprotoxorg-xorgproto @2019.2: Failed to configure on macOS 10.15
config.status:896: creating applewmproto.pc
config.status:1048: error: could not create applewmproto.pc

Well that's not the most helpful error message. The config.status line printing the error seems to be:

eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \
  >$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5

I can't reproduce the issue on Mojave.

comment:2 Changed 7 weeks ago by cjones051073 (Chris Jones)

I've had no issue either with this update, on two 10.15 machines and one running 10.13.

comment:3 Changed 7 weeks ago by jmroot (Joshua Root)

Is gawk working for you in general? Any difference if you deactivate it, clean xorg-xorgproto, and try again?

comment:4 Changed 7 weeks ago by cjones051073 (Chris Jones)

Not sure if you directed that at me or the OP, but I did not have the gawk port installed previously on the 10.15 machines. However, installing it, and then forcibly rebuilding and installing xorg-xorgproto worked fine also.

comment:5 Changed 7 weeks ago by haberg-1

FYI, the error arrived after

port install frescobaldi-devel

So you might try that.

comment:6 Changed 7 weeks ago by haberg-1

Also, xorg-server was successfully installed before, which also depends on xorg-xorgproto.

comment:7 Changed 7 weeks ago by haberg-1

One can deactivate gawk and get further with xorg-xorgproto, but then 'port install xorg-libX11' fails.

comment:8 Changed 7 weeks ago by haberg-1

Now I get error on port install libxml2, the log file starts with ":debug:sysinfo macOS 10.15 (darwin/19.0.0) arch i386", and i386 is not supported on MacOS 10.15:

-->  Computing dependencies for libxml2
--->  Fetching archive for libxml2
--->  Attempting to fetch libxml2-2.9.9_3.darwin_19.x86_64.tbz2 from https://packages.macports.org/libxml2
--->  Attempting to fetch libxml2-2.9.9_3.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/libxml2
--->  Attempting to fetch libxml2-2.9.9_3.darwin_19.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libxml2
--->  Building libxml2
Error: Failed to build libxml2: command execution failed
Last edited 7 weeks ago by jmroot (Joshua Root) (previous) (diff)

comment:9 Changed 7 weeks ago by cjones051073 (Chris Jones)

Please do not mix up tickets with reports for multiple ports. If you have an issue with libxml2, submit a new ticket for that, and *always* include a complete log from a clean build attempt. The above messages tell us nothing.

comment:10 Changed 7 weeks ago by haberg-1

It seems that the whole installation is broken, so it probably must be removed and reinstalled.

Note: See TracTickets for help on using tickets.