From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Tim Lee <progscriptclone@gmail.com>, help-guix@gnu.org
Subject: Re: Why doesn't Guix build static libraries?
Date: Sun, 31 Oct 2021 16:03:09 +0100 [thread overview]
Message-ID: <20211031160309.5b648139@primarylaptop.localdomain> (raw)
In-Reply-To: <87fssh2ybn.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
On Sun, 31 Oct 2021 12:48:19 +0100
Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> My worry is that leaving .a files around will cause some build
> systems to silently prefer them to the .so and link statically. I
> can't remember the name of the packages, but this does happen.
Could it also do that when the static libraries are split in their
own package/derivation like openssl:static for instance?
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-31 15:04 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 [this message]
2021-10-31 16:13 ` Tobias Geerinckx-Rice
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=20211031160309.5b648139@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
--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).