Re: [EXTERNAL] Re: Adding support for Intel compilers

Bill Deegan <[email protected]>
Newsgroups gmane.comp.programming.tools.scons.user
Message-ID <CAEyG4CGjjKFJv+QmpeodGMiYb6s5yJqrWnwOfmksk4=SfzBRSw@mail.gmail.com>
I'd change:

env = Environment (
    CC = cc,
    CFLAGS = cflags,
    CPPDEFINES = defines,
    CPPPATH = cpppath,
    CXX = cxx,
    CXXFLAGS = cxxflags,
    ENV = environ,
    FORTRANFLAGS = fortranflags,
    FORTRAN = f90,
    FORTRANLIBS = libs_fortran,
    FORTRANPATH = fortranpath,
    LIBPATH = libpath,
    LINKFLAGS = linkflags )

to:
env = Environment (tools=[], ENV = environ)


then set each of these via env['VARNAME'] = value.
CC = cc,
CFLAGS = cflags,
CPPDEFINES = defines,
CPPPATH = cpppath,
CXX = cxx,
CXXFLAGS = cxxflags,
ENV = environ,
FORTRANFLAGS = fortranflags,
FORTRAN = f90,
FORTRANLIBS = libs_fortran,
FORTRANPATH = fortranpath,
LIBPATH = libpath,
LINKFLAGS = linkflags

Then

env.Tool('intelc')
env.Tool('ilink')
env.Tool('ifort')
env.Tool('ar')
env.Tool('gas')


What's your shell's PATH set to?
Is gcc installed?
Which os/platform/distro?

-Bill
Discord server might be helpful for more interactive interaction..

On Wed, Jun23, 2021 at 4:15 PM Jason Kenny <[email protected]> wrote:

