Yes, this also seems to work on my end.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 15, 2021, at 12:05, Satish Balay wrote:
>
> Does setting MACOSX_DEPLOYMENT_TARGET also work?
>
> Satish
>
> On Mon, 15 Feb 2021, Jacob Faibussowitsch wrot
Does setting MACOSX_DEPLOYMENT_TARGET also work?
Satish
On Mon, 15 Feb 2021, Jacob Faibussowitsch wrote:
> I think this problem ultimately stems from the fact that gcc/g++ and gfortran
> are not from the same people on macOS. It seems like clang is configured to
> build for 11.0 target, whilst
I think this problem ultimately stems from the fact that gcc/g++ and gfortran
are not from the same people on macOS. It seems like clang is configured to
build for 11.0 target, whilst gcc defaults to newest available target. And
indeed if I change my compile command there is no warning:
mkdir -
Ok so if I pass -mmacosx-version-min=11.2 to the linker the warning
disappears...
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 15, 2021, at 11:41, Jacob Faibussowitsch wrote:
>
> I can reproduce the warning compiling just that simple code y
ok - gfortran is using:
> COLLECT_GCC_OPTIONS='-o'
> '/var/folders/9w/7dlszmmn6q1gd5yf3r9n79bcgn/T/petsc-dk9aiv7x/config.compilers/conftest'
> '-v' '-Wall' '-ffree-line-length-0' '-Wno-unused-dummy-argument' '-g'
> '-mmacosx-version-min=11.2.0' '-asm_macosx_version_min=11.2' '-shared-libgcc
I can reproduce the warning compiling just that simple code you listed. This is
the compile command:
mkdir -p build && gfortran -c -o ./build/conftest.o conftest.F90 && gcc -o
./build/libconftest.dylib ./build/conftest.o -dynamiclib -undefined
dynamic_lookup && rm -rf ./build
And error:
ld: wa
Here is the compile command and the warning:
>>
= Checking linker
Executing: gfortran -c -o
/var/folders/9w/7dlszmmn6q1gd5yf3r9n79bcgn/T/petsc-dk9aiv7x/config.setCompilers/conftest.o
-I/var/folders/9w/7dlszmmn6q1gd5yf3r9n79bcgn/T/petsc-dk9aiv7x/config.setCompilers
/var/folde
Pierre Jolivet writes:
> I’m playing the Devil’s advocate since the beginning, we’ve had a
> --enable-generic (off by default) which turns -march=native into
> -march=generic for 20+ years (I’m seeing references to PPC7450 and Intel
> Coppermine in our configure…).
> We turn this flag on when
> On 15 Feb 2021, at 1:41 AM, Barry Smith wrote:
>
>
>
>> On Feb 14, 2021, at 4:04 PM, Jed Brown wrote:
>>
>> Barry Smith writes:
>>
>>> My feeling is 90+% of users don't care about portability, they want to get
>>> fast performance on the machine they are compiling with (or a collecti
