Bug 97929 - Clear the tree of icc and ifc useflags.
|
Bug#:
97929
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: bicatali@gentoo.org
|
Reported By: kugelfang@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: Clear the tree of icc and ifc useflags.
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-07-04 13:03 0000
|
Let's use something like [[ $(tc-getCC) = icc ]] when deciding to apply
patches,
k?
Also, i'll tweak fortran.eclass to use ifc patches as well.
./dev-libs/blitz/blitz-0.6.ebuild:10:IUSE="icc"
./dev-libs/blitz/blitz-0.8.ebuild:12:IUSE="icc"
./dev-libs/blitz/blitz-0.7.ebuild:14:IUSE="icc"
./dev-libs/boost/boost-1.31.0.ebuild:17:IUSE="icc"
./dev-libs/boost/boost-1.30.0.ebuild:15:IUSE="icc"
./dev-libs/boost/boost-1.30.2.ebuild:13:IUSE="icc"
./dev-libs/boost/boost-1.32.0.ebuild:16:IUSE="icc"
./dev-libs/boost/boost-1.32.0-r1.ebuild:16:IUSE="icc"
./dev-libs/boost/boost-1.32.0-r2.ebuild:16:IUSE="icc debug threads threadsonly
static"
./dev-libs/boost/boost-1.32.0-r3.ebuild:16:IUSE="debug icc pyste static threads
threadsonly"
./dev-libs/boost/boost-1.32.0-r4.ebuild:16:IUSE="debug doc icc pyste static
threads threadsonly"
./games-board/crafty/crafty-19.1.ebuild:12:IUSE="icc"
./games-board/crafty/crafty-19.8.ebuild:14:IUSE="icc no-opts"
./games-board/crafty/crafty-19.15.ebuild:14:IUSE="icc no-opts"
./games-board/crafty/crafty-19.12.ebuild:14:IUSE="icc no-opts"
./games-board/crafty/crafty-19.18.ebuild:14:IUSE="icc no-opts"
./games-board/crafty/crafty-19.19.ebuild:14:IUSE="icc no-opts"
./media-gfx/xd3d/xd3d-8.2.1.ebuild:16:IUSE="icc"
./x11-libs/qt/qt-3.3.3-r1.ebuild:21:IUSE="cups debug doc firebird gif icc ipv6
mysql nas odbc opengl postgres sqlite xinerama zlib immqt immqt-bc"
./sci-libs/blas-reference/blas-reference-19940131-r1.ebuild:16:IUSE="ifc"
./sci-libs/blas-reference/blas-reference-19940131.ebuild:15:IUSE="ifc"
./sci-libs/lapack-atlas/lapack-atlas-3.6.0.ebuild:20:IUSE="ifc doc"
./sci-libs/lapack-reference/lapack-reference-3.0.ebuild:18:IUSE="ifc"
./sci-libs/plplot/plplot-5.3.1.ebuild:18:IUSE="debug doc fortran gd-external
gnome ifc java jpeg png python tcltk tetex truetype X itcl octave"
./sci-libs/plplot/plplot-5.5.1.ebuild:18:IUSE="debug doc fortran gd-external
gnome ifc java jpeg png python tcltk tetex truetype X itcl octave"
./sci-libs/plplot/plplot-5.5.2.ebuild:18:IUSE="debug doc fortran gd-external
gnome ifc java jpeg png python tcltk tetex truetype X itcl octave"
./sci-mathematics/mathomatic/mathomatic-12.3.1.ebuild:14:IUSE="icc"
./sci-mathematics/octave/octave-2.1.57-r1.ebuild:15:IUSE="emacs static readline
zlib tetex hdf5 mpi ifc blas"
./sci-mathematics/octave/octave-2.1.69.ebuild:15:IUSE="emacs static readline
zlib tetex hdf5 mpi ifc blas"
./sci-mathematics/scilab/scilab-2.7-r3.ebuild:15:IUSE="tcltk gtk ifc"
./sci-mathematics/scilab/scilab-3.1.1.ebuild:14:IUSE="ifc ocaml tcltk atlas gtk
gtk2 Xaw3d"
./sci-misc/camfr/camfr-1.2.ebuild:8:IUSE="ifc"
In case you still want to do something about this, here's an uptodate list:
$ pquery --raw --has-use=icc
dev-libs/blitz-0.6
dev-libs/blitz-0.7
dev-libs/blitz-0.8
dev-libs/blitz-0.9
games-board/crafty-20.13
games-board/crafty-20.14
sci-mathematics/mathomatic-12.4.5
sci-mathematics/mathomatic-12.5.13
sci-mathematics/mathomatic-12.5.20
sci-mathematics/mathomatic-12.6.4
sci-visualization/xd3d-8.2.1
sys-cluster/charm-5.9
---
$ pquery --raw --has-use=ifc
sci-libs/blas-reference-19940131-r2
sci-libs/lapack-atlas-3.6.0
sci-libs/lapack-atlas-3.6.0-r1
sci-libs/lapack-atlas-3.6.0-r2
sci-libs/lapack-atlas-3.7.11
sci-libs/lapack-atlas-3.7.11-r1
sci-libs/lapack-reference-3.0
sci-libs/lapack-reference-3.0-r1
sci-libs/lapack-reference-3.0-r2
sci-libs/plplot-5.5.2
sci-mathematics/octave-2.1.57-r1
sci-mathematics/octave-2.1.69
sci-mathematics/scilab-2.7-r3
sci-mathematics/scilab-3.1.1-r3
sci-physics/camfr-1.2
> Let's use something like [[ $(tc-getCC) = icc ]] when deciding to apply
> patches,
> k?
Yes, avoid icc and ifc use flags at most. Although some ebuilds do need them
for fetching (idb and acml are such examples), the solution above should be
used for compiling.
self-reminder:
* Packages with ifc use flag:
These ebuild should be cleaned of the flags:
sci-mathematics/octave: needs work
sci-libs/lapack-atlas: wait for alpha to stab >=3.8.x so we can punt older ones
sci-libs/plplot-5.5.2: needs work (see bug #204524 for newer version)
sci-libs/acml: binary package pulling ifc. will turn into a local flag
dev-lang/idb: same as acml
* Packages with icc use flag:
games-board/crafty: needs work
sys-cluster/charm: needs work
dev-libs/blitz: needs work
sci-mathematics/mathomatic: stabilize newer, then punt 12.6.5
dev-lang/idb: same situation as for ifc use flag
> sci-mathematics/octave
> sci-libs/lapack-atlas
> sci-libs/plplot
> games-board/crafty
> sys-cluster/charm
> dev-libs/blitz
> sci-mathematics/mathomatic
All done.
Tree cleaned of icc and ifc flags.
