Opened 9 months ago
Last modified 9 months ago
#67892 new defect
xfconf @4.16.0 failed to compile on Ventura arm64, and a potential workaround
| Reported by: | philberthfz (Philip LeBlond) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | arm64 ventura, | Cc: | barracuda156 |
| Port: | xfconf |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
There are no compiled binary packages for xfconf available yet. When macports attempts to compile, compilation fails with the message:
Error: Failed to configure xfconf: configure failure: command execution failed.
It appears that the configuration step fails to run aclocal at the appropriate point.
I have identified a possible workaround, and am sharing it here in the hopes that I will be able to find it on google the next time I inevitably need to do this again. Given that the package itself appears unmaintained, consider this a best-effort workaround for anybody else pulling their hair out over this and that further problems will probably continue to exist. Consider also that I have sample size of exactly one install on one M1 Mac mini, so users on other machines with other software configurations will undoubtably encounter other issues - your mileage will vary.
Doing the following produced a probably-functional copy of xfconf for me:
- Manually navigating to the appropriate work directory (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_xfce_xfconf/xfconf/work/xfconf-4.16.0)
sudo aclocalsudo /opt/local/bin/xdt-autogen --prefix=/opt/local --disable-visibilitysudo make && sudo make installsudo port -f activate xfconf
At least, this appears to generate a working xfconf. At the very least, other packages which depend on xfconf will build/install with no more errors than they otherwise would exhibit.
Change History (1)
comment:1 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | barracuda156 added |
|---|---|
| Description: | modified (diff) |
| Keywords: | ventura added; M1 apple silicon Ventura removed |
| Priority: | Low → Normal |
| Summary: | xfconf failed to compile on Ventura arm64, and a potential workaround → xfconf @4.16.0 failed to compile on Ventura arm64, and a potential workaround |
Thanks for the tip on getting it working.
It might be helpful it you attached a log showing what the problem was.
You should basically never need to force a port to activate.
As you know, this port is unmaintained. If you can provide a fix, please file a pull request.
This port, and the rest of xfce, should be updated to the latest stable versions (4.18.x). Maybe that will already fix the problem you saw.