Bug 195189 - sci-libs/itpp-4.0.0_rc2 configure error - invalid package name: blas --without-lapack
Bug#: 195189 Product:  Gentoo Linux Version: unspecified Platform: x86
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: markusle@gentoo.org Reported By: jarausch@igpm.rwth-aachen.de
Component: Ebuilds
URL: 
Summary: sci-libs/itpp-4.0.0_rc2 configure error - invalid package name: blas --without-lapack
Keywords:  
Status Whiteboard: 
Opened: 2007-10-09 08:25 0000
Description:   Opened: 2007-10-09 08:25 0000
sci-libs/itpp-4.0.0_rc2 fails to build:
Compiling source in
/var/tmp/portage/sci-libs/itpp-4.0.0_rc2/work/itpp-4.0.0-rc2 ...
 * econf: updating itpp-4.0.0-rc2/config/config.sub with
/usr/share/gnuconfig/config.sub
 * econf: updating itpp-4.0.0-rc2/config/config.guess with
/usr/share/gnuconfig/config.guess
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --enable-html-doc --disable-debug --without-lapack
--without-blas --without-lapack --build=i686-pc-linux-gnu
configure: error: invalid package name: blas --without-lapack
 * Call stack:
 *               ebuild.sh, line 1687:  Called dyn_compile
 *               ebuild.sh, line 1025:  Called qa_call 'src_compile'
 *               ebuild.sh, line   44:  Called src_compile
 *   itpp-4.0.0_rc2.ebuild, line   60:  Called econf '--enable-html-doc'
'--disable-debug' '--without-lapack' '--without-blas --without-lapack'
 *               ebuild.sh, line  624:  Called die

Going to /var/tmp/portage/sci-libs/itpp-4.0.0_rc2/work/itpp-4.0.0-rc2
and running configure with these options DOES succeed

Reproducible: Always

Steps to Reproduce:
1. try to build sci-libs/itpp-4.0.0_rc2
2.
3.

------- Comment #1 From Markus Dittrich 2007-10-09 13:24:13 0000 -------
Hi Helmut,

Thanks for the note -- this was a weird bug!
Anyway, I believe I just fixed it in portage cvs.
Please re-sync in an hour or so and try again;
feel free to re-open this bug should the problem 
persists.

Thanks,
Markus