From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: collect2: fatal error: cannot find 'ld'
Date: Mon, 11 Mar 2019 16:53:30 +0100 [thread overview]
Message-ID: <87d0mxv24l.fsf@gnu.org> (raw)
In-Reply-To: <87tvh8ir2d.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 12 Feb 2019 23:23:54 +0100")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> I still think that we should hide the plain gcc packages on the command
>>> line.
>>
>> Agreed.
>
> Is this the right way to hide the package (see patch)? I searched for
> GCC on the command line with “guix package --search=gcc” and the results
> did not include the plain gcc packages.
It still includes the ‘gcc-toolchain’ packages, right?
> From 8cbb0b446930264b7f2a771cc95534e14dde9edd Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Tue, 12 Feb 2019 23:21:48 +0100
> Subject: [PATCH] gnu: gcc-4.7: Hide package.
>
> * gnu/packages/gcc.scm (gcc-4.7): Wrap in "hidden-package" expression.
Alternately you could simply add a ‘properties’ field (with a comment),
which would make the diff smaller.
Go for it!
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-03-11 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 12:38 collect2: fatal error: cannot find 'ld' znavko
2019-02-09 14:35 ` Ricardo Wurmus
2019-02-09 15:50 ` vikram sai balaji ulaganathan
2019-02-10 10:28 ` znavko
[not found] ` <<87wom9kp1q.fsf@elephly.net>
[not found] ` <LYLwvzs--3-1@tutanota.com-LYLwzou----1>
2019-02-10 10:45 ` znavko
2019-02-11 11:40 ` zimoun
2019-02-11 12:01 ` Ricardo Wurmus
2019-02-11 12:07 ` zimoun
2019-02-12 16:44 ` Ludovic Courtès
2019-02-12 22:23 ` Ricardo Wurmus
2019-02-22 15:51 ` zimoun
2019-02-22 15:55 ` Ricardo Wurmus
2019-03-11 15:53 ` Ludovic Courtès [this message]
2019-05-09 21:20 ` Ricardo Wurmus
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=87d0mxv24l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.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).