On Wednesday 11 May 2005 1:23 pm, Christopher G. Traylor wrote: > On Tue, 2005-05-10 at 16:39 -0400, Darren Dale wrote: > > On Tuesday 10 May 2005 3:37 pm, Christopher G. Traylor wrote: > > > Sorry, if this has been addressed before. We're trying to build scipy > > > on an dual opteron box in 64 bit mode. With the r1 ebuild, it fails > > > complaining that it can't find some symbol. If I take the atlas-3.6.0 > > > requirement out, it builds fine, but during the test phase, it gives > > > these errors. My guess is that having atlas in there is causing some > > > sort of multilib problem, and that blas-atlas provides all the required > > > symbols, but doesn't have the proper internal support to return the > > > answers that the scipy test suite is expecting. I guess my confusion > > > stems from the whole "odd" virtual atlas set up. Any guidance would be > > > appreciated. > > > > sci-libs/atlas will, if installed after lapack-atlas, overwrite a symlink > > in /usr/lib with an incomplete lapack library. atlas should not be in the > > ebuild. Only lapack-atlas should be in there, which still provides the > > atlas libraries. I wrote about this in the bug report. > > > > > > > > > > Try running ls -l /usr/lib/liblapack.*, they should all be symlinks to > > files in /usr/lib/lapack/atlas/. If, in /usr/lib, liblapack.a (I think > > .a) is not a symlink, it is probably smaller than ~5.5MB, and isnt a full > > lapack implementation. > > Right. All three are symlinks. Although my thinking is that if the > library was missing a function, then you would have had a segfault or > some other "catastrophic" error like a failed build/link.
I think I recall that it would build, but the errors wouldnt show up until the test phase. I could be wrong. > I added the patches to my ebuild file, and everything seems to go fine > until the testing phase. Then I get an Xlib failure. It spits out that > it couldn't connect to :0.0, and that no protocol was specified (i.e. > typical useless X error message). My first question was why is the > ebuild trying to launch a graphical app on install (although, I didn't > specify it quite that politely when I realized it<g>)? Is there possibly > some use flag that needs set so that the test suite allows it to run in > a text mode that I'm retardedly omitting? Also, I was wondering whether > I should bother with a bug report on this since we are talking about > this directly. A shot in the dark: You wouldn't happen to have been installing over an ssh connection, would you? Also, could you check that the patches are being applied properly? I wasnt sure whether to keep "Scipy-complete-0.3.2" in the path, on the first two lines of the patch file. Darren
pgpsrOVAKeYWb.pgp
Description: PGP signature
