From: Marius Bakke <mbakke@fastmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>, help-guix@gnu.org
Subject: Re: gfortran seems to require gcc-toolchain
Date: Fri, 15 Nov 2019 18:41:51 +0100 [thread overview]
Message-ID: <871ru9ghpc.fsf@devup.no> (raw)
In-Reply-To: <m1h83aqo9t.fsf@khs-macbook.home>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Hi Marius,
>
>> 'as' is part of Binutils, you don't need the entire toolchain.
>>
>> That said, there are various other workarounds in Guix due to GCC
>> (and apparently gfortran) lacking an absolute reference to 'as'.
>>
>> Can you try the following patch and see if it works for your case?
>
> Thanks for looking into this!
>
> With your patch, I can compile Fortran programs in an environment
> containing nothing but "gfortran", so I'd say it works!
On second though, the patch increases the size of 'gcc' from 238.0 MiB
to 291.5 MiB. It may also make it difficult to use a different 'as'
executable.
So I'm not sure whether the added convenience is worth it.
Thoughts?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-15 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 16:09 gfortran seems to require gcc-toolchain Konrad Hinsen
2019-11-09 23:03 ` Marius Bakke
2019-11-10 7:14 ` Efraim Flashner
2019-11-10 19:50 ` Marius Bakke
2019-11-11 18:08 ` Konrad Hinsen
2019-11-15 17:41 ` Marius Bakke [this message]
2019-11-16 8:44 ` Konrad Hinsen
2019-11-18 10:40 ` zimoun
2019-11-18 12:09 ` Konrad Hinsen
2019-11-19 21:26 ` Marius Bakke
2019-11-19 21:28 ` brettg
2019-11-20 4:37 ` John Soo
2019-11-20 5:48 ` ML on Guix (Was: Re: gfortran seems to require gcc-toolchain) brettg
2019-11-30 14:52 ` gfortran seems to require gcc-toolchain Konrad Hinsen
2019-11-18 10:43 ` Konrad Hinsen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871ru9ghpc.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.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).