From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@libertad.pw>
Cc: 25142@debbugs.gnu.org
Subject: bug#25142: openssl lacks lib/libssl.a
Date: Fri, 09 Dec 2016 15:09:24 +0100 [thread overview]
Message-ID: <874m2ddwiz.fsf@gnu.org> (raw)
In-Reply-To: <87a8c5wf5y.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0@libertad.pw's message of "Fri, 09 Dec 2016 10:49:29 +0000")
ng0 <ng0@libertad.pw> skribis:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> ng0 <ng0@libertad.pw> writes:
>>
>>> Marius Bakke <mbakke@fastmail.com> writes:
>>>
>>>> ng0 <ng0@libertad.pw> writes:
>>>>
>>>>> In commit 0c69a17efdba0c7c3da0f25800a3c3233200e47b I found out
>>>>> that our openssl lacks lib/libssl.a ... this should be fixed
>>>>> somehow with the next update of the openssl package.
>>>>
>>>> Did you try the "static" output of OpenSSL?
>>>
>>> No, I did not know it existed. If this would be in out:static,
>>> why is this file in libressl normal output?
>>
>> I think the main reason static libraries are often in separate outputs
>> is because of bandwidth concerns, since they are often much larger than
>> their dynamic counterparts (.so). And the closure size can be smaller,
>> since they don't contain external references.
>>
>> LibreSSL probably haven't seen enough use for it to be a concern. Feel
>> free to submit a patch! :-)
>
> Oh, so this is a bug and not intentional. Okay, I'll submit a
> patch this month.
The OpenSSL “static” output was added in 8c78aeb7 to save ~6 MiB, which
were unused by the in-tree packages.
Ludo’.
prev parent reply other threads:[~2016-12-09 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 21:41 bug#25142: openssl lacks lib/libssl.a ng0
2016-12-09 8:40 ` Marius Bakke
2016-12-09 10:26 ` ng0
2016-12-09 10:40 ` Marius Bakke
2016-12-09 10:49 ` ng0
2016-12-09 14:09 ` Ludovic Courtès [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=874m2ddwiz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25142@debbugs.gnu.org \
--cc=ng0@libertad.pw \
/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).