-
Notifications
You must be signed in to change notification settings - Fork 4
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
build failure ‘tbb_allocator’ is not a member of ‘tbb’ #98
Comments
The configuration is
|
Sounds like a change in tbb. The allocator isn't defined and things go haywire after that. |
Ok, not a change. I think this is because you used "--with-tbb-malloc=no", which should turn off the use off |
This should be fixed as of 14a17e9 and published in 1.7.2 |
@smoe Please try this again. I could not reproduce fully. There also will be some performance impact to not using TBB malloc for many threads. |
Thank you for your swift action. I had always tried different compiler options, i.e. with and without tbb and tbb-malloc, which from what I recollect always led to the same error. And - good news - we are past that now. When not passing any options to configure (besides disable static and arbhome) I see
This does not seem too surprising since
and when I then add the same compiler flags that suggest not to use the tbb and tbb-malloc, I get a bunch of link errors which seem independent of the tbb-malloc setting (have not checked them all):
So, my immediate fix would be to use the tbb (had only set the "no" in a hope to avoid that initial build error) and start investigating what is causing the non-tbb link errors. Suggestions welcome :) I can find a machine for you to log in to and reproduce the error any time if that is of any help. Many thanks and kind regards! |
A machine to reproduce would indeed help! If you could copy https://github.com/epruesse.keys to |
I'm guessing that there is some I can probably try this in a Debian docker, actually. Just need to find the time to track the problem. |
Hello,
I keep running into
Any idea?
on Debian unstable. I saw the problem also reported in June on https://www.mail-archive.com/[email protected]/msg117530.html.
Many thanks!
The text was updated successfully, but these errors were encountered: