-
Notifications
You must be signed in to change notification settings - Fork 23
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
nemea make command not working #20
Comments
Can you provide information about your operating system and compiler version, please? |
Operating system : |
Ok, thank you for the information, I was able to repeat the issue locally, I'll provide a patch soon. A temporary workaround for you can be: |
Well, it seems to me this time it uses a different location of some previously installed library... To skip installed libraries and use files from relative paths in the repo during the build, there is a special parameter, so maybe Also, sending output of |
…t least 10 According to https://gcc.gnu.org/gcc-10/changes.html, new gcc has changed default behavior so we get compile errors without -fno-common. This should help with: CESNET/Nemea#20
Add gcc version check in UniRec and insert -fcommon flag. This should solve #20.
After updates, I have tested to build everything on a clean Fedora32 using podman container - build succeeded. Can you confirm it's fixed now? |
According to https://gcc.gnu.org/gcc-10/changes.html, new GCC has changed default behaviour so we get compile errors without -fcommon. This is not required for the unirec library itself, which builds fine, but for (some of) the users in the modules repository. The unirec usage depends heavily on the -fcommon behaviour and fixing that would require major redesign, so just explicitly add this option to keep the old GCC behaviour. This should help with: CESNET/Nemea#20
We have deployed nemea module .we want to develop it through binary source code .at the time of compilation its gets configured but after we got error please helpt resolve this isssue .

The text was updated successfully, but these errors were encountered: