-
Notifications
You must be signed in to change notification settings - Fork 184
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
Can't compile on openSUSE #470
Comments
Hi, Did you run |
hello, |
I see, I also have to package klib and debugbreak 🤔 |
Oh sorry, I missed the "packaging" part. Yeah, there are subprojects and submodules as well: |
nice, thanks! BoxFort I already packaged it yesterday. Now I have to package those 2 submods. |
Are you working on the official packaging of Criterion for SUSE? |
Yes, I am :)
|
Thanks for doing this.
|
|
@MrAnno I think I'll do the same. No point in having a separate pacakge for |
in the end I packaged both
any idea? |
boxfort is found though:
and correctly linked:
|
Hmm, let me check the out-of-tree linking against Boxfort in my dev env. |
@paolostivanin Can you share your build commands and the BoxFort version you use, please? |
I'm using boxfort = 0.1.4 taken from For both boxtrot and criterion the build and install cmds are:
but on criterion I also add About those macros:
|
I've tried different stuff, but I always get stuck on that undef reference 🤔 |
I could not reproduce this, I'll try on openSUSE soon. |
Steps to reproduce it:
|
also, for criterion I've applied the following patch, otherwise nanopb is not correctly detected:
|
Thanks, I'm checking it. |
I've reproduced it too. It seems symbols are really missing from BoxFort and nanopb:
After recompiling BoxFort ( |
I recompiled with the extended compiler flags and parameters you provided, and that build worked as expected too. |
Yes, the build system strips debug symbols by default. Maybe you can spot what's causing the issue 🤔 |
It's brp-15-strip-debug that removes essential symbols from the BoxFort static library. Probably it is also responsible for removing |
Right, thanks! That check + LTO are causing the issue. Working on a fix. |
I think BoxFort is currently not ready to operate as a shared library because it does some black magic during sandbox creation: it patches the user's main function. But I believe we will eventually make it work as a shared lib too. |
Hmm, it seems to be working perfectly as a shared library if I set |
without any side issues? that'd be cool 😄 |
I will investigate this a little deeper and open a pull request. |
Ok, so now boxfort is working fine, but the problem is with nanopb. I've disabled both stripping and lto, but it's not helping:
PS: yes, the static lib is fine for now, thanks! |
Sorry, I was wrong about this one. pb_release() is for ENABLE_MALLOC. |
cool :D now it's working (well, it compiles at least! 😄 now I've gotta test it!) |
thanks a lot for your help! |
My pleasure. Thanks for the hard work. I'm really excited about the first RPM-based Criterion package. |
FYI, first test package is ready: https://build.opensuse.org/package/show/home:polslinux:tools/criterion will test it this afternoon, let's see how it goes :D |
couple of findings:
|
that feeling when everything works :D can confirm that Criterion now works fine on openSUSE Tumbleweed. Will test Leap too and then tomorrow I'll start the official packaging process. |
Hello,
I'm trying to package Criterion on openSUSE, but I'm facing some issues:
then the compilation starts and fails at the following steps:
The text was updated successfully, but these errors were encountered: