public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bertini, Denis Dr." <D.Bertini@gsi.de>
To: Harald Anlauf <anlauf@gmx.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Problem setting buffer size for gfortran ( v 11.2)
Date: Wed, 23 Feb 2022 21:23:14 +0000	[thread overview]
Message-ID: <a33603281b9249d688463e441ac0e8e8@gsi.de> (raw)
In-Reply-To: <trinity-9bf94afe-e773-4366-b0b2-ae398de80664-1645651097363@3c-app-gmx-bs49>

Hi Harald,

I ran also the same with gfortran v11.2. together with singularity and

did not work as well.

Then i change the defintion of the buffer size in unix.c to default at 1 MiB

and it works.

What do you mean by vendor?

Do you think the problem could be linked to running fortran within singularity container?

Best

Denis

________________________________
From: Harald Anlauf <anlauf@gmx.de>
Sent: Wednesday, February 23, 2022 10:18:17 PM
To: Bertini, Denis Dr.
Cc: fortran@gcc.gnu.org
Subject: Re: Problem setting buffer size for gfortran ( v 11.2)

Hi Denis,

if I'm reading the strace output correctly, you're running the app
with gfortran-8 (too old) under singularity (virtualization software).

I'm afraid you need to contact your vendor or system folks.

Cheers,
Harald


Gesendet: Mittwoch, 23. Februar 2022 um 21:59 Uhr
Von: "Bertini, Denis Dr." <D.Bertini@gsi.de>
An: "Harald Anlauf" <anlauf@gmx.de>, "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Betreff: Re: Problem setting buffer size for gfortran ( v 11.2)

Hi Harald,



I do not know why the attachment was not sent with my email
I try again
Best
Denis


  parent reply	other threads:[~2022-02-23 21:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 16:10 Bertini, Denis Dr.
2022-02-23 18:26 ` Harald Anlauf
2022-02-23 18:26   ` Harald Anlauf
2022-02-23 20:28   ` Bertini, Denis Dr.
2022-02-23 20:57     ` Harald Anlauf
2022-02-23 20:57       ` Harald Anlauf
2022-02-23 20:59     ` Bertini, Denis Dr.
     [not found]       ` <trinity-9bf94afe-e773-4366-b0b2-ae398de80664-1645651097363@3c-app-gmx-bs49>
2022-02-23 21:23         ` Bertini, Denis Dr. [this message]
2022-02-23 21:38           ` Harald Anlauf
2022-02-24  7:57             ` Bertini, Denis Dr.
2022-02-24  8:13               ` Tobias Burnus
2022-02-24  8:15                 ` Bertini, Denis Dr.
2022-02-24  8:20                   ` Tobias Burnus
2022-02-25 17:28                     ` Bertini, Denis Dr.
     [not found]                       ` <trinity-59001f50-077d-424e-a648-24645944dd0c-1645813711633@3c-app-gmx-bap28>
2022-02-25 20:01                         ` Bertini, Denis Dr.
2022-02-25 20:44                           ` Harald Anlauf
2022-02-25 20:44                             ` Harald Anlauf
2022-02-25 20:53                             ` Bertini, Denis Dr.
2022-02-26  9:20                               ` Thomas Koenig
2022-02-26 15:37                                 ` Bertini, Denis Dr.

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=a33603281b9249d688463e441ac0e8e8@gsi.de \
    --to=d.bertini@gsi.de \
    --cc=anlauf@gmx.de \
    --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).