-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FVCOM 4.4.7 with PETSc 3.18.5 build syntax errors (f951: Error: Unexpected end of file in ‘mod_petsc.f90’) on Rocky Linux 9 #26
Comments
It turns out Fortran has a line length limit. Everything above that limit will be ignored.
The lines were no longer being truncated and that solved the issue. Hope it helps. |
Hey! Thanks I totally got tunnel vision on the error message here. I'll give the flag a try and report back. |
New error:
A quick google search seems to suggest that this line was written with the intent of a Intel Fortran compiler-only feature: https://stackoverflow.com/questions/10509734/gfortran-error-unexpected-element-in-format-string |
Oh I had to solve that problem with "unexpected element '<' just yesterday ... Try modifying: You might (like me) get a new error at the end of the compilation about libjulian not supporting PIE when the makefile tries to make the fvcom executable. To solve this you need to remake libjulian using the cflag -no-pie (add it in JOPTS). I got it to compile like that ... Although now the executable fails because it cannot find libifports... That's tomorrows battle :) |
Thanks for the update! I'll see if I can get further in the build with this info. |
After adding -fallow-argument-mismatch to address some rank mismatching, and modifying '==' signs in with .eq. and .eqv. (depending on the line) in ocpcre.F, and adding hypre + fblaslapack to PETSC, I got libfvcom.a to build! I need to test still but I'll update you. |
Hi Danesnick, Marcos, USE petscmat However the arguments have changed or the compiler checks are more stringent... before i try to figure out how to update the code I was wondering if you had to do anything similar. I don't see any changes in mot_petsc.F from version 4.4.7 to v5.0 or 4.3 which is the one I am using. Example of the errors I get: |
Did you change your make.inc file to use the newer version of petsc?
|
I did change the include path but not the Flag... I can see now that the mod_petsc was changed in version 5.1. I had only downloaded up to 5.0 and didn't see those changes in my local repository. Thank you for the quick response! |
After including the equivalent semi_implicit PETSC_C for the wave_current_interaction the last error I got was in the linker, .....-Wl,-rpath,/work/rito/apps/petsc/intelmpi/3.18.5/lib -lpetsc -lmkl_intel_lp64 -lmkl_core -lmkl_sequential -lpthread -lX11 -lstdc++ -ldl -lifport -lifcoremt -limf -lsvml -lm -lipgo -lirc -lpthread -lgcc_s -lirc_s -lstdc++ -ldl -o fvcom |
Hi Ricardo,
Did you compile PETSC including hypre? This error seems to be pointing more
to hypre than to petsc imho.
Best,
Marcos
Best
tor. 19. sep. 2024, 14:50 skrev Ricardo Torres ***@***.***>:
… After including the equivalent semi_implicit PETSC_C for the
wave_current_interaction the last error I got was in the linker,
.....-Wl,-rpath,/work/rito/apps/petsc/intelmpi/3.18.5/lib -lpetsc
-lmkl_intel_lp64 -lmkl_core -lmkl_sequential -lpthread -lX11 -lstdc++ -ldl
-lifport -lifcoremt -limf -lsvml -lm -lipgo -lirc -lpthread -lgcc_s -lirc_s
-lstdc++ -ldl -o fvcom
ld: mod_petsc.o: in function mod_petsc_mp_petsc_set_':
mod_petsc.f90:(.text+0x44b1): undefined reference to pchypresettype_'
pchypresettype is included in petscpc mod which is correctly invoked at
the begining of mod_petsc.F
When I comment the culprit line
CALL PCHYPRESetType(Pc,"boomeramg",IERR);CHKERRQ(IERR)
the compilation proceeds to completion.
That same line is commented in the wave_current section (with a couple
more lines) but not in the NH or semi-implicit sections.
I haven't tried to use the binary yet. If anyone can shed any light on
this I would be greatful!
Regards
Ricardo
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4T34GKSZUZQFRDLPZDXY3ZXLCCLAVCNFSM6AAAAABMQPU2RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHEYDCOBYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
that could very well be the case. I didn't add any options to the configuration and installation of PETSC. Will re-install with the option.
Thank you!
Ricardo
________________________________
From: Marcos Antonio Carvajalino Fernández ***@***.***>
Sent: Thursday, September 19, 2024 14:12
To: FVCOM-GitHub/FVCOM ***@***.***>
Cc: Ricardo Torres ***@***.***>; Comment ***@***.***>
Subject: Re: [FVCOM-GitHub/FVCOM] FVCOM 4.4.7 with PETSc 3.18.5 build syntax errors (f951: Error: Unexpected end of file in ‘mod_petsc.f90’) on Rocky Linux 9 (Issue #26)
Caution:This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your IT Department
Hi Ricardo,
Did you compile PETSC including hypre? This error seems to be pointing more
to hypre than to petsc imho.
Best,
Marcos
Best
tor. 19. sep. 2024, 14:50 skrev Ricardo Torres ***@***.***>:
After including the equivalent semi_implicit PETSC_C for the
wave_current_interaction the last error I got was in the linker,
.....-Wl,-rpath,/work/rito/apps/petsc/intelmpi/3.18.5/lib -lpetsc
-lmkl_intel_lp64 -lmkl_core -lmkl_sequential -lpthread -lX11 -lstdc++ -ldl
-lifport -lifcoremt -limf -lsvml -lm -lipgo -lirc -lpthread -lgcc_s -lirc_s
-lstdc++ -ldl -o fvcom
ld: mod_petsc.o: in function mod_petsc_mp_petsc_set_':
mod_petsc.f90:(.text+0x44b1): undefined reference to pchypresettype_'
pchypresettype is included in petscpc mod which is correctly invoked at
the begining of mod_petsc.F
When I comment the culprit line
CALL PCHYPRESetType(Pc,"boomeramg",IERR);CHKERRQ(IERR)
the compilation proceeds to completion.
That same line is commented in the wave_current section (with a couple
more lines) but not in the NH or semi-implicit sections.
I haven't tried to use the binary yet. If anyone can shed any light on
this I would be greatful!
Regards
Ricardo
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4T34GKSZUZQFRDLPZDXY3ZXLCCLAVCNFSM6AAAAABMQPU2RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHEYDCOBYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#26 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGHWP4CF2MZEYTEF6JK5FTZXLEVHAVCNFSM6AAAAABMQPU2RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHE2TCMZYHE>.
You are receiving this because you commented.Message ID: ***@***.***>
Visit our website www.pml.ac.uk | Subscribe to our newsletter <https://www.pml.ac.uk/newsletter> | Follow us on social media: LinkedIn<https://www.linkedin.com/company/plymouth-marine-laboratory-&-pml-applications-ltd>, X / Twitter<https://twitter.com/PlymouthMarine>, Instagram<https://www.instagram.com/plymouthmarinelab>, Facebook<https://www.facebook.com/PlymouthMarineLaboratory>, YouTube<https://www.youtube.com/channel/UCfsYrcvGOp-JJm5owSJN8OA>
This message is private and confidential. If you have received this message in error, please notify the sender and remove it from your system. You are reminded that e-mail communications are not secure and may contain viruses; PML accepts no liability for any loss or damage which may be caused by viruses. Our Privacy Notice is available at http://www.pml.ac.uk/System-pages/Privacy_Notice .
Plymouth Marine Laboratory (PML) is a company limited by guarantee registered in England & Wales, company number 4178503. Registered Charity No. 1091222. Registered Office: Prospect Place, The Hoe, Plymouth PL1 3DH, UK. PML Applications Ltd, www.pml-applications.co.uk , is the wholly owned subsidiary of PML, registered as a company in England & Wales, company number 4232750.
|
Just as an FYI @riquitorres , here's what I used to build PETSC 3.18 (GCC+MPICH)
|
Hi, im having this error when compiling Julian: mpif90 -O3 -no-pie -o tconvert tconvert.for libjulian.a Did you know what's happening? thanks |
Hi, This looks like a julian problem to me. Did you compile julian? You have julian (and other libraries inside /src/libs). After that:
|
Hi liesvy
It seems to me your compilation is not finding some functions (te dice "sin
definir"). Are you compiling using the makefile in the Julian folder? That
works ok for me
Best
Marcos
søn. 22. sep. 2024, 05:10 skrev Liesvy Valladares ***@***.***
…:
-no-pie
Hi, im having this error when compiling Julian:
mpif90 -O3 -no-pie -o tconvert tconvert.for libjulian.a
/usr/bin/ld: /tmp/cc1aLpZm.o: en la función MAIN__':
tconvert.for:(.text+0x208): referencia a fjul_parsedt_' sin definir
/usr/bin/ld: tconvert.for:(.text+0x294): referencia a fjul_formatpds_'
sin definir /usr/bin/ld: tconvert.for:(.text+0x33e): referencia a fjul_formatsql_'
sin definir
/usr/bin/ld: tconvert.for:(.text+0x425): referencia a fjul_taiofdutc_'
sin definir /usr/bin/ld: tconvert.for:(.text+0x443): referencia a fjul_etoftai_'
sin definir
/usr/bin/ld: tconvert.for:(.text+0x694): referencia a fjul_jdoftai_' sin
definir /usr/bin/ld: tconvert.for:(.text+0x710): referencia a fjul_jdoftai_'
sin definir
/usr/bin/ld: tconvert.for:(.text+0x788): referencia a fjul_jdoftai_' sin
definir /usr/bin/ld: tconvert.for:(.text+0x804): referencia a fjul_mjdoftai_'
sin definir
/usr/bin/ld: tconvert.for:(.text+0x880): referencia a fjul_mjdoftai_' sin
definir /usr/bin/ld: tconvert.for:(.text+0x8f8): referencia a fjul_mjdoftai_'
sin definir
Did you know what's happening? thanks
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4T34EEGRSM24NCSBTM4P3ZXYYI3AVCNFSM6AAAAABMQPU2RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGQZTMOJTGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thanks, it seems that something I had changed in the code inside the libs. I copied it again, changed the line in fproj to: _cd fproj && ./configure
I have been looking inside mod_petsc.F, and in the call to How can I compile pets with double precision? or do I need to load them from mod_pestc? Thanks |
seems like I need to add --with-precision=double when compiling petsc |
Short update on Semi-implicit + waves |
Hi Ricardo i am compiling fvcom with non_hydrostatic: can you share what do you used in this lines of code for the Wave_current_interaction?
I have tried with
And if I Use
Then when running the model I got this errors:
I am using: petsc-3.21.5, FVCOM4.4.7, with |
Hi Liesvy, |
Thanks, same here, I modified mod_petsc.F and mod_non_hydro.F, I am using petsc-2.3.3-p16 because other versions doesn't compile. Now I am compiling without error, but got some errors when running, I put off the data_assimilation flag cause it gives me more errors in compilation. When running with NH flag gives me this
I have run this same input files without NH flag, when I try to compile with wet_dry gives more errors in mod_petsc.F. I have modified the depth_check.F to eliminate this error. Now I got this I have uploaded the files with modifications too. Thanks |
Hi,
I'm attempting to build FVCOM 4.4.7 on our local HPC cluster using GCC 11.3 and MPICH 4.2 running Rocky Linux 9, I had to make some config changes to get the libraries built, and then run into a final snag at the end of the build process.
First, here's the build environment:
Here are the relevant bits of my $TOPDIR/make.inc file:
Then, I had to make a small modification with
$TOPDIR/src/libs/makefile
to getfproj
to build by adding the-Df2cFortran
in myCFLAGS
:Now when I go back to
$TOPDIR/src
to build the main program, most stuff completes until I hit the end:The text was updated successfully, but these errors were encountered: