GNU bug report logs -
#30006
bzip2 does not provide libbz2.so
Previous Next
Reported by: ludo <at> gnu.org (Ludovic Courtès)
Date: Sat, 6 Jan 2018 13:30:02 UTC
Severity: normal
Done: Marius Bakke <mbakke <at> fastmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Tobias Geerinckx-Rice <me <at> tobias.gr> writes:
> Marius,
>
> On 2018-03-23 13:02, Marius Bakke wrote:
>> diff --git a/gnu/packages/compression.scm
>> b/gnu/packages/compression.scm
>> index b158feac4..fd111e579 100644
>> --- a/gnu/packages/compression.scm
>> +++ b/gnu/packages/compression.scm
>> @@ -272,6 +272,9 @@ file; as a result, it is often used in conjunction
>> with \"tar\", resulting in
>> (lambda* (#:key outputs #:allow-other-keys)
>> (let* ((out (assoc-ref outputs "out"))
>> (libdir (string-append out "/lib")))
>> + ;; The Make target above does not create "libbz2.so",
>> only
>> + ;; the versioned libs, so we have to create it
>> ourselves.
>> + (symlink "libbz2.so.1.0" "libbz2.so")
>
> How about symlinking to (string-append ... version) directly?
> Seems more robust & worked fine when I tried it, I think.™
That makes sense. I just wanted to stay close to the typical Autotools
way of creating these links, where libfoo.so points to libfoo.so.1 which
points to libfoo.so.1.2. I'll change to (version-major+minor ...)
instead, in the off chance that bzip2 ever gets a new version.
Side note: "copy-file" (and thus "install-file") actually dereferences
symlinks, so in the end you get three copies of the same library. Is
there an alternative to "copy-file" that preserves soft links? Not that
it matters in practice due to deduplication, but still...
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 7 years and 116 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.