[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: $CC and intel icc/ecc compiler
From: |
Allan Sandfeld Jensen |
Subject: |
Re: $CC and intel icc/ecc compiler |
Date: |
Thu, 10 Apr 2003 11:38:19 +0200 |
User-agent: |
KMail/1.5.9 |
On Thursday 10 April 2003 04:20, Samuel Meder wrote:
> On Wed, 2003-04-09 at 20:52, Bob Friesenhahn wrote:
> > It seems to me that both the before and after code is incorrect. The
> > reason why I say is is that $CC may contain the command plus some
> > arguments which are required for it to behave in some consistent way.
>
> So it is naive to think that those things should go into CFLAGS? Off the
> top of my head I can't think of a single scenario where I'd want them in
> $CC rather than $CFLAGS. Do you have one?
>
Actually "-Wl,-rpath,/opt/intel/compiler70/ia32/lib" is a good one to put in
$CC instead of $CFLAGS, because it needs to be first and always included. But
usually I just edit the icc-shellscript directly and add it to the iccbin
call.
What about just matching on icc*|ecc*? This way we can also catch anyone
trying to call iccbin directly.
`Allan
- Re: $CC and intel icc/ecc compiler, (continued)
- Re: $CC and intel icc/ecc compiler, Charles Wilson, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Bob Friesenhahn, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Samuel Meder, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Bob Friesenhahn, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Samuel Meder, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Bob Friesenhahn, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Charles Wilson, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Robert Boehne, 2003/04/09
- Re: $CC and intel icc/ecc compiler, Allan Sandfeld Jensen, 2003/04/15
- Re: $CC and intel icc/ecc compiler, Samuel Meder, 2003/04/20
- Re: $CC and intel icc/ecc compiler,
Allan Sandfeld Jensen <=