> I don’t see, from what I can see at the moment, anything loading the
> intelc.py tool. It looks like you are loading the default tools which I
> believe will try to load gcc.py tool and then the logic here is to override
> the CC, CXX for the compiler you want to be used.
>
>
>
> Jason
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Jason Kenny <[email protected]>
> *Sent: *Wednesday, June 23, 2021 6:02 PM
> *To: *SCons users mailing list <[email protected]>
> *Subject: *Re: [Scons-users] [EXTERNAL] Re: Adding support for Intel
> compilers
>
>
>
> Can you resent config/pleiades_intel.py as .txt file.. it is being removed
> as a possible malicious script.
>
>
>
> Also to ask Bill Deegan question. Is this based on
> https://github.com/enzo-project/enzo-e
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fenzo-project%2Fenzo-e&data=04%7C01%7C%7Ca1801b98bd5f43114c1608d9369ae802%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637600861206506817%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jKyZJCkWialvQWOBbdzFlV162QjYMJLbwd8CSQrLL14%3D&reserved=0>
> ??
>
>
>
> Jason
>
>
>
> *From:* Scons-users <[email protected]> * On Behalf Of *Kokron,
> Daniel S. (ARC-606.2)[InuTeq, LLC] via Scons-users
> *Sent:* Wednesday, June 23, 2021 5:56 PM
> *To:* SCons users mailing list <[email protected]>
> *Cc:* Kokron, Daniel S. (ARC-606.2)[InuTeq, LLC] <[email protected]
> >
> *Subject:* Re: [Scons-users] [EXTERNAL] Re: Adding support for Intel
> compilers
>
>
>
> Jason,
>
> I think I see what you are after.
>
>
>
> The SConstruct file in the enzo-e tree includes the following (see
> attached)
>
>
>
> elif (arch == "pleiades_intel"): from pleiades_intel import *
>
>
>
> config/pleiades_intel.py is attached.
>
>
>
> env = Environment (
>
>      CC           = cc,
>
>      CFLAGS       = cflags,
>
>      CPPDEFINES   = defines,
>
>      CPPPATH      = cpppath,
>
>      CXX          = cxx,
>
>      CXXFLAGS     = cxxflags,
>
>      ENV          = environ,
>
>      FORTRANFLAGS = fortranflags,
>
>      FORTRAN      = f90,
>
>      FORTRANLIBS  = libs_fortran,
>
>      FORTRANPATH  = fortranpath,
>
>      LIBPATH      = libpath,
>
>      LINKFLAGS    = linkflags )
>
>
>
> *From: *Scons-users <[email protected]> on behalf of Jason
> Kenny <[email protected]>
> *Reply-To: *SCons users mailing list <[email protected]>
> *Date: *Wednesday, June 23, 2021 at 5:34 PM
> *To: *SCons users mailing list <[email protected]>
> *Subject: *[EXTERNAL] Re: [Scons-users] Adding support for Intel compilers
>
>
>
> Can you share how you set up your Environment object. I can take a quick
> look at what you need to tweak to get it running correctly.
>
>
>
> Jason
>
>
>
> *From:* Scons-users <[email protected]> *On Behalf Of *Jason
> Kenny
> *Sent:* Wednesday, June 23, 2021 4:58 PM
> *To:* SCons users mailing list <[email protected]>
> *Subject:* Re: [Scons-users] Adding support for Intel compilers
>
>
>
>
>
> I believe you need to make sure you load the c++/gcc tool as well as this
> adds other items you need to have defined that the intelc.py tool does not
> handle if I recall correctly with pure SCons
>
>
>
> You should be able to find some examples of how in Pure SCons to create
> the Environment correctly in the user list.
>
>
>
> I have support for icc in my extension for Scons called Parts. In fact, I
> am adding support for the new icx version that should be replacing the
> existing/classic icc case for the next drop.
>
>
>
> Jason
>
> *From:* Scons-users <[email protected]> on behalf of Kokron,
> Daniel S. (ARC-606.2)[InuTeq, LLC] via Scons-users <[email protected]>
> *Sent:* Wednesday, June 23, 2021 4:14 PM
> *To:* [email protected] <[email protected]>
> *Cc:* Kokron, Daniel S. (ARC-606.2)[InuTeq, LLC] <[email protected]
> >
> *Subject:* [Scons-users] Adding support for Intel compilers
>
>
>
> I have a user on our system whose application (ENZO-E) depends on SCons.
> We have a working build that uses GNU compilers however I would like to
> test the code using Intel compilers as they typically provide better
> performance on our system.  I have already worked through some issues by
> modifying SCons/Tool/intelc.py so it can find our installation tree.
>
>
>
> -            for d in
> glob.glob('/opt/intel/compilers_and_libraries_%s/linux'%version):
>
> +            for d in
> glob.glob('/nasa/intel/Compiler/2020.4.304/compilers_and_libraries_%s/linux'%version):
>
>
>
> I have tried duplicating the set of files used for GNU compilers (gcc.py,
> g++.py and gxx.py), replacing GNU compiler names with appropriate names of
> Intel compilers.  However, nothing I’ve tried has been able to resolve the
> following.
>
>
>
> scons: *** While building `['cello.o']' from `['cello.cpp']': Don't know
> how to build from a source file with suffix `.cpp'.  Expected a suffix in
> this list: ['.c', '.m', '.i', '.fpp', '.FPP', '.I', '.f77', '.F77', '.i90',
> '.I90', '.f95', '.F95', '.f03', '.F03', '.f08', '.F08', '.s', '.asm',
> '.ASM', '.spp', '.SPP', '.sx', '.S', '.d'].
>
>
>
> Can anyone offer some guidance on how to proceed?
>
>
>
> Daniel Kokron
> RedLine Performance Solutions
> SciCon/APP group
>
> --
>
>
>
>
> _______________________________________________
> Scons-users mailing list
> [email protected]
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users
FD6664EB8FF948AEB40957F23E585DE4.png (image/png, 140 B) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.