Re: [petsc-users] Failed to configure on Windows with latest Intel OneAPI

2023-06-01 Thread Barry Smith
If you try to access it from the Windows side the file is a link that is not easily dealt with. You need to find some way to access and send the file from Cygwin or copy it to another machine with a sane operating system. Barry > On Jun 1, 2023, at 9:12 PM, Hawk Shaw wrote: > > When I

Re: [petsc-users] Failed to configure on Windows with latest Intel OneAPI

2023-06-01 Thread Barry Smith
Please send configure.log to petsc-ma...@mcs.anl.gov > On Jun 1, 2023, at 10:01 AM, Hawk Shaw wrote: > > Hi, > > I failed to configue PETSc on Windows with latest Intel OneAPI toolkit: > > ./configure --with-cc="win32fe cl" --with-cxx="win32fe cl"

[petsc-users] Failed to configure on Windows with latest Intel OneAPI

2023-06-01 Thread Hawk Shaw
Hi, I failed to configue PETSc on Windows with latest Intel OneAPI toolkit: ./configure --with-cc="win32fe cl" --with-cxx="win32fe cl" --with-fc=0 \ --with-debugging=0 --with-shared-libraries=0 --with-x=0 --with-quad-precision=0 \ --with-threadcomm=1 --with-openmp=1 \

Re: [petsc-users] Gauss-Lobatto-Legendre Element Gradient -- Caught signal number 11 SEGV

2023-06-01 Thread Matthew Knepley
On Thu, Jun 1, 2023 at 1:46 AM Duan Junming via petsc-users < petsc-users@mcs.anl.gov> wrote: > Dear all, > > > I have a simple demo code attached below, which gives a segmentation > violation error. > > Can you help me with this problem? I think the problem is due to the > destroy function. > >