From: ng0 <ng0@we.make.ritual.n0.is>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: help with setenv of perl-curses
Date: Sat, 06 Aug 2016 13:28:39 +0000 [thread overview]
Message-ID: <878twagh6g.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAEwRq=r9nNb6onTKLG2Jpp81aRHwmG0XcZ8OZsht8=-sbRizXQ@mail.gmail.com>
Hi,
Vincent Legoll <vincent.legoll@gmail.com> writes:
> Hello,
>
>> + (build-system perl-build-system)
>> + (inputs `(("ncurses" ,ncurses)))
>> + (arguments
>> + `(#:phases
>> + (modify-phases %standard-phases
>> + (add-before
>> + 'configure 'set-curses-ldflags
>> + (lambda* (#:key inputs #:allow-other-keys)
>> + (setenv "CURSES_LIBTYPE" "ncurses")
>> + (setenv "CURSES_CFLAGS"
>> + (string-append "-I" (assoc-ref inputs "ncurses")
>> + "/include"))
>> + (setenv "CURSES_LDFLAGS"
>> + (string-append "-L" (assoc-ref inputs "ncurses")
>
> Is this specific to perl-ncurses or would other ncurses-using packages also need
> these definitions ?
I don't know, read the README and/or INSTALL file of this package on
cpan.
> --
> Vincent Legoll
--
♥Ⓐ ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org
prev parent reply other threads:[~2016-08-06 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 1:23 help with setenv of perl-curses ng0
2016-06-15 9:19 ` Ricardo Wurmus
2016-07-23 13:18 ` ng0
2016-07-23 13:58 ` ng0
2016-07-24 5:25 ` Efraim Flashner
2016-08-06 13:31 ` ng0
2016-08-19 13:23 ` [PATCH] gnu: Add perl-curses (need help) ng0
2016-08-19 13:36 ` [PATCH][v2] gnu: Add perl-curses ng0
2016-09-06 17:36 ` Efraim Flashner
2016-09-06 21:39 ` ng0
2016-09-07 6:09 ` Efraim Flashner
2016-07-25 8:18 ` help with setenv of perl-curses Vincent Legoll
2016-08-06 13:28 ` ng0 [this message]
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=878twagh6g.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=vincent.legoll@gmail.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.