public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Salvatore Filippone <filippone.salvatore@gmail.com>
To: Andrew Benson <abenson@carnegiescience.edu>
Cc: Fortran List <fortran@gcc.gnu.org>
Subject: Re: Error message
Date: Mon, 17 Oct 2022 18:05:44 +0200	[thread overview]
Message-ID: <CANSzZf59++Go51_4iqbYRCBx6Tcfu-mRKsTDjsNNE594xGXJPA@mail.gmail.com> (raw)
In-Reply-To: <5058880.PNISsnXf8o@abensonca-precision-7540>

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

It was indeed a case of misalignment of compiled files (in my case, make
install going to one location, and the code to be compiled picking up from
a different one)

Thanks to all,
Salvatore

On Mon, Oct 17, 2022 at 4:42 PM Andrew Benson <abenson@carnegiescience.edu>
wrote:

> Hi Salvatore,
>
> I've run into similar error messages occasionally. I've never been able to
> fully track down the cause, but it seems to happen if I change the content
> of
> a derived type (e.g. add some new variable to it), recompile the module
> containing it, but don't recompile some other module that USEs that first
> module. It seems like there are then multiple definitions of the derived
> type
> (from different modules) that are out of sync. So, recompiling everything
> resolves this issue for me.
>
> But, as I said, I'm not 100% sure that this is the explanation!
>
> -Andrew
>
> On Monday, October 17, 2022 2:28:33 AM PDT Salvatore Filippone via Fortran
> wrote:
> > Dear all
> > I am getting the following error message, which I find quite confusing
> >
> >    68 |   use amg_prec_mod
> >
> >       |       1
> >
> > Fatal Error: Mismatch in components of derived type
> > '__vtype_psb_c_par_mat_mod_Psb_c_par_mat_type' from 'psb_c_par_mat_mod'
> at
> > (1): expecting 'bldext', but got 'aclsum'
> > compilation terminated.
> >
> > from
> >  mpifort -v
> > mpifort for MPICH version 3.4.3
> > Using built-in specs.
> > COLLECT_GCC=/opt/gnu/12.1.0/bin/gfortran
> >
> COLLECT_LTO_WRAPPER=/opt/gnu/12.1.0/libexec/gcc/x86_64-pc-linux-gnu/12.1.0/l
> > to-wrapper Target: x86_64-pc-linux-gnu
> > Configured with: ../gcc-12.1.0/configure --prefix=/opt/gnu/12.1.0
> > --enable-languages=c,c++,fortran
> > Thread model: posix
> > Supported LTO compression algorithms: zlib
> > gcc version 12.1.0 (GCC)
> >
> >
> > What might  the compiler be  complaining about? Where can I find
> additional
> > info on what to do?
> > Any help greatly appreciated
> >
> > Salvatore
>
>
> --
>
> * Andrew Benson: https://abensonca.github.io
>
> * Galacticus: https://github.com/galacticusorg/galacticus
>
>
>
>

  reply	other threads:[~2022-10-17 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  9:28 Salvatore Filippone
2022-10-17 14:42 ` Andrew Benson
2022-10-17 16:05   ` Salvatore Filippone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-05 17:16 error message paul starr
2008-04-04 15:11 Error message Salvatore Filippone
2008-04-04 15:37 ` Tobias Burnus
2008-04-04 15:45   ` Salvatore Filippone

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=CANSzZf59++Go51_4iqbYRCBx6Tcfu-mRKsTDjsNNE594xGXJPA@mail.gmail.com \
    --to=filippone.salvatore@gmail.com \
    --cc=abenson@carnegiescience.edu \
    --cc=fortran@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).