Summary: | Ebuild for Intel C++ compiler on AMD64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Heinemann <theine> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Ebuild
modified linker script environment variable definitions |
Description
Tobias Heinemann
2004-06-28 13:59:12 UTC
Created attachment 34350 [details]
Ebuild
Created attachment 34351 [details]
modified linker script
Created attachment 34352 [details]
environment variable definitions
well, i'm against this solution. Intel has already a beta version of a native i[c,f]c for IA32-EM64T (a.k.a iAMD64 ;-) ). We will put that version into portage as soon as it is available. Further, the icc ebuild is meant to provide a compiler that you can use with portage. (There are several ebuilds with icc USE-flags, yet use.mask'ed atm...) If you want or need to use i[c,f]c for IA32 on amd64, i'd suggest to use a 32bit chroot and compile anything there. Tobias: However, this ebuild you submitted is quite cool. There are errors, but using that script was a good idea. I'll discuss implementing a kind of multilib setup for the intel compilers with the rest of the team. I guess we can wait quite a while until there's reasonable stable version of ifc/icc for IA32-EM64T, but I agree, this ebuild is too much of a dirty hack to enter the official portage tree. Anybody who's interested in this solution can get it here. |