From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Openssl missing in CPATH
Date: Tue, 1 Jan 2013 15:04:53 +0100 [thread overview]
Message-ID: <201301011504.53141.andreas@enge.fr> (raw)
In-Reply-To: <87y5gfyzhj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
Am Sonntag, 30. Dezember 2012 schrieb Ludovic Courtès:
> Could it be that OpenSSL actually lacks a directory called ‘include’?
After installatio, there is .guix-profile/include/openssl/
with lots of header files.
Andreas
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
next prev parent reply other threads:[~2013-01-01 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 23:56 Openssl missing in CPATH Andreas Enge
2012-12-30 21:57 ` Ludovic Courtès
2013-01-01 14:04 ` Andreas Enge [this message]
2013-01-02 15:00 ` Ludovic Courtès
2013-01-13 18:52 ` Andreas Enge
2013-01-13 22:27 ` Ludovic Courtès
2013-01-13 23:04 ` Andreas Enge
2013-01-15 16:12 ` 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=201301011504.53141.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-guix@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).