unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: Tim Lee <progscriptclone@gmail.com>, help-guix@gnu.org
Subject: Re: Why doesn't Guix build static libraries?
Date: Sun, 31 Oct 2021 17:13:09 +0100	[thread overview]
Message-ID: <877ddt2mvl.fsf@nckx> (raw)
In-Reply-To: <20211031160309.5b648139@primarylaptop.localdomain>

[-- Attachment #1: Type: text/plain, Size: 203 bytes --]

Denis 'GNUtoo' Carikli 写道:
> Could it also do that when the static libraries are split in 
> their
> own package/derivation like openssl:static for instance?

Nope.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2021-10-31 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31  4:49 Why doesn't Guix build static libraries? Tim Lee
2021-10-31 11:48 ` Tobias Geerinckx-Rice
2021-10-31 15:03   ` Denis 'GNUtoo' Carikli
2021-10-31 16:13     ` Tobias Geerinckx-Rice [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

  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=877ddt2mvl.fsf@nckx \
    --to=me@tobias.gr \
    --cc=GNUtoo@cyberdimension.org \
    --cc=help-guix@gnu.org \
    --cc=progscriptclone@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.
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).