From: Dave Love <dave.love@manchester.ac.uk>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: fortran@gcc.gnu.org
Subject: Re: backwards incompatibility
Date: Fri, 16 Mar 2018 13:48:00 -0000 [thread overview]
Message-ID: <87vadwyvv7.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <f4b02d10-0fa7-7fe1-0b13-3d0b0f14b036@charter.net> (Jerry DeLisle's message of "Tue, 13 Mar 2018 19:30:27 -0700")
Jerry DeLisle <jvdelisle@charter.net> writes:
> It would be an order of magnitude easier and take less time if you
> just recompiled all of your sources. I hope you use make or cmake or
> at least some build scripting and let it run overnight. Or, does it
> take a week or two?
>
> Regards,
>
> Jerry
[I saw this late on gmane as I'm not subscribed to the list.]
This isn't necessarily about "my" sources (stuff on local systems). I
go with the engineering trades-off in packaging and late binding (in
this context) rather than combinatorial rebuild-the-world and distribute
packaging.
I'm specifically interested in RHEL (EPEL) packages, and concerned by
the lack of information on ABI compatibility of, say, gfortran 4.8 (the
system version) and gfortran 6 (the latest with the same libgfortan,
distributed for RHEL-like systems and necessary for several things like
proper MPI support and avx512). Can someone say if 6 is (in)compatible
with 4.8 apart from the module format, assuming the same language
features?
prev parent reply other threads:[~2018-03-16 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 15:40 Dave Love
2018-03-12 17:05 ` Steve Kargl
2018-03-12 20:42 ` Dave Love
2018-03-12 21:18 ` Thomas Koenig
2018-03-13 15:14 ` Dave Love
2018-03-14 2:31 ` Jerry DeLisle
2018-03-16 13:48 ` Dave Love [this message]
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=87vadwyvv7.fsf@albion.it.manchester.ac.uk \
--to=dave.love@manchester.ac.uk \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).