

Rebuilding gcc with icc wouldn't help anyway, because all the build would do is build xgcc using icc (if it's possible at all.) Eventually the gcc build would build a compiler to build itself.Kihaji wrote:Just re-reading this thread and saw this. Why in the name of jebus would you want to compile one compiler with a different one?stonent wrote:The real test is compiling a kernel, complete with vector optimizations.
I'm drooling! Maybe even build GCC under ICC! Super fast emerges!
And a listing of apps would be sweet.
well, I only get ICC 7:yamakawa wrote:I tried this codeand see what I got...Code: Select all
# emerge -evp world|grep iccCode: Select all
[ebuild N ] x11-misc/xscreensaver-4.14-r1 +gnome +gtk +gtk2 +icc +jpeg -kerberos -krb4 +opengl +pam -xinerama 3,894 kB [ebuild N ] dev-lang/icc-8.0.055 0 kB *1
Code: Select all
# emerge -evp world|grep icc
[ebuild N ] dev-lang/icc-7.1.006 0 kB
Ahh, it was my CFLAGS it puked on -march=pentium3 so I stripped it down to -O3 and it worked ok.stonent wrote:However:Code: Select all
Beginning configuration for bash-2.05b-release for i686-pc-linux-gnu checking for i686-pc-linux-gnu-gcc... icc checking for C compiler default output... configure: error: C compiler cannot cr eate executables !!! ERROR: app-shells/bash-2.05b-r9 failed. !!! Function econf, Line 339, Exitcode 77 !!! econf failed
Code: Select all
Aurora bin # icc test.c Aurora bin # file a.out a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs), not stripped Aurora bin #

Code: Select all
Aurora root # emerge -U -p --deep world
>>> --upgradeonly implies --update... adding --update to options.
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuild N ] dev-lang/icc-7.1.006
[ebuild U ] media-libs/libsdl-1.2.7 [1.2.6-r3]
[ebuild UD] media-sound/lame-3.93.1-r1 [3.95.1]
[ebuild U ] media-sound/cdparanoia-3.9.8-r1 [3.9.8]
[ebuild U ] dev-util/yacc-1.9.1-r2 [1.9.1-r1]
[ebuild U ] app-text/ghostscript-7.07.1-r1 [7.07.1]
[ebuild U ] media-libs/imlib2-1.1.0 [1.0.6-r1]
[ebuild U ] x11-libs/libast-0.5-r2 [0.5-r1]Code: Select all
Aurora root # emerge -p icc
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] dev-lang/icc-7.1.006
Aurora root # ACCEPT_KEYWORDS="~x86" emerge -p icc
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] dev-lang/icc-8.0.055
Did you edit /etc/ld.so.conf directly? It is generated from LDPATH entries in the files in /etc/env.d. The icc8 ebuild should include /etc/env.d/05icc-ifc with the corrent entry.nagzi wrote:I have a bit of a prob with icc. i'v gotten icc to install and works nicely and all. but the prob that i'v having is that its entry in /etc/ld.so.conf always seems to get removed with every new emerge. is there a way that i can get icc's entry in it to stay?
echo >> "dev-lang/icc ~x86" >> /etc/portage/package.keywordsstonent wrote:Now that I have ICC 8, I've noticed when I try to do a emerge -U --deep -p world, it wants to install ICC 7.1
as N
Code: Select all
Aurora root # emerge -U -p --deep world >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] dev-lang/icc-7.1.006 [ebuild U ] media-libs/libsdl-1.2.7 [1.2.6-r3] [ebuild UD] media-sound/lame-3.93.1-r1 [3.95.1] [ebuild U ] media-sound/cdparanoia-3.9.8-r1 [3.9.8] [ebuild U ] dev-util/yacc-1.9.1-r2 [1.9.1-r1] [ebuild U ] app-text/ghostscript-7.07.1-r1 [7.07.1] [ebuild U ] media-libs/imlib2-1.1.0 [1.0.6-r1] [ebuild U ] x11-libs/libast-0.5-r2 [0.5-r1]Something is screwy. I just re-emerged ICC8 just to be sure, but it didn't help.Code: Select all
Aurora root # emerge -p icc These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] dev-lang/icc-7.1.006 Aurora root # ACCEPT_KEYWORDS="~x86" emerge -p icc These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-lang/icc-8.0.055


I have never used it but I think you also need the icc USE flag - but not sure if even that's enough..ett_gramse_nap wrote:I've searched around a bit but haven't found out how to use icc with portage. I don't think `emerge icc` is enough...

The author is talking about how he compiled a series 2.4 kernel using a series of patches. Good practice of my Japanesehaugboel wrote:Here is a link to a japanesepdf file describing what have to be done in order to compile a kernel with icc 8.0.
http://www.suri.co.jp/~ohkubo-k/linux/i ... 030801.pdf
Unfortunately my japanese skills are rather limitedbut if anybody feels like translating it to the rest of the world it would be rocking.
[/url]