Discussion:
I'm trying to compile Plasma 6.4. It was released June 17th by the KDE project, and in Ports on the same day, just a few hours later.
Thing is, x11/plasma6-libplasma is not compiling for me. And it's stopping the rest of the compilation.
I start with:
Compilation goes OK until it's time to compile x11/plasma6-libplasma. That is captured in the attached typescript.txt
Reading through typescript.txt, I can see that the problem is that there's a CMake problem. The interesting part begins on line 765:
Thing is, I don't know how to fix that, or where to file a PR for this stuff.
I tried checking with portsfallout.com, but it only mentions logs for x11/plasma6-libplasma at v. 6.2.5. Freshports reports that same port being at v. 6.4.0... in
I guess the moral of this story is: It's not a bad idea to research how to properly report the failure. You just might discover along the way that there is a simple fix to the problem.
I think it's still worthwhile to leave this up - 6.4 is awfully new, and the very fact that I did encounter (and solve, albeit in a hacky workaround) those problems, it may be of use to someone else. But if someone reads this and has insights, please reply to this thread!
I'm trying to compile Plasma 6.4. It was released June 17th by the KDE project, and in Ports on the same day, just a few hours later.
Code:
astyle@way-kde6:~ $ uname -a
FreeBSD way-kde6.localdomain 14.3-RELEASE FreeBSD 14.3-RELEASE releng/14.3-n271432-8c9ce319fef7 GENERIC amd64Thing is, x11/plasma6-libplasma is not compiling for me. And it's stopping the rest of the compilation.
I start with:
Code:
# cd /usr/ports/x11/plasma6-plasma
# make && make installCompilation goes OK until it's time to compile x11/plasma6-libplasma. That is captured in the attached typescript.txt
Reading through typescript.txt, I can see that the problem is that there's a CMake problem. The interesting part begins on line 765:
Thing is, I don't know how to fix that, or where to file a PR for this stuff.
I tried checking with portsfallout.com, but it only mentions logs for x11/plasma6-libplasma at v. 6.2.5. Freshports reports that same port being at v. 6.4.0... in
Latest repos for amd64 and i386, but older versions for everywhere else!I guess the moral of this story is: It's not a bad idea to research how to properly report the failure. You just might discover along the way that there is a simple fix to the problem.
I think it's still worthwhile to leave this up - 6.4 is awfully new, and the very fact that I did encounter (and solve, albeit in a hacky workaround) those problems, it may be of use to someone else. But if someone reads this and has insights, please reply to this thread!