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

OpenBLAS build failure with MAKEFLAGS='-j4 -l4' #28768

Closed
zimmermann6 opened this issue Nov 19, 2019 · 20 comments
Closed

OpenBLAS build failure with MAKEFLAGS='-j4 -l4' #28768

zimmermann6 opened this issue Nov 19, 2019 · 20 comments

Comments

@zimmermann6
Copy link

I get an error when compiling Sage 8.9 from source on my workstation (Intel(R) Core(TM) i5-4590 under Debian GNU/Linux bullseye/sid). The compilation of openblas fails (see attached file):

/usr/bin/ld: cannot find -l4

Upstream (OpenBLAS) issue:

Depends on #29913

Upstream: Fixed upstream, in a later stable release.

CC: @dimpase @slel

Component: packages: standard

Reviewer: Samuel Lelièvre

Issue created by migration from https://trac.sagemath.org/ticket/28768

@embray
Copy link
Contributor

embray commented Jan 6, 2020

comment:1

Attachment: openblas-0.3.6.p0.log

Ticket retargeted after milestone closed

@embray embray modified the milestones: sage-9.0, sage-9.1 Jan 6, 2020
@dimpase
Copy link
Member

dimpase commented Jan 17, 2020

comment:3

this looks very obscure.

How about using Sage 9.0 or even 9.1betas with openblas from the system?

@embray
Copy link
Contributor

embray commented Jan 17, 2020

comment:4

Googling, and the only reference I can find to -l4 would be if you passed the flag -l4 to make, in which case if you got something like this it would be some kind of flag confusion. I can't imagine otherwise what this would mean.

@embray
Copy link
Contributor

embray commented Jan 17, 2020

comment:5

I'm also looking at the openblas build system and the spkg-install and I can't for the life of me figure out where this could be coming from. Can you post your full environment?

@zimmermann6
Copy link
Author

comment:7

Replying to @embray:

I'm also looking at the openblas build system and the spkg-install and I can't for the life of me figure out where this could be coming from. Can you post your full environment?

Erik, I guess you found it. I have in my environment:

export MAKEFLAGS="-j4 -l4"

which means to use 4 threads for make, but with a global limit of 4 for the cpu load.
I guess the MAKEFLAGS variable is used somewhere in the Sage and/or OpenBLAS makefile,
and not properly protected.

Paul

@zimmermann6
Copy link
Author

comment:8

I did extract the OpenBLAS-0.3.6 tarball shipped with Sage 8.9, did "make" in upstream/OpenBLAS-0.3.6, and the same issues appears:

gfortran -O2 -Wall -frecursive -m64  -mavx2  -o sblat1 sblat1.o ../libopenblas_haswellp-r0.3.6.a -lm -lpthread -lgfortran -lm -lpthread -lgfortran -L/usr/lib/gcc/x86_64-linux-gnu/9 -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/9/../../..  -l4 -lc  
/usr/bin/ld: cannot find -l4

Thus I believe the issue is due to upstream.

@zimmermann6
Copy link
Author

comment:9

I've reported the issue to the openblas developers. They say:

Thank you for the report.

I think we didn't test MAKEFLAGS="-j4 -l4" case.

@zimmermann6
Copy link
Author

Upstream: Reported upstream. Developers acknowledge bug.

@mkoeppe
Copy link
Member

mkoeppe commented Apr 30, 2020

comment:10

We upgraded openblas to 0.3.9, is it fixed?

@zimmermann6
Copy link
Author

comment:11

the issue is still present with openblas 0.3.9 (downloaded from https://github.com/xianyi/OpenBLAS/releases).

@zimmermann6
Copy link
Author

comment:12

please can someone with a github account create the issue on
https://github.com/xianyi/OpenBLAS/issues ?

@dimpase
Copy link
Member

dimpase commented Apr 30, 2020

comment:13

comment:9 says that a report has already been made - surely, if a github issue is to be filed, it would be useful to mention this.

With all respect, setting a gihub account takes a couple of minutes, what's the point of contacting them via an intermediary? Is it forbidden in INRIA?

@zimmermann6
Copy link
Author

comment:14

it is just that I'm reluctant to open a github account for personal reasons. Indeed I reported the issue to Zhang Xianyi on January 17, and sent him a reminder today. His answer was that one could create an issue on github.

@mkoeppe mkoeppe removed this from the sage-9.1 milestone May 7, 2020
@slel
Copy link
Member

slel commented Jun 18, 2020

comment:16

I opened a ticket at OpenBLAS on Paul's behalf.

@slel

This comment has been minimized.

@zimmermann6
Copy link
Author

comment:17

thank you Samuel!

@slel
Copy link
Member

slel commented Jun 20, 2020

Changed upstream from Reported upstream. Developers acknowledge bug. to Fixed upstream, in a later stable release.

@slel
Copy link
Member

slel commented Jun 20, 2020

Reviewer: Samuel Lelièvre

@slel
Copy link
Member

slel commented Jun 20, 2020

Dependencies: #29913

@slel
Copy link
Member

slel commented Jun 20, 2020

comment:18

There was already a relevant ticket and fix upstream:

The fix is part of OpenBLAS 0.3.10 released last week.

Paul confirmed to me he could no longer observe
the problem with OpenBLAS 0.3.10.

Upgrading to OpenBLAS 0.3.10 is now tracked at #29913.

@slel slel changed the title another openblas build failure OpenBLAS build failure with MAKEFLAGS='-j4 -l4' Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants