Closed Tatsh closed 5 years ago
Did you already have the port installed? If so any commit made afterwards can have introduced the regression.
Sent from a pocket terminal
On 20 Feb 2019, at 11:43, Tatsh notifications@github.com wrote:
15d0161 related?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I uninstalled kf5-plasma-runtime and its dependencies. Got the same error.
I am getting the same error when attempting to build grantlee5. Not sure what the /bin/ps
part is about (ps works fine). The main error seems to be :info:build Error running link command: No such file or directory
. I was able to compile other packages without issues.
I haven't touched the grantlee5 port in a long time, but failure building that means your issue can't be related to the plasma-desktop port.
Could you attach a full log for grantlee5 please? It's bound to be a lot simpler so the issue should be easier to pinpoint.
Full log with buildmakejobs set to 1
Also, apparently the /bin/ps
error is because whatever is running at that point is likely running in the sandbox. See Running /bin/ps with NSTask with App Sandboxing enabled. This might not be the source of the failure.
My guess based on the log is that it's the ar
command having the wrong path. The command is showing /opt/local/var/macports/build/_Users_tatsh_dev_macstrop_devel_grantlee/grantlee5/work/build/ar
as the path to ar
when it looks like, for me, it should be /usr/bin/ar
(or just ar
). This is despite MacPorts passing -DCMAKE_AR="ar"
to CMake.
I ran ccmake
to verify and yes, CMAKE_AR
, CMAKE_NM
, and CMAKE_RANLIB
are pointing to the wrong paths. And I verified that other packages using CMake/Qt/etc work fine.
Yes, I just confirmed the same thing.
The error I made was assuming that CMAKE_AR and family work like CMAKE_CXX_COMPILER and family in that they accept just command names. Instead, they require a full path. That's not even documented as far as I can tell...
I'll push a fix in a moment.
R.
Also, apparently the
/bin/ps
error is because whatever is running at that point is likely running in the sandbox.
Questions are which sandbox, and who runs ps...
This might not be the source of the failure.
Indeed it isn't. The error is an ENOENT trying to create a static library. My guess is you shouldn't be getting it anymore.
Fixed.
Getting this error:
I have
/bin/ps
(as all Macs do).