Skip to content
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

On EPYC/gcc 4.8, testers not linked with common.a #120

Closed
pmucci opened this issue Dec 5, 2017 · 4 comments
Closed

On EPYC/gcc 4.8, testers not linked with common.a #120

pmucci opened this issue Dec 5, 2017 · 4 comments

Comments

@pmucci
Copy link

pmucci commented Dec 5, 2017

Hi all,

Just testing out this library on a new AMD EPYC. Using the latest git repo, cmake3 and gcc 4.8, the library builds but the tests fail when trying to link the tester because of undefined reference to Sleef_x86CpuID. Looking into link.txt into tester.dir shows the reason why. The shared library is linked after the libcommon.a meaning the dependencies of that shared library won't be satisfied.

I don't know Cmake or I'd submit a patch, but the solution for me was to add the ../common/libcommon.a to the end of src/libm-tester/CMakeFiles/tester.dir/link.txt

This is against current git head. I must assume that others are seeing this? I couldn't find anything special about my config that would cause that ordering.

The tests appear to pass ok, but alas, I cannot use it because libsleef.so does not include common.a as well. I need to keep looking.

@pmucci
Copy link
Author

pmucci commented Dec 5, 2017

Ok, my error was CMAKE_BUILD_TYPE set to an invalid string. Trying it again with that set to RelWithDebInfo seems to have worked. I'd say this isn't a bug per-se, but might want to check that string.

@shibatch
Copy link
Owner

shibatch commented Dec 6, 2017

Hi Philip,

For some reasons, the functions in common.c are now included in libsleefdft. I will move them to libsleef.

@pmucci
Copy link
Author

pmucci commented Dec 8, 2017 via email

@shibatch
Copy link
Owner

shibatch commented Dec 8, 2017

I will fix this problem in the next week. Please be patient. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants