Hi all,

To be able to configure parrot to build with icc (the intel C
compiler) one currently needs a command line which looks like this:

perl Configure.pl --cc=icc --link=icc --ld=icc
--ccflags="<icc-header-path> -no-gcc" --ccwarn="-wd269 -Wall -Wcheck
-w2"

However, the only things which need to be specified here are:

(a) the cc setting
(b) the icc header path

the rest is set in the linux hints file.

So what's the problem you ask?  Well, to get icc to see its own header
files, one needs to specify the icc header path in the --ccflags
option.  This overwrites any settings given in the hints file.  It
would be great to give a configure command like this instead:

perl Configure.pl --cc=icc --ccflags-append=<icc-header-path>

then any settings that were already in ccflags can stay, and any hints
get added in without the developer having to remember what they are
and then add them in at the configure command line.

So, is it alright if I go and add yet another command line option to
configure?  Namely --ccflags-append?

Paul

Reply via email to