Re: Error installing Kampose
On Oct 28, 2022, at 12:23, James McManus wrote: > However, I am still not able to install Kompose. I'm still getting the not a > git repository error message: > > :info:build Executing: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/github.com/kubernetes/kompose" > && make -j8 -w bin > :debug:build system: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/github.com/kubernetes/kompose" > && make -j8 -w bin > :info:build fatal: not a git repository (or any of the parent directories): > .git > :info:build make: Entering directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_kompose/kompose/work/gopath/src/github.com/kubernetes/kompose' > > The directory path listed above does exist. But presumably the directory is not a git repository. And that may be fine. I would ignore this "fatal" error and look for the next error after this. > The I'm also getting a build error: > > :info:build > ../../../../pkg/mod/golang.org/x/sys@v0.0.0-20201029080932-201ba4db2418/unix/zsyscall_darwin_amd64.go:121:3: > too many errors The relevant error will be before this line, possibly significantly before. Usually the relevant error is the first error in the extract or patch or configure or build or destroot phase, except that in this case I think you can ignore the message about not being a git repository since, if that were required, the port would have been programmed to accomplish that. On Oct 28, 2022, at 16:25, James McManus wrote: > The first errors in the log 404 errors: > > :msg:archivefetch ---> Fetching archive for kompose > :debug:archivefetch Executing org.macports.archivefetch (kompose) > :debug:archivefetch euid/egid changed to: 0/0 > :debug:archivefetch chowned /opt/local/var/macports/incoming to macports > :debug:archivefetch euid/egid changed to: 503/501 > :info:archivefetch ---> kompose-1.24.0_0.darwin_22.x86_64.tbz2 doesn't seem > to exist in /opt/local/var/macports/incoming/verified > :msg:archivefetch ---> Attempting to fetch > kompose-1.24.0_0.darwin_22.x86_64.tbz2 from > https://packages.macports.org/kompose > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 You can ignore archive fetch failures. They indicate that a pre-compiled archive was not found. No problem; it will be compiled from source on your system. We have not created any pre-compiled archives for macOS Ventura yet. As you can see it's not always straightforward to determine what the relevant error is, so I recommend when you encounter a port that doesn't install you just file a bug report in our issue tracker and attach the log, and someone else can look at the log and determine what the problem is.
Re: macports-users Digest, Vol 194, Issue 22
On Oct 29, 2022, at 07:50, Artemio González López wrote: > > Error: Failed to activate py310-jupyter: Image error: > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/__pycache__/jupyter.cpython-310.pyc > is being used by the active py310-jupyter_core port. Please deactivate this > port first, or use 'port -f activate py310-jupyter' to force the activation. > > Should I deactivate py310-jupyter_core, activate py310-jupyter, and activate > py310-jupyter_core, or is it better to just force activation of py310-jupyter > … or none of the above? Force-activating ports is not recommended. You should probably wait for the maintainer of the port to resolve the conflict, which I see you have reported at https://trac.macports.org/ticket/66124. Or anyone else can feel free to solve it and submit a pull request.
Re: Texmaker installation failed due to inability to build qt5 web engine
On Nov 4, 2022, at 07:03, Chris Jones wrote: > Just on this point, if you don't want to have to build everything from > source, then you should not update your OS before MacPorts has deployed > buildbots for the new OS. You can check this at e.g. > > https://build.macports.org/waterfall > > and yes we do not yet have macOS13 in place. Ryan might be able to give an > idea of a timeline for this. I can't give you any timeline yet.
Re: Libomp notes
On Nov 4, 2022, at 11:49, John Wiggins wrote: > I am running macOS Monterey 12.6.1 and updated Xcode and CLT to 14.1. > When I “upgrade outdate” I get note concerning libomp: > > … >> ---> Some of the ports you installed have notes: >> libomp has the following notes: >> To use this OpenMP library: >> * For clang-3.8+, or clang-3.7 with +openmp variant: >>add "-fopenmp" during compilation / linking. >> * For clang-3.7 without +openmp variant, use: >>"-I/opt/local/include/libomp -L/opt/local/lib/libomp -fopenmp" >> libpsl has the following notes: >> libpsl API documentation is provided by the port 'libpsl-docs’. > > > There any action required of me? The note is advising you how to use libomp in your own projects. If you aren't using libomp in your own projects you can disregard the message.
Libomp notes
I am running macOS Monterey 12.6.1 and updated Xcode and CLT to 14.1. When I “upgrade outdate” I get note concerning libomp: … > ---> Some of the ports you installed have notes: > libomp has the following notes: > To use this OpenMP library: > * For clang-3.8+, or clang-3.7 with +openmp variant: > add "-fopenmp" during compilation / linking. > * For clang-3.7 without +openmp variant, use: > "-I/opt/local/include/libomp -L/opt/local/lib/libomp -fopenmp" > libpsl has the following notes: > libpsl API documentation is provided by the port 'libpsl-docs’. There any action required of me? It seems to not apply as: > $ clang --version > Apple clang version 14.0.0 (clang-1400.0.29.202) > Target: arm64-apple-darwin21.6.0 > Thread model: posix > InstalledDir: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin > jwMini: (macports_dir) /Users/jw/macports_dir > $ Thanks, jw This …snip… > ---> Fetching archive for libomp > ---> Attempting to fetch libomp-15.0.3_0.darwin_21.arm64.tbz2 from > https://packages.macports.org/libomp > ---> Attempting to fetch libomp-15.0.3_0.darwin_21.arm64.tbz2.rmd160 from > https://packages.macports.org/libomp > ---> Installing libomp @15.0.3_0 > ---> Cleaning libomp > ---> Deactivating libomp @14.0.6_0 > ---> Cleaning libomp > ---> Activating libomp @15.0.3_0 > ---> Cleaning libomp > ---> Uninstalling libomp @14.0.6_0 > ---> Cleaning libomp …snip…
Re: Texmaker installation failed due to inability to build qt5 web engine
Apart from the glacial place of OS update migration (*every *app and dependency is downloaded and built from source), Just on this point, if you don't want to have to build everything from source, then you should not update your OS before MacPorts has deployed buildbots for the new OS. You can check this at e.g. https://build.macports.org/waterfall and yes we do not yet have macOS13 in place. Ryan might be able to give an idea of a timeline for this. Chris
Re: Texmaker installation failed due to inability to build qt5 web engine
Dear Gregory, On Fri, 4 Nov 2022 at 06:10, Gregory Dodwell wrote: > > :error:build Failed to build qt5-qtwebengine: command execution failed ... > Other errors deep in the text-dump. Too long to paste here. Should I send a > .zip file of the build log somewhere? At a loose end. The best way to report such issues is Trac where you can upload main.log with complete logs of the failure: https://trac.macports.org/wiki/Tickets (It's nothing wrong if you ask for further advice on the list anyway, but having the log available, or someone else with access to the latest OS, is essential to be able to proceed). Mojca
