Your message dated Wed, 03 Aug 2011 22:47:37 +0200
with message-id <[email protected]>
and subject line Openblas custom fail
has caused the Debian Bug report #636369,
regarding Build failure: libopenblasp-*.so
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
636369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636369
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openblas
Severity: normal

A build of svn r38633 fails towards the end with:

$ fakeroot debian/rules custom
...
ln -fs libopenblas_opteronp-r0.1alpha2.2.so libopenblas.so

 OpenBLAS build complete.

  OS               ... Linux             
  Architecture     ... x86_64               
  BINARY           ... 64bit                 
  C compiler       ... GCC  (command line : gcc)
  Fortran compiler ... GFORTRAN  (command line : gfortran)
  Library Name     ... libopenblas_opteronp-r0.1alpha2.2.a (Multi threaded; Max 
num-threads is 8)

make[2]: Leaving directory `/path/to/openblas-0.1alpha2.2'
if test "custom" != "" -a "custom" != "custom"; then            \
                        echo "Use the value 'custom' provided by the user";     
\
                        /usr/bin/make "NO_LAPACK=1" TARGET=custom;              
\
        fi;
rm libopenblas.so
mv libopenblasp-*.so libopenblas.so.0
mv: cannot stat `libopenblasp-*.so': No such file or directory
make[1]: *** [build-stamp] Error 1
make[1]: Leaving directory `/path/to/openblas-0.1alpha2.2'
make: *** [custom] Error 2
$ 

This is the only .so available:

$ find . -name 'libopenblas*.so'
./libopenblas_opteronp-r0.1alpha2.2.so


Ryan



--- End Message ---
--- Begin Message ---
Hello,

This bug has been fixed in my svn but I forgot to commit (oups). please
update. ;)

Sylvestre




--- End Message ---

Reply via email to