public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with cblas libraries
Date: Fri, 26 Aug 2011 23:20:18 +0200	[thread overview]
Message-ID: <3590927.sXiB4Um2sz@weird> (raw)
In-Reply-To: <CAKf_S2JNr3GrMnh08NqHnGQGWnwbX=ofY7oMs113inQ=mx9M+Q@mail.gmail.com>

denis cohen writes:

> I recently removed some packages like blas-reference, cblas-reference,
> and lapack-reference to get emerge to run (some blocking issues).

I unmerged eselect-cblas and eselect-blas when I had similar problems, and I 
think also {blas,cblas}-reference. The eselect packages got remerged 
automatically, and some block I do not remember remained, but after some 
days, a deep world update finally was working again.

> Not sure that was a good idea because now, even if I've reinstalled
> these packages,
> I am having several new problems:
> 
> - compiling gcc with the gsl library spits out errors like:
> g++ -L/usr/local/lib -lm -lgsl  exact.o
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../lib64/libgsl.so:
> undefined reference to `cblas_ctrmv'
[...]
> and so on.......
> 
> - still can't re-emerge packages like gsl and gmsh. For example, for gmsh
> I get; .....
> [100%] Building CXX object
> CMakeFiles/gmsh.dir/contrib/bamg/bamglib/MeshDraw.cpp.o
> [100%] Building CXX object
> CMakeFiles/gmsh.dir/contrib/bamg/bamglib/MeshQuad.cpp.o
> [100%] Building CXX object
> CMakeFiles/gmsh.dir/contrib/bamg/bamglib/MeshWrite.cpp.o
> [100%] Building CXX object
> CMakeFiles/gmsh.dir/contrib/bamg/bamglib/Meshio.cpp.o [100%] Building CXX
> object
> CMakeFiles/gmsh.dir/contrib/bamg/bamglib/QuadTree.cpp.o
> make[2]: *** No rule to make target `/usr/lib64/libcblas.so', needed
> by `gmsh'.  Stop.

This looks strange. A target in the root file system? Here the log continues 
like this:

[100%] Building CXX object 
CMakeFiles/gmsh.dir/contrib/bamg/bamglib/Meshio.cpp.o
[100%] Building CXX object 
CMakeFiles/gmsh.dir/contrib/bamg/bamglib/QuadTree.cpp.o
[100%] Building CXX object 
CMakeFiles/gmsh.dir/contrib/bamg/bamglib/SetOfE4.cpp.o
Linking CXX executable gmsh
[100%] Built target gmsh
>>> Source compiled.
>>> Test phase [not enabled]: sci-libs/gmsh-2.5.0



> Does anyone have an idea of how solve this problem?

No. All I can say is that I just emerged gmsh without problems on ~amd64,  
both with and without the blas USE flag. The other USE flags are those:
     Installed versions:  2.5.0{tbz2}(23:10:59 26.08.2011)(X blas jpeg png 
zlib -cgns -chaco -doc -examples -lua -med -metis -mpi -netgen -opencascade 
-petsc -taucs -tetgen)                                             

	Wonko



  parent reply	other threads:[~2011-08-26 21:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 12:12 [gentoo-user] Problem with cblas libraries denis cohen
2011-08-26 15:36 ` Helmut Jarausch
2011-08-26 17:41 ` [gentoo-user] " Gene Hannan
2011-08-26 21:20 ` Alex Schuster [this message]
2011-08-27 15:27 ` [gentoo-user] " Valmor de Almeida
2011-08-27 16:34   ` Michael Mol
2011-08-30 22:15     ` denis cohen
2011-08-30 22:27       ` Michael Mol
2011-08-30 23:02       ` Alex Schuster
2011-08-30 23:14         ` denis cohen
2011-08-30 23:27           ` denis cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3590927.sXiB4Um2sz@weird \
    --to=wonko@wonkology.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox