Bug 69766 - blas-config-1.0.0 fails with get_libdir:command not found, blas-config-1.0.1 works OK
|
Bug#:
69766
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: PPC
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: sci@gentoo.org
|
Reported By: nowhcreek@yahoo.com.au
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: blas-config-1.0.0 fails with get_libdir:command not found, blas-config-1.0.1 works OK
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-11-01 13:57 0000
|
blas-config-1.0.0 fails in the same manner described in bug 69556 on PPC.
Changing to blas-config-1.0.1 fixed the problem. I have attached emerge info
below as this may be related to the version of portage I am using.
For information lapack-config-1.0.1 also worked OK, however I did not try
lapack-config-1.0.0
Reproducible: Always
Steps to Reproduce:
1.emerge blas-atlas using blas-config-1.0.0
2.
3.
Actual Results:
problem described in bug 69556 resulting in incorrect links to blas libraries
Expected Results:
produced correct links to blas libraries
Portage 2.0.51-r2 (default-ppc-2004.2, gcc-3.4.1, glibc-2.3.3.20040420-r2,
2.6.9-gentoo-r1 ppc)
=================================================================
System uname: 2.6.9-gentoo-r1 ppc 740/750
Gentoo Base System version 1.4.16
ccache version 2.2 [enabled]
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.90.0.3-r3
Headers: sys-kernel/linux-headers-2.4.22
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CFLAGS="-O3 -pipe -mcpu=750"
CHOST="powerpc-unknown-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown
/usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -pipe -mcpu=750"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks"
GENTOO_MIRRORS="http://planetmirror.com/pub/gentoo
http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="X alsa arts berkdb cdr crypt cups dvd emacs f77 gdbm gif gtk gtk2 java
jpeg
kde lapack ldap libwww maildir motifmozilla moznocompose moznoirc moznomail nls
opengl pam perl png ppc python qt readline ssl tcpd tetex tiff truetype"
Can somebody on ppc please test blas-config-1.0.1 and mark it stable? I don't
really want to mark the arch on which I cannot test but if this bug sits open
few more days I'll just go ahead and mark it stable on all arches (its a simple
bash script after all, it should be insensitive to the arch).
To ppc people whom I CC'd:
we (sci team) would like ot see this version marked stable, as 1.0.0 starts to
conflict with new toolchain.
George
Heh, I just hit this bug. Using 1.01 fixed the problem. Fixed in CVS.
