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.

Sign up for GitHub

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

Jump to bottom

Building v0.2.20 fails on non-glibc systems #1252

Closed
pbregener opened this issue Jul 27, 2017 · 5 comments
Closed

Building v0.2.20 fails on non-glibc systems #1252

pbregener opened this issue Jul 27, 2017 · 5 comments
Milestone
0.3.0

Comments

@pbregener
Copy link

Building OpenBLAS 0.2.20 fails on non-glibc systems, due to unsafe use of the __GLIBC_PREREQ preprocessor macro. Will there be a patch release soon or should downstream maintainers patch this?
@brada4
Copy link
Contributor

brada4 commented Jul 27, 2017

It is #1247 that reverts offending change

@martin-frbg
Copy link
Collaborator

martin-frbg commented Jul 27, 2017 •
edited
Loading

Master branch has the problematic change already reverted in anticipation of a quick interim release,
current develop branch has a partially fixed version of the intended functionality (that still breaks when compiled with NO_AFFINITY=1, hopefully fixed for good in a few hours)

@brada4
Copy link
Contributor

brada4 commented Jul 27, 2017

I think it is more to @xianyi if he intends 0.2.21 tomorrow....

@jirutka jirutka mentioned this issue Jul 28, 2017
Merged
@pbregener pbregener mentioned this issue Jul 30, 2017
Closed
@martin-frbg martin-frbg mentioned this issue Jul 31, 2017
Merged
@martin-frbg
Copy link
Collaborator

Inadvertently closed with my PR for develop - reopening until 0.2.21 is out.

@martin-frbg martin-frbg reopened this Aug 1, 2017
@martin-frbg martin-frbg mentioned this issue Aug 4, 2017
Closed
@isuruf isuruf mentioned this issue Aug 8, 2017
Merged
@jakirkham jakirkham mentioned this issue Sep 8, 2017
Closed
@martin-frbg martin-frbg added this to the 0.3.0 milestone Apr 2, 2018
@martin-frbg
Copy link
Collaborator

Guess we can skip 0.2.21 now as it would no longer be a "quick fix" after six months have passed, but hopefully 0.3.0 can be released "very soon now".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
3 participants
@martin-frbg @pbregener @brada4