all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: Symlinks to generic names
Date: Sat, 01 Feb 2014 19:32:21 -0500	[thread overview]
Message-ID: <87eh3me4mi.fsf@netris.org> (raw)
In-Reply-To: <87r47mads0.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 01 Feb 2014 22:28:15 +0400")

Nikita Karetnikov <nikita@karetnikov.org> writes:

>> Some software (rightly or wrongly) tries to build with "lex" and "yacc" .  Guix does not provide these.
>> Instead we have "flex" and "bison".  Most operating systems have symbolic links lex -> flex and yacc -> bison.
>> Shouldn't we provide these too?
>
> I guess this should solve the problem (untested):
>
> (inputs
>   `(("lex" ,flex)
>     ("yacc" ,bison)
>     ...))

No, this wouldn't work.  Those strings ("lex" and "yacc" above) do not
become commands on the filesystem, so they won't be visible to a build
system that's looking for lex or yacc.  They are merely used within the
derivation to refer to the inputs.

Implementing John's suggestion would involve installing symbolic links
in /nix/store/*-flex-* and /nix/store/*-bison-* in the flex and bison
recipes, which I guess means adding a new phase to those recipes.

      Mark

  reply	other threads:[~2014-02-02  0:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01  8:21 Symlinks to generic names John Darrington
2014-02-01 18:28 ` Nikita Karetnikov
2014-02-02  0:32   ` Mark H Weaver [this message]
2014-02-02  7:34 ` Ludovic Courtès
2014-02-02  7:46   ` John Darrington
2014-02-02 18:06     ` Ludovic Courtès
2014-02-02 13:40   ` John Darrington
2014-02-02 16:42     ` Andreas Enge
2014-02-02 17:47       ` John Darrington
2014-02-03 13:46         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eh3me4mi.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=nikita@karetnikov.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 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.