From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Marius Bakke <mbakke@fastmail.com>, help-guix@gnu.org
Subject: Re: gfortran seems to require gcc-toolchain
Date: Sat, 16 Nov 2019 09:44:18 +0100 [thread overview]
Message-ID: <m1r228rz19.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <871ru9ghpc.fsf@devup.no>
Hi Marius,
>> 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.
I'd prefer a compiler that works at 291.5 MiB to a compiler that doesn't
work at 238.0 MiB.
When you know how to fix the problem (by installing binutils), it's
perhaps just a convenience. If you don't know, it's a show-stopper.
I see the point of wanting to use a different 'as', but are there any
concrete alternatives in Guix that someone might wish to substitute?
Personally I have never cared much about 'as'. It's a necessary tool
but also a very boring and predictable one. I don't see what I could
gain by replacing it.
Cheers,
Konrad.
next prev parent reply other threads:[~2019-11-16 8:44 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
2019-11-16 8:44 ` Konrad Hinsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1r228rz19.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.