-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CURSES_CURSES_LIBRARY being set NOTFOUND #156
Comments
Thank you for reporting! |
It's Here's the complete buildlog that I have available: https://build.opensuse.org/package/live_build_log/home:sfalken/wlmaker/openSUSE_Tumbleweed/x86_64 |
Curious... this is from https://github.com/phkaeser/libbase/blob/main/CMakeLists.txt, and I suspect the CMake configuration may have been using some cargo cult. Could you try editing the file there and replace:
(so far, my systems hadn't shown the error, so it'd be great if you could help fixing it) |
Making those changes, it no longer throws the error:
And now the error is:
If I change from The build does start, as expected, but it fails, please see buildlog: |
I did just notice I had a typo in my sed statements, where I was setting CURSES_CURSES_INCLUDE_DIRS to CURSES_INCLUDE_DIRS rather than DIR, but fixing that didn't fix the build failure. |
The curses variables should be fixed with #160. That additional build error in https://paste.opensuse.org/pastes/aef7b57cf2c5 looks surprising, though. I noticed you're pulling in libbase in your build somehow (`/usr/lib/rpm/rpmuncompress -x /home/abuild/rpmbuild/SOURCES/libbase-27aae1898bcc9bd125f260c42c370896159afbee.tar.gz/usr/lib/rpm/rpmuncompress -x /home/abuild/rpmbuild/SOURCES/libbase-27aae1898bcc9bd125f260c42c370896159afbee.tar.gz). Can you verify and confirm that libbase is recent? (with #160 , it should be today's https://github.com/phkaeser/libbase/ at HEAD). |
That did the trick. Pulling from libbase HEAD, and the compile goes through just fine. I'm not getting any docs included, but that's something I'll get sorted out. |
Got it figured out, even though I don't need them to get it packaged, they're just nice to have. |
Happy to hear it compiles on OpenSUSE, @sfalken ! The Still, it shouldn't fail, unless something is missing. Could you paste the failing build log for |
Here's a copy of the complete build log, with the flags set to enable https://build.opensuse.org/package/live_build_log/home:sfalken/wlmaker/openSUSE_Tumbleweed/x86_64 |
There appears to be a problem with
The versions for both are slightly newer than on my machine. I'm afraid I don't have an idea what's wrong there. Maybe trying whether |
I don't know if you want to add it to the checks for existing packages, but at least on openSUSE, our I've still got the error, when it comes to packaging it into an .rpm but that's an openSUSE problem I need to solve, and not wlmakers issue. It builds fine if I just unpack the sources locally and make sure that |
Got it done. Just had to add a few more bits to the build environment. Just leaving this link, mostly for folks that might be building it in non-debian/ubuntu environments, so they can see the https://build.opensuse.org/projects/home:sfalken/packages/wlmaker/files/wlmaker.spec?expand=1 The installation locations for the icons and .desktop files isn't suitable for inclusion in the main openSUSE Repos for now, but it's packaged well enough for folks to be able to install it, and have it work. |
Thank you so much for getting this to work, @sfalken ! Curious finding, about the fonts. On Debian, these fonts appear to be in package (leaving open for now; I might later move that into a separate issue, since the original "curses" dependency has been fixed) |
I'm trying to package wlmaker 0.4.1 for openSUSE, roughly adapting the rpm .spec file from Fedora:
https://src.fedoraproject.org/rpms/wlmaker/blob/rawhide/f/wlmaker.spec
But I'm hitting an error, and I'm not sure how to fix it:
Do you have any insight as to what might be happening here? (It's not impossible that our cmake macro within the build system may be messing with things)
The text was updated successfully, but these errors were encountered: