unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 21214@debbugs.gnu.org
Subject: bug#21214: symlinks cc -> gcc, lex -> flex etcetc
Date: Wed, 19 Aug 2015 15:29:54 +0200	[thread overview]
Message-ID: <20150819152954.32452f9f@dayas> (raw)
In-Reply-To: <87egj0ieuo.fsf@gnu.org>

Hello,

On Tue, 18 Aug 2015 21:19:43 +0200
ludo@gnu.org (Ludovic Courtès) wrote:

> Danny Milosavljevic <dannym@scratchpost.org> skribis:
> In practice most software build systems will look for both ‘cc’ and
> ‘gcc’.  For those who don’t, it’s usually easy to specify an alternate
> compiler name, for instance via ‘make’ flags (there are several
> examples of that in the packages.)

Yes it is. 

I'm just slowly documenting all the problems I encountered while
trying GuixSD on a X200. 

This was one of the first: I checked out
cbfstool from coreboot in order to swap Fn and Ctrl and tried to make
it, but it didn't find "cc" and then got stuck in an endless loop
(which is a problem in coreboot, also reported there as
http://comments.gmane.org/gmane.linux.bios/81588 ).

> If that’s fine with you, I’ll close this bug.

That's okay. If it already was discussed that's fine. 

With kind regards,
   Danny

  reply	other threads:[~2015-08-19 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 21:52 bug#21214: symlinks cc -> gcc, lex -> flex etcetc Danny Milosavljevic
2015-08-18 19:19 ` Ludovic Courtès
2015-08-19 13:29   ` Danny Milosavljevic [this message]
2015-08-19 19:13     ` Ludovic Courtès

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=20150819152954.32452f9f@dayas \
    --to=dannym@scratchpost.org \
    --cc=21214@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).