openssl lacks lib/libssl.a

  • Done
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Marius Bakke
  • ng0
Owner
unassigned
Submitted by
ng0
Severity
normal
N
(address . bug-guix@gnu.org)
8737hy85fq.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me
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.
M
M
Marius Bakke wrote on 9 Dec 2016 09:40
87lgvpxzpm.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me
ng0 <ng0@libertad.pw> writes:

Toggle quote (4 lines)
> 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?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlhKbfUACgkQoqBt8qM6
VPqK3Qf9EDn6WE5cEPVEymUtbZyg6gkWk/Q0rt/PEdSa1HZk4FGh3ZIaajKbEa2j
RDRt4tE9nfH4qr/hfusEQA9TYK1K5qNLeks4GpRf7tn/Gru0pe9yiNHhRryKC7ts
xkRpgcM2XOczmiyA5rtw/BVKs3HJZdGfpFFTL0+iJSF6LiegHKJS8VGH/014OjoU
TPIwX62WeP+zhjWU+6BVapa/B5L+WamGUvbADSydoMl7fdUzxq/BwxQUkkBxlonk
3hCWnBOe74tAwumT/FT9vVTstPvhAt8a7WPeAl8OFKkJgjVdCt8UCRf3W0mRPTFx
G0bjR9FZt3E369oK2hnsGnavGHirYQ==
=tpSx
-----END PGP SIGNATURE-----

N
(name . Marius Bakke)(address . mbakke@fastmail.com)(address . 25142@debbugs.gnu.org)
87eg1hwg8u.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (8 lines)
> 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?
--
♥? ng0 | ng0.chaosnet.org
M
M
Marius Bakke wrote on 9 Dec 2016 11:40
(name . ng0)(address . ng0@libertad.pw)(address . 25142@debbugs.gnu.org)
87d1h1xu4s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me
ng0 <ng0@libertad.pw> writes:

Toggle quote (13 lines)
> 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! :-)
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlhKijMACgkQoqBt8qM6
VPpoZQgAhwZnmGl4xpWSmJ4gU6P7pi4EKChcfhGEpAoDxiIGCafTFNjK65AMyIlu
wAPLucfoTprwQ+cXOlUlMlTD9NjOBMepSth4QSou0BZRscOJITH4bvZjL5F3EM7t
W3RlvCi0DTicIa6KeeIRQrq2GV1IpGIENuetI+TCHj+RbywIlqG0AK/tEJcev0g0
TL+uotmRa2hglNo1Vhb7uBfWxBne24H4Zic4IJJVuunG5ZpkaqPHPh2bizXJhVxz
q47eNSTFQEovaREb9RSxhOKAWYbGTi6BS7M85MQgz9ADXJvH1NYjHzqkEepHgLAE
RBJ+oH2wYQX8/LPCvSs9rjEkh45T9w==
=plMC
-----END PGP SIGNATURE-----

N
(name . Marius Bakke)(address . mbakke@fastmail.com)(address . 25142@debbugs.gnu.org)
87a8c5wf5y.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (23 lines)
> 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.
--
♥? ng0 | ng0.chaosnet.org
L
L
Ludovic Courtès wrote on 9 Dec 2016 15:09
(name . ng0)(address . ng0@libertad.pw)
874m2ddwiz.fsf@gnu.org
ng0 <ng0@libertad.pw> skribis:

Toggle quote (28 lines)
> 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’.
L
L
Ludovic Courtès wrote on 9 Dec 2016 15:09
control message for bug #25142
(address . control@debbugs.gnu.org)
8737hxdwig.fsf@gnu.org
tags 25142 notabug
close 25142
?
Your comment

This issue is archived.

To comment on this conversation send an email to 25142@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 25142
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch