Re: Is it possible atlas is linked wrongly by new binutils?

On 08/15/2017 02:47 PM, Kevin Kofler wrote: Please note that what I am proposing here is not the same as my proposal from 3 years ago that was rejected. While I would not complain if my old proposal were implemented, I am now suggesting a much simpler approach (which was already hinted at in the

Re: Is it possible atlas is linked wrongly by new binutils?

On 08/14/2017 03:35 AM, Kevin Kofler wrote: That said, ATLAS should really go away, unless they add support for runtime CPU detection and the result matches or exceeds OpenBLAS performance. In its current state (which has been the state since its inception), ATLAS is really unsuitable for

OpenBLAS as the default BLAS (was: Re: Is it possible atlas is linked wrongly by new binutils?)

On Saturday, 12 August 2017 at 00:11, Dominik 'Rathann' Mierzejewski wrote: > On Thursday, 10 August 2017 at 12:29, Richard W.M. Jones wrote: > > Never mind. Something in the atlas build segfaults when building > > on ppc64le: > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=21145734

Re: Is it possible atlas is linked wrongly by new binutils?

On Fri, Aug 18, 2017 at 08:04:52AM +0200, Jakub Martisko wrote: > It should work now [1]. > > Jakub > > [1]: > https://koji.fedoraproject.org/koji/taskinfo?taskID=21296324 Thanks, I'll try to rebuild ocaml-gsl & ocaml-lacaml shortly. Rich. -- Richard Jones, Virtualization Group, Red Hat

Re: Is it possible atlas is linked wrongly by new binutils?

It should work now [1]. Jakub [1]: https://koji.fedoraproject.org/koji/taskinfo?taskID=21296324 On 9.8.2017 11:37, Richard W.M. Jones wrote: > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > fails to link to atlas: > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg

Re: Is it possible atlas is linked wrongly by new binutils?

On 08/17/2017 12:05 AM, Dan Horák wrote: On Wed, 16 Aug 2017 22:57:28 +0200 Kevin Kofler wrote: Dave Love wrote: Kevin Kofler writes: If you are talking about the missing RPM AutoProvides: Provides: libblas.so.3()(64bit) does wonders. I mean you need to get the

Re: Is it possible atlas is linked wrongly by new binutils?

On 08/16/2017 04:34 PM, Tom Callaway wrote: > > > On 08/09/2017 05:37 AM, Richard W.M. Jones wrote: >> >> ocaml-gsl (OCaml bindings for GNU Scientific Library) currently >> fails to link to atlas: >> >> + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I >> examples

Re: Is it possible atlas is linked wrongly by new binutils?

On Wed, 16 Aug 2017 22:57:28 +0200 Kevin Kofler wrote: > Dave Love wrote: > > > Kevin Kofler writes: > >> If you are talking about the missing RPM AutoProvides: > >> Provides: libblas.so.3()(64bit) > >> does wonders. > > > > I mean you need to get the soname right and

Re: Is it possible atlas is linked wrongly by new binutils?

Dave Love wrote: > Kevin Kofler writes: >> If you are talking about the missing RPM AutoProvides: >> Provides: libblas.so.3()(64bit) >> does wonders. > > I mean you need to get the soname right and ensure that you have > everything implemented in the replacement library. Only the soname of the

Re: Is it possible atlas is linked wrongly by new binutils?

On 08/09/2017 05:37 AM, Richard W.M. Jones wrote: > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > fails to link to atlas: > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I > examples lib/gsl.cmxa examples/blas_ex.cmx -o

Re: Is it possible atlas is linked wrongly by new binutils?

Kevin Kofler writes: > Dave Love wrote: >> You'll find Dominik was correct if you try it. > > If you are talking about the missing RPM AutoProvides: > Provides: libblas.so.3()(64bit) > does wonders. I mean you need to get the soname right and ensure that you have

Re: Is it possible atlas is linked wrongly by new binutils?

Dave Love wrote: > You'll find Dominik was correct if you try it. If you are talking about the missing RPM AutoProvides: Provides: libblas.so.3()(64bit) does wonders. > Various things have been changed to use openblas on x86 after some of us > agitated. The problem is, "various things" is not

Re: Is it possible atlas is linked wrongly by new binutils?

(I am reversing the paragraphs so that the order of the replies makes sense.) Dominik 'Rathann' Mierzejewski wrote: > Thinking again, we had this discussion over 3 years ago: > https://pagure.io/packaging-committee/issue/352 > and another one starting 2 years ago: >

Re: Is it possible atlas is linked wrongly by new binutils?

On 15.8.2017 10:39, Dave Love wrote: > > I don't know whether that's true, but Fedora could at least improve the > situation by providing more than the -sse2 and -sse3 packages. > I am planning to drop the sse2 sse3 subpackages and replace them with something a bit more "modern" [1] with the

Re: Is it possible atlas is linked wrongly by new binutils?

Kevin Kofler writes: > Dominik 'Rathann' Mierzejewski wrote: >> It also needs some patching, because each library has a different >> SONAME. > > Symlinking > libblas.so.3 → libopenblas.so.0 > liblapack.so.3 → libopenblas.so.0 > is enough to get things linked against BLAS

Re: Is it possible atlas is linked wrongly by new binutils?

Matthew Miller writes: > On Sun, Aug 13, 2017 at 11:01:04AM +0200, Kevin Kofler wrote: >> Can't we make it a drop-in replacement for reference BLAS/LAPACK and ATLAS, >> i.e., having symlinks or linker scripts pointing at least libblas.so and >> liblapack.so to

Re: Is it possible atlas is linked wrongly by new binutils?

On Monday, 14 August 2017 at 02:35, Kevin Kofler wrote: > Dominik 'Rathann' Mierzejewski wrote: > > It also needs some patching, because each library has a different > > SONAME. > > Symlinking > libblas.so.3 → libopenblas.so.0 > liblapack.so.3 → libopenblas.so.0 > is enough to get things linked

Re: Is it possible atlas is linked wrongly by new binutils?

Dominik 'Rathann' Mierzejewski wrote: > It also needs some patching, because each library has a different > SONAME. Symlinking libblas.so.3 → libopenblas.so.0 liblapack.so.3 → libopenblas.so.0 is enough to get things linked against BLAS and/or LAPACK to pick up OpenBLAS instead. A similar

Re: Is it possible atlas is linked wrongly by new binutils?

On Sunday, 13 August 2017 at 14:58, Matthew Miller wrote: > On Sun, Aug 13, 2017 at 11:01:04AM +0200, Kevin Kofler wrote: > > Can't we make it a drop-in replacement for reference BLAS/LAPACK and ATLAS, > > i.e., having symlinks or linker scripts pointing at least libblas.so and > > liblapack.so

Re: Is it possible atlas is linked wrongly by new binutils?

On Sun, Aug 13, 2017 at 11:01:04AM +0200, Kevin Kofler wrote: > Can't we make it a drop-in replacement for reference BLAS/LAPACK and ATLAS, > i.e., having symlinks or linker scripts pointing at least libblas.so and > liblapack.so to libopenblas.so.*, ideally also libblas.so.3 and >

Re: Is it possible atlas is linked wrongly by new binutils?

Dominik 'Rathann' Mierzejewski wrote: > Yes, you don't need to add -L%{_libdir}/atlas to LDFLAGS anymore and you > link with -lopenblas. Can't we make it a drop-in replacement for reference BLAS/LAPACK and ATLAS, i.e., having symlinks or linker scripts pointing at least libblas.so and

Re: Is it possible atlas is linked wrongly by new binutils?

On Saturday, 12 August 2017 at 23:30, Richard W.M. Jones wrote: > On Sat, Aug 12, 2017 at 12:40:18PM +0200, Kevin Kofler wrote: > > Richard W.M. Jones wrote: > > > I have no particular affinity for Atlas. But if we're going to > > > replace it, is OpenBLAS a complete drop-in replacement for Atlas

Re: Is it possible atlas is linked wrongly by new binutils?

On Sat, Aug 12, 2017 at 12:40:18PM +0200, Kevin Kofler wrote: > Richard W.M. Jones wrote: > > I have no particular affinity for Atlas. But if we're going to > > replace it, is OpenBLAS a complete drop-in replacement for Atlas that > > requires no or at least very minimal changes? In what ways is

Re: Is it possible atlas is linked wrongly by new binutils?

Richard W.M. Jones wrote: > I have no particular affinity for Atlas. But if we're going to > replace it, is OpenBLAS a complete drop-in replacement for Atlas that > requires no or at least very minimal changes? In what ways is it better > or worse? Proper support for runtime CPU feature

Re: Is it possible atlas is linked wrongly by new binutils?

On Sat, Aug 12, 2017 at 12:11:00AM +0200, Dominik 'Rathann' Mierzejewski wrote: > On Thursday, 10 August 2017 at 12:29, Richard W.M. Jones wrote: > > Never mind. Something in the atlas build segfaults when building > > on ppc64le: > > > >

Re: Is it possible atlas is linked wrongly by new binutils?

On Thursday, 10 August 2017 at 12:29, Richard W.M. Jones wrote: > Never mind. Something in the atlas build segfaults when building > on ppc64le: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=21145734 > > This is a mess :-( Just switch to openblas already. ;) I'd propose a Change for

Re: Is it possible atlas is linked wrongly by new binutils?

Well, yes, the current version is a bit messy, I am currently working on rebase to 3.10.3, where the builds seem to be more stable but I wanted to test it a bit more before publishing it tbh. :-/ On 10.8.2017 12:29, Richard W.M. Jones wrote: > Never mind. Something in the atlas build segfaults

Re: Is it possible atlas is linked wrongly by new binutils?

Never mind. Something in the atlas build segfaults when building on ppc64le: https://koji.fedoraproject.org/koji/taskinfo?taskID=21145734 This is a mess :-( Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog:

Re: Is it possible atlas is linked wrongly by new binutils?

On Thu, Aug 10, 2017 at 11:21:30AM +0200, Jakub Martisko wrote: > > > On 9.8.2017 11:37, Richard W.M. Jones wrote: > > > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > > fails to link to atlas: > > > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I

Re: Is it possible atlas is linked wrongly by new binutils?

On Wed, Aug 09, 2017 at 02:10:02PM +0200, Antonio Trande wrote: > On 08/09/2017 11:37 AM, Richard W.M. Jones wrote: > > > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > > fails to link to atlas: > > > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I

Re: Is it possible atlas is linked wrongly by new binutils?

On Wed, Aug 9, 2017 at 3:37 AM, Richard W.M. Jones wrote: > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > fails to link to atlas: > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I > examples lib/gsl.cmxa examples/blas_ex.cmx

Re: Is it possible atlas is linked wrongly by new binutils?

On 08/09/2017 11:37 AM, Richard W.M. Jones wrote: > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > fails to link to atlas: > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I > examples lib/gsl.cmxa examples/blas_ex.cmx -o

Is it possible atlas is linked wrongly by new binutils?

ocaml-gsl (OCaml bindings for GNU Scientific Library) currently fails to link to atlas: + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I examples lib/gsl.cmxa examples/blas_ex.cmx -o examples/blas_ex.native /usr/lib64/atlas/libsatlas.so: undefined reference to