[petsc-dev] [petsc-users] PETSc/VC12 compilation
Barry Smith
bsmith at mcs.anl.gov
Tue Jan 14 14:01:01 CST 2014
On Jan 14, 2014, at 1:46 PM, Aron Ahmadia <aron at ahmadia.net> wrote:
> You produce warnings all the time. When you ignore environment variables, or another variable is set that suggests a mistake in configuration.
Those few warnings all come in the initial start up of ./configure. Maybe it doesn’t matter but I fear if we spew many warnings they start to get ignored.
But why shouldn’t we default to setting the cxx compiler correctly? We currently try to do it for non-Windows systems.
Barry
>
> Or am I missing something here.
>
>
> On Tue, Jan 14, 2014 at 2:43 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
> On Jan 14, 2014, at 1:21 PM, Aron Ahmadia <aron at ahmadia.net> wrote:
>
> > I'd make it a warning, not a default.
>
> Why?
>
> We generally don’t produce “warnings” during configuration currently
>
> Barry
>
> >
> >
> > On Tue, Jan 14, 2014 at 2:16 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >
> > Hmm, if the user provides --with-cc='win32fe cl’ shouldn’t we automatically add --with-cxx='win32fe cl’ as well?
> >
> > It does not harm (right?) and will prevent this from hitting other people in the future.
> >
> > Barry
> >
> > Request-assigned: balay automatically add --with-cxx='win32fe cl’ if --with-cc='win32fe cl’ is provided?
> >
> >
> > On Jan 14, 2014, at 10:37 AM, Satish Balay <balay at mcs.anl.gov> wrote:
> >
> > > Try adding configure option: --with-cxx='win32fe cl'
> > >
> > > Satish
> > >
> > > On Tue, 14 Jan 2014, Abilash Nair wrote:
> > >
> > >> Hello all,
> > >>
> > >> I am trying to build petsc to use as a library on a visual C++ project.
> > >>
> > >> I configured the petsc (v3.4.3) with VC++ 2012 under the shell provided by
> > >> VC2012 with the following command (in cygwin):
> > >>
> > >> ./config/configure.py --with-mpi=0 --download-f2cblaslapack=1 --with-fc=0
> > >> --with-cc='win32fe cl' --with-debugging=1
> > >>
> > >> then I did a make all; make test while still in cygwin. I have sent the log
> > >> file outputs from these commands. As the files show, I am able to make with
> > >> no errors at all, however I am unable to execute any of the tests (error
> > >> being that a libstcc++.lib not found).
> > >>
> > >> I hope you would be able to suggest a path forward.
> > >>
> > >> Thanks!
> > >> Abilash.
> > >>
> > >
> >
> >
>
>
More information about the petsc-dev
mailing list