Re: [petsc-users] win32fe?
Some additional notes on win32fe:
- PETSc uses cygwin python/make/shell etc for build tools - i.e they
all work with cygwin (aka unix) paths. However cl,icl etc work with
MS native paths. So win32fe parses the compiler options and converts
the cygwin paths to native paths before invoking windows compilers.
- And the compile targets used [in makefiles] assume compilers behave
like gcc (most unix compilers - essentially behave the same way -
except for some differences in compiler options). However MS
compilers require additional syntax restrictions - i.e options have
to be set in a particular order. Win32fe does this reordering of
compiler options before invoking cl.
- And there are other quirks with MS build tools [like lib] that
win32fe handles - and gives a unix 'ar' like interface
Note: This was developed 20+ years ago - and only minor updates since
then [as the primary developer has moved on]
Satish
On Tue, 31 Jan 2023, Satish Balay via petsc-users wrote:
> Assuming 'icx/ifx' compiler options are same as 'icl/ifort' - you can try:
>
> --with-cc='win32fe icl --use icx' --with-cxx='win32fe icl --use icx'
> --with-fc='win32e ifort --use ifx'
>
> Also check 'win32fe --help'
>
> However I think the above assumption [i.e icx is a drop in replacement for
> icl] is likely invalid - so this might not work.
>
> Note: petsc/main has shell wrappers for 'win32fe icl' - so one could add
> similar wrappers for icx - if the above would work.
>
> balay@p1 /home/balay/petsc (main =)
> $ cat lib/petsc/bin/win32fe/win_cl
> #!/usr/bin/env sh
> #
> # Wrapper for Microsoft Windows cl using win32fe as a full path compiler
> #
> p=`dirname $0`
> ${p}/win32fe cl $*
>
>
> The sources for win32fe are at https://bitbucket.org/petsc/win32fe
>
> And 'win32fe icl --verbose' is useful to understand the commands its invoking
> internally.
>
> Satish
>
> On Tue, 31 Jan 2023, Daniel Stone wrote:
>
> > Hello all,
> >
> > I am currently having to figure out a way to get petsc working on windows,
> > using compilers from the intel oneAPI package. This means new compiler
> > names, such as "icx" for the c compiler and "ifx" for the fortran one.
> >
> > I see from the installation instructions, and from old notes from a
> > collegue, how to set up the cygwin environment and to use, e.g.,
> > --with-cc="win32fe icl" (if using an older intel compiler) when configuring.
> >
> > Unfortunately,win32fe only workes with a number of fixed (older) compilers,
> > and simply cannot be made to work with icx or ifx, as far as I can see.
> > When I try to not use the compilers without win32fe (e.g. --withcc=icx"),
> > I get a slew of problems when the configure script trys to compile and link
> > test c programs. It seems that icx works fine, but gets extemely confused
> > when having to target output files to, e.g., /tmp or /anywhere/non/trivial,
> > when running under cygwin. Is this the sort of problem that win32fe is
> > intended to solve?
> >
> > I can't find any source code for win32fe, nor really any explainations of
> > what it's supposed to be doing or how it works. Since it looks like I have
> > to find a way of making it work with icx and ifx, I'm a bit stuck. Can
> > anyone
> > provide any insight as to what/how win32 does, or where I can look for some?
> >
> > Many thanks,
> >
> > Daniel
> >
>
Re: [petsc-users] win32fe?
Assuming 'icx/ifx' compiler options are same as 'icl/ifort' - you can try:
--with-cc='win32fe icl --use icx' --with-cxx='win32fe icl --use icx'
--with-fc='win32e ifort --use ifx'
Also check 'win32fe --help'
However I think the above assumption [i.e icx is a drop in replacement for icl]
is likely invalid - so this might not work.
Note: petsc/main has shell wrappers for 'win32fe icl' - so one could add
similar wrappers for icx - if the above would work.
balay@p1 /home/balay/petsc (main =)
$ cat lib/petsc/bin/win32fe/win_cl
#!/usr/bin/env sh
#
# Wrapper for Microsoft Windows cl using win32fe as a full path compiler
#
p=`dirname $0`
${p}/win32fe cl $*
The sources for win32fe are at https://bitbucket.org/petsc/win32fe
And 'win32fe icl --verbose' is useful to understand the commands its invoking
internally.
Satish
On Tue, 31 Jan 2023, Daniel Stone wrote:
> Hello all,
>
> I am currently having to figure out a way to get petsc working on windows,
> using compilers from the intel oneAPI package. This means new compiler
> names, such as "icx" for the c compiler and "ifx" for the fortran one.
>
> I see from the installation instructions, and from old notes from a
> collegue, how to set up the cygwin environment and to use, e.g.,
> --with-cc="win32fe icl" (if using an older intel compiler) when configuring.
>
> Unfortunately,win32fe only workes with a number of fixed (older) compilers,
> and simply cannot be made to work with icx or ifx, as far as I can see.
> When I try to not use the compilers without win32fe (e.g. --withcc=icx"),
> I get a slew of problems when the configure script trys to compile and link
> test c programs. It seems that icx works fine, but gets extemely confused
> when having to target output files to, e.g., /tmp or /anywhere/non/trivial,
> when running under cygwin. Is this the sort of problem that win32fe is
> intended to solve?
>
> I can't find any source code for win32fe, nor really any explainations of
> what it's supposed to be doing or how it works. Since it looks like I have
> to find a way of making it work with icx and ifx, I'm a bit stuck. Can
> anyone
> provide any insight as to what/how win32 does, or where I can look for some?
>
> Many thanks,
>
> Daniel
>
[petsc-users] win32fe?
Hello all, I am currently having to figure out a way to get petsc working on windows, using compilers from the intel oneAPI package. This means new compiler names, such as "icx" for the c compiler and "ifx" for the fortran one. I see from the installation instructions, and from old notes from a collegue, how to set up the cygwin environment and to use, e.g., --with-cc="win32fe icl" (if using an older intel compiler) when configuring. Unfortunately,win32fe only workes with a number of fixed (older) compilers, and simply cannot be made to work with icx or ifx, as far as I can see. When I try to not use the compilers without win32fe (e.g. --withcc=icx"), I get a slew of problems when the configure script trys to compile and link test c programs. It seems that icx works fine, but gets extemely confused when having to target output files to, e.g., /tmp or /anywhere/non/trivial, when running under cygwin. Is this the sort of problem that win32fe is intended to solve? I can't find any source code for win32fe, nor really any explainations of what it's supposed to be doing or how it works. Since it looks like I have to find a way of making it work with icx and ifx, I'm a bit stuck. Can anyone provide any insight as to what/how win32 does, or where I can look for some? Many thanks, Daniel
Re: [petsc-users] win32fe icl won't work
Yes, removing --with-batch works. Thanks a lot. On Tue, Dec 17, 2019 at 11:58 AM Balay, Satish wrote: > You don't need --with-batch for this usage [esp with --with-mpi=0] > > > Also suggest using latest petsc version [and update your code to it] > > Satish > > > On Tue, 17 Dec 2019, Sam Guo wrote: > > > It is better but the configuration still failed. > > > > On Tue, Dec 17, 2019 at 8:42 AM Balay, Satish wrote: > > > > > Alternative is to update PATH so that link.exe from compiler is before > the > > > one from cygwin. > > > > > > I have it at '/cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > > 14.0/VC/BIN/amd64/link.exe' so would do: > > > > > > export PATH='/cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > > 14.0/VC/BIN/amd64':$PATH > > > > > > And verify with: > > > > > > balay@ps4 ~ > > > $ which link.exe > > > /cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > > 14.0/VC/BIN/amd64/link.exe > > > > > > balay@ps4 ~ > > > $ > > > > > > > > > Satish > > > > > > > > > On Tue, 17 Dec 2019, Sam Guo wrote: > > > > > > > I cannot move link.exe: > > > > $ mv link.exe link_cyg.exe > > > > mv: cannot move 'link.exe' to 'link_cyg.exe': Permission denied > > > > > > > > I figure I need admin privilege. > > > > > > > > On Mon, Dec 16, 2019 at 8:30 PM Balay, Satish > wrote: > > > > > > > > > Try: > > > > > > > > > > mv /usr/bin/link.exe /usr/bin/link-cygwin.exe > > > > > > > > > > And rerun configure > > > > > > > > > > Satish > > > > > > > > > > -- > > > > > > > > > > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > > > > > Thanks for the quick response. I attach the configure.log again. > > > > > > > > > > > > icl is found > > > > > > $ icl > > > > > > Intel(R) C++ Intel(R) 64 Compiler for applications running on > > > Intel(R) > > > > > 64, > > > > > > Version 18.0.3.210 Build 20180410 > > > > > > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > > > > > > icl: command line error: no files specified; for help type "icl > > > /help" > > > > > > > > > > > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish > > > > wrote: > > > > > > > > > > > > > The attached configure.log is a link file. Can you resend the > log > > > from > > > > > > > PETSC_ARCH/lib/petsc/conf > > > > > > > > > > > > > > Also can you verify that you followed instructions from > > > > > > > > > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > > > > > > [its not explicitly specified - but you need to run the > correct cmd > > > > > that > > > > > > > sets up Intel compiler - instead of the MS compiler] > > > > > > > > > > > > > > i.e verify 'icl' works from cygwin/bash - before attempting > > > configure. > > > > > > > > > > > > > > Satish > > > > > > > > > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > > > > > > > > > Dear PETSc dev team, > > > > > > > >I tried to compile petsc using intel compiler win32fe icl > on > > > > > cygwin > > > > > > > but > > > > > > > > encountered error. By the way, I am able to compile using > visual > > > > > studio > > > > > > > > compiler win32fe cl. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > === > > > > > > > > Configuring PETSc to compile on your system > > > > > > > > > > > > > > > > > > > > > > > > === > > > > > > > > > > > > > > > > > > > > > > > > === > > > > > > > > Warning: "with-clean" is specified. Removing all build files > from > > > > > > > > > > > > > > > > > > > > > > > > arch-starccmplus_s=== > > > > > > > > TESTING: checkCCompiler from > > > > > > > > > > > > > > > > > > > > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > > > > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see > > > > > configure.log for > > > > > > > > details): > > > > > > > > > > > > > > > > > > > > > > > > --- > > > > > > > > C compiler you provided with -with-cc=win32fe icl does not > work. > > > > > > > > Cannot compile/link C with > > > > > > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe > > > icl. > > > > > > > > > > > > > > > > > > > > > > > > *** > > > > > > > > > > > > > > > > BR, > > > > > > > > Sam > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [petsc-users] win32fe icl won't work
You don't need --with-batch for this usage [esp with --with-mpi=0] Also suggest using latest petsc version [and update your code to it] Satish On Tue, 17 Dec 2019, Sam Guo wrote: > It is better but the configuration still failed. > > On Tue, Dec 17, 2019 at 8:42 AM Balay, Satish wrote: > > > Alternative is to update PATH so that link.exe from compiler is before the > > one from cygwin. > > > > I have it at '/cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > 14.0/VC/BIN/amd64/link.exe' so would do: > > > > export PATH='/cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > 14.0/VC/BIN/amd64':$PATH > > > > And verify with: > > > > balay@ps4 ~ > > $ which link.exe > > /cygdrive/c/Program Files (x86)/Microsoft Visual Studio > > 14.0/VC/BIN/amd64/link.exe > > > > balay@ps4 ~ > > $ > > > > > > Satish > > > > > > On Tue, 17 Dec 2019, Sam Guo wrote: > > > > > I cannot move link.exe: > > > $ mv link.exe link_cyg.exe > > > mv: cannot move 'link.exe' to 'link_cyg.exe': Permission denied > > > > > > I figure I need admin privilege. > > > > > > On Mon, Dec 16, 2019 at 8:30 PM Balay, Satish wrote: > > > > > > > Try: > > > > > > > > mv /usr/bin/link.exe /usr/bin/link-cygwin.exe > > > > > > > > And rerun configure > > > > > > > > Satish > > > > > > > > -- > > > > > > > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > > > Thanks for the quick response. I attach the configure.log again. > > > > > > > > > > icl is found > > > > > $ icl > > > > > Intel(R) C++ Intel(R) 64 Compiler for applications running on > > Intel(R) > > > > 64, > > > > > Version 18.0.3.210 Build 20180410 > > > > > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > > > > > icl: command line error: no files specified; for help type "icl > > /help" > > > > > > > > > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish > > wrote: > > > > > > > > > > > The attached configure.log is a link file. Can you resend the log > > from > > > > > > PETSC_ARCH/lib/petsc/conf > > > > > > > > > > > > Also can you verify that you followed instructions from > > > > > > > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > > > > > [its not explicitly specified - but you need to run the correct cmd > > > > that > > > > > > sets up Intel compiler - instead of the MS compiler] > > > > > > > > > > > > i.e verify 'icl' works from cygwin/bash - before attempting > > configure. > > > > > > > > > > > > Satish > > > > > > > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > > > > > > > Dear PETSc dev team, > > > > > > >I tried to compile petsc using intel compiler win32fe icl on > > > > cygwin > > > > > > but > > > > > > > encountered error. By the way, I am able to compile using visual > > > > studio > > > > > > > compiler win32fe cl. > > > > > > > > > > > > > > > > > > > > > > > > > > === > > > > > > > Configuring PETSc to compile on your system > > > > > > > > > > > > > > > > > > > === > > > > > > > > > > > > > > > > > > > === > > > > > > > Warning: "with-clean" is specified. Removing all build files from > > > > > > > > > > > > > > > > > > > arch-starccmplus_s=== > > > > > > > TESTING: checkCCompiler from > > > > > > > > > > > > > > > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > > > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see > > > > configure.log for > > > > > > > details): > > > > > > > > > > > > > > > > > > > --- > > > > > > > C compiler you provided with -with-cc=win32fe icl does not work. > > > > > > > Cannot compile/link C with > > > > > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe > > icl. > > > > > > > > > > > > > > > > > > > *** > > > > > > > > > > > > > > BR, > > > > > > > Sam > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [petsc-users] win32fe icl won't work
Alternative is to update PATH so that link.exe from compiler is before the one from cygwin. I have it at '/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/amd64/link.exe' so would do: export PATH='/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/amd64':$PATH And verify with: balay@ps4 ~ $ which link.exe /cygdrive/c/Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/amd64/link.exe balay@ps4 ~ $ Satish On Tue, 17 Dec 2019, Sam Guo wrote: > I cannot move link.exe: > $ mv link.exe link_cyg.exe > mv: cannot move 'link.exe' to 'link_cyg.exe': Permission denied > > I figure I need admin privilege. > > On Mon, Dec 16, 2019 at 8:30 PM Balay, Satish wrote: > > > Try: > > > > mv /usr/bin/link.exe /usr/bin/link-cygwin.exe > > > > And rerun configure > > > > Satish > > > > -- > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > Thanks for the quick response. I attach the configure.log again. > > > > > > icl is found > > > $ icl > > > Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) > > 64, > > > Version 18.0.3.210 Build 20180410 > > > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > > > icl: command line error: no files specified; for help type "icl /help" > > > > > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish wrote: > > > > > > > The attached configure.log is a link file. Can you resend the log from > > > > PETSC_ARCH/lib/petsc/conf > > > > > > > > Also can you verify that you followed instructions from > > > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > > > [its not explicitly specified - but you need to run the correct cmd > > that > > > > sets up Intel compiler - instead of the MS compiler] > > > > > > > > i.e verify 'icl' works from cygwin/bash - before attempting configure. > > > > > > > > Satish > > > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > > > Dear PETSc dev team, > > > > >I tried to compile petsc using intel compiler win32fe icl on > > cygwin > > > > but > > > > > encountered error. By the way, I am able to compile using visual > > studio > > > > > compiler win32fe cl. > > > > > > > > > > > > > > > > === > > > > > Configuring PETSc to compile on your system > > > > > > > > > > > === > > > > > > > > > > > === > > > > > Warning: "with-clean" is specified. Removing all build files from > > > > > > > > > > > arch-starccmplus_s=== > > > > > TESTING: checkCCompiler from > > > > > > > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see > > configure.log for > > > > > details): > > > > > > > > > > > --- > > > > > C compiler you provided with -with-cc=win32fe icl does not work. > > > > > Cannot compile/link C with > > > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > > > > > > > > > > > *** > > > > > > > > > > BR, > > > > > Sam > > > > > > > > > > > > > > > > > > > > >
Re: [petsc-users] win32fe icl won't work
I cannot move link.exe: $ mv link.exe link_cyg.exe mv: cannot move 'link.exe' to 'link_cyg.exe': Permission denied I figure I need admin privilege. On Mon, Dec 16, 2019 at 8:30 PM Balay, Satish wrote: > Try: > > mv /usr/bin/link.exe /usr/bin/link-cygwin.exe > > And rerun configure > > Satish > > -- > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > Thanks for the quick response. I attach the configure.log again. > > > > icl is found > > $ icl > > Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) > 64, > > Version 18.0.3.210 Build 20180410 > > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > > icl: command line error: no files specified; for help type "icl /help" > > > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish wrote: > > > > > The attached configure.log is a link file. Can you resend the log from > > > PETSC_ARCH/lib/petsc/conf > > > > > > Also can you verify that you followed instructions from > > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > > [its not explicitly specified - but you need to run the correct cmd > that > > > sets up Intel compiler - instead of the MS compiler] > > > > > > i.e verify 'icl' works from cygwin/bash - before attempting configure. > > > > > > Satish > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > Dear PETSc dev team, > > > >I tried to compile petsc using intel compiler win32fe icl on > cygwin > > > but > > > > encountered error. By the way, I am able to compile using visual > studio > > > > compiler win32fe cl. > > > > > > > > > > > > === > > > > Configuring PETSc to compile on your system > > > > > > > > === > > > > > > > > === > > > > Warning: "with-clean" is specified. Removing all build files from > > > > > > > > arch-starccmplus_s=== > > > > TESTING: checkCCompiler from > > > > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see > configure.log for > > > > details): > > > > > > > > --- > > > > C compiler you provided with -with-cc=win32fe icl does not work. > > > > Cannot compile/link C with > > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > > > > > > > > *** > > > > > > > > BR, > > > > Sam > > > > > > > > > > > > > >
Re: [petsc-users] win32fe icl won't work
BTW: You can try the branch 'balay/update-win32-link-check/maint' to check if you get an appropriate warning message for this usage. Satish On Tue, 17 Dec 2019, Balay, Satish wrote: > Try: > > mv /usr/bin/link.exe /usr/bin/link-cygwin.exe > > And rerun configure > > Satish > > -- > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > Thanks for the quick response. I attach the configure.log again. > > > > icl is found > > $ icl > > Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, > > Version 18.0.3.210 Build 20180410 > > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > > icl: command line error: no files specified; for help type "icl /help" > > > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish wrote: > > > > > The attached configure.log is a link file. Can you resend the log from > > > PETSC_ARCH/lib/petsc/conf > > > > > > Also can you verify that you followed instructions from > > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > > [its not explicitly specified - but you need to run the correct cmd that > > > sets up Intel compiler - instead of the MS compiler] > > > > > > i.e verify 'icl' works from cygwin/bash - before attempting configure. > > > > > > Satish > > > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > > > Dear PETSc dev team, > > > >I tried to compile petsc using intel compiler win32fe icl on cygwin > > > but > > > > encountered error. By the way, I am able to compile using visual studio > > > > compiler win32fe cl. > > > > > > > > > > > === > > > > Configuring PETSc to compile on your system > > > > > > > === > > > > > > > === > > > > Warning: "with-clean" is specified. Removing all build files from > > > > > > > arch-starccmplus_s=== > > > > TESTING: checkCCompiler from > > > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log > > > > for > > > > details): > > > > > > > --- > > > > C compiler you provided with -with-cc=win32fe icl does not work. > > > > Cannot compile/link C with > > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > > > > > > > *** > > > > > > > > BR, > > > > Sam > > > > > > > > > > > > >
Re: [petsc-users] win32fe icl won't work
Try: mv /usr/bin/link.exe /usr/bin/link-cygwin.exe And rerun configure Satish -- On Mon, 16 Dec 2019, Sam Guo wrote: > Thanks for the quick response. I attach the configure.log again. > > icl is found > $ icl > Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, > Version 18.0.3.210 Build 20180410 > Copyright (C) 1985-2018 Intel Corporation. All rights reserved. > icl: command line error: no files specified; for help type "icl /help" > > On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish wrote: > > > The attached configure.log is a link file. Can you resend the log from > > PETSC_ARCH/lib/petsc/conf > > > > Also can you verify that you followed instructions from > > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > > [its not explicitly specified - but you need to run the correct cmd that > > sets up Intel compiler - instead of the MS compiler] > > > > i.e verify 'icl' works from cygwin/bash - before attempting configure. > > > > Satish > > > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > > > Dear PETSc dev team, > > >I tried to compile petsc using intel compiler win32fe icl on cygwin > > but > > > encountered error. By the way, I am able to compile using visual studio > > > compiler win32fe cl. > > > > > > > > === > > > Configuring PETSc to compile on your system > > > > > === > > > > > === > > > Warning: "with-clean" is specified. Removing all build files from > > > > > arch-starccmplus_s=== > > > TESTING: checkCCompiler from > > > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > > UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for > > > details): > > > > > --- > > > C compiler you provided with -with-cc=win32fe icl does not work. > > > Cannot compile/link C with > > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > > > > > *** > > > > > > BR, > > > Sam > > > > > > > >
Re: [petsc-users] win32fe icl won't work
Thanks for the quick response. I attach the configure.log again. icl is found $ icl Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 18.0.3.210 Build 20180410 Copyright (C) 1985-2018 Intel Corporation. All rights reserved. icl: command line error: no files specified; for help type "icl /help" On Mon, Dec 16, 2019 at 7:03 PM Balay, Satish wrote: > The attached configure.log is a link file. Can you resend the log from > PETSC_ARCH/lib/petsc/conf > > Also can you verify that you followed instructions from > https://www.mcs.anl.gov/petsc/documentation/installation.html#windows > [its not explicitly specified - but you need to run the correct cmd that > sets up Intel compiler - instead of the MS compiler] > > i.e verify 'icl' works from cygwin/bash - before attempting configure. > > Satish > > On Mon, 16 Dec 2019, Sam Guo wrote: > > > Dear PETSc dev team, > >I tried to compile petsc using intel compiler win32fe icl on cygwin > but > > encountered error. By the way, I am able to compile using visual studio > > compiler win32fe cl. > > > > > === > > Configuring PETSc to compile on your system > > > === > > > === > > Warning: "with-clean" is specified. Removing all build files from > > > arch-starccmplus_s=== > > TESTING: checkCCompiler from > > > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > > UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for > > details): > > > --- > > C compiler you provided with -with-cc=win32fe icl does not work. > > Cannot compile/link C with > > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > > > *** > > > > BR, > > Sam > > > > configure.log Description: Binary data
Re: [petsc-users] win32fe icl won't work
The attached configure.log is a link file. Can you resend the log from PETSC_ARCH/lib/petsc/conf Also can you verify that you followed instructions from https://www.mcs.anl.gov/petsc/documentation/installation.html#windows [its not explicitly specified - but you need to run the correct cmd that sets up Intel compiler - instead of the MS compiler] i.e verify 'icl' works from cygwin/bash - before attempting configure. Satish On Mon, 16 Dec 2019, Sam Guo wrote: > Dear PETSc dev team, >I tried to compile petsc using intel compiler win32fe icl on cygwin but > encountered error. By the way, I am able to compile using visual studio > compiler win32fe cl. > > === > Configuring PETSc to compile on your system > === > === > Warning: "with-clean" is specified. Removing all build files from > arch-starccmplus_s=== > TESTING: checkCCompiler from > config.setCompilers(config/BuildSystem/config/setCompilers.py*** > UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for > details): > --- > C compiler you provided with -with-cc=win32fe icl does not work. > Cannot compile/link C with > /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. > *** > > BR, > Sam >
[petsc-users] win32fe icl won't work
Dear PETSc dev team, I tried to compile petsc using intel compiler win32fe icl on cygwin but encountered error. By the way, I am able to compile using visual studio compiler win32fe cl. === Configuring PETSc to compile on your system === === Warning: "with-clean" is specified. Removing all build files from arch-starccmplus_s=== TESTING: checkCCompiler from config.setCompilers(config/BuildSystem/config/setCompilers.py*** UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for details): --- C compiler you provided with -with-cc=win32fe icl does not work. Cannot compile/link C with /home/xianzhongg/dev/star/petsc/lib/petsc/bin/win32fe/win32fe icl. *** BR, Sam configure.log Description: Binary data
