public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "afernandez at odyhpc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100755] Error with fortran object (v11.1.0)
Date: Tue, 25 May 2021 21:10:52 +0000	[thread overview]
Message-ID: <bug-100755-4-k59q1S9Cqq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100755-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100755

--- Comment #3 from afernandez at odyhpc dot com ---
Sorry for the delay. The system is AArch64 and running CentOS8.3. I have 2 GCC
installations, one is 8.3.1 and the second is 11.1.0. NCEPLIBS builds with the
former but not with the second. 
The 1st step is with cmake
cd /opt/prae
sudo git clone https://github.com/NOAA-EMC/NCEPLIBS
cd /opt/prae/NCEPLIBS
sudo mkdir -p build && cd build 
sudo /usr/local/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/prae/NCEP
-DCMAKE_C_COMPILER=/opt/prae/openmpi/bin/mpicc
-DCMAKE_Fortran_COMPILER=/opt/prae/openmpi/bin/mpif90
-DCMAKE_INSTALL_PREFIX=/opt/prae/NCEP -DCMAKE_PREFIX_PATH=/opt/prae/netcdf
-DNetCDF_INCLUDE_DIRS=/opt/prae/netcdf/include
-DNetCDF_LIBRARIES=/opt/prae/netcdf/lib /opt/prae/NCEPLIBS
Then, it fails when invoking make. I also tried adding the flag
"-fdefault-integer-8" but it didn't change anything. 

If I'm understanding correctly and this is an extension being deprecated, is
there any option to push the compilation with gcc11.1 through? I'm not the
developer so even if they agreed to make the necessary changes, it might take
some time. Thanks.

  parent reply	other threads:[~2021-05-25 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 15:27 [Bug fortran/100755] New: " afernandez at odyhpc dot com
2021-05-25 15:42 ` [Bug fortran/100755] " marxin at gcc dot gnu.org
2021-05-25 18:58 ` [Bug middle-end/100755] " anlauf at gcc dot gnu.org
2021-05-25 21:10 ` afernandez at odyhpc dot com [this message]
2021-05-25 22:04 ` dominiq at lps dot ens.fr
2021-05-26  0:11 ` afernandez at odyhpc dot com
2021-05-26  6:42 ` anlauf at gcc dot gnu.org
2021-05-26 13:43 ` afernandez at odyhpc dot com
2021-06-18 17:52 ` anlauf at gcc dot gnu.org
2022-01-01  9:04 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100755-4-k59q1S9Cqq@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).