The only way you would have got 'main' branch is if '-b release' option was
missing [or there was some error in specifying it.
Either way - 'git checkout release' would set the repo to the desired 'release'
branch.
Satish
On Mon, 3 Oct 2022, fujisan wrote:
> I probably did:
>
> git clone -b
I probably did:
git clone -b release https://gitlab.com/petsc/petsc.git petsc
like the documentation says. But I found out that I was in branch main.
Cloning 3.17.4 is an abuse of language. I ment cloning petsc when that
release was 3.17.4.
Anyway I git pulled this morning and checked out
Not that I know of, today is the first time I’ve read of it.
It actually happened few hours ago while googling for this issue, and the
results with most things in common with my case were 3 now closed
Issues on the spack repository (never heard of it). Seems something related to
Autoconf up to
You are getting a "-loopopt=0" added to your link line.
No idea what that is or where it comes from.
I don't see it in our repo.
Does this come from your environment somehow?
https://dl.acm.org/doi/abs/10.1145/3493229.3493301
On Mon, Oct 3, 2022 at 9:20 AM Paolo Lampitella
wrote:
> Hi Mark,
>
>
What were the git commands used here [for each of these cases]?
Normally you would checkout a branch - and pull on it. So "cloning 3.17.4"
doesn't really make sense - as there is no "3.17.4" branch.
you ether checkout a tag - v3.17.4 - then you don't get a branch to pull on.
[sure you can do
This is strange. It works for me [with is simple test]
[balay@pj01 ~]$ mpiicc -show
icc -I"/opt/intel/oneapi/mpi/2021.7.0/include"
-L"/opt/intel/oneapi/mpi/2021.7.0/lib/release"
-L"/opt/intel/oneapi/mpi/2021.7.0/lib" -Xlinker --enable-new-dtags -Xlinker
-rpath -Xlinker
That is indeed disappointing. mpicc and mpiicc are simple scripts that
select the compiler based on multiple criteria include the environmental
variables so it is curious that this functionality does not work.
Barry
> On Oct 3, 2022, at 9:58 AM, Paolo Lampitella
> wrote:
>
> Hi
Hi Barry,
thanks for the suggestion. I tried this but doesn’t seem to work as expected.
That is, configure actually works, but it is because it is not seeing the LLVM
based compilers, only the intel classical ones. Yet the variables seem
correctly exported.
Paolo
Da: Barry
bsmith@petsc-01:~$ mpicc
This script invokes an appropriate specialized C MPI compiler driver.
The following ways (priority order) can be used for changing default
compiler name (gcc):
1. Command line option: -cc=
2. Environment variable: I_MPI_CC (current value '')
3. Environment
Hi Paolo,
You can use things like this in your configure file to set compilers and
options.
And you want to send us your configure.log file if it fails.
Mark
'--with-cc=gcc-11',
'--with-cxx=g++-11',
'--with-fc=gfortran-11',
'CFLAGS=-g',
'CXXFLAGS=-g',
'COPTFLAGS=-O0',
'main' is the development version, 'release' is the latest release version.
You can select the branch when cloning or later with git checkout.
See https://petsc.org/release/install/download/#recommended-download
Jose
> El 3 oct 2022, a las 11:08, fujisan escribió:
>
> Hi everyone,
> What are
Dear PETSc users and developers,
as per the title, I recently installed the base and HPC Intel OneApi toolkits
on a machine running Ubuntu 20.04.
As you probably know, OneApi comes with the classical compilers (icc, icpc,
ifort) and relative mpi wrappers (mpiicc, mpiicpc, mpiifort) as well as
Hi everyone,
What are the differences between the 'main' and 'release' branches?
Where I git cloned version 3.17.4, I was by default in the 'main' branch.
Where I git cloned version 3.18.0 (I haven't git pulled from 3.17.4 yet), I
was by default in the 'release' branch.
Fuji
13 matches
Mail list logo
