Hi Carsten-- On Sun 2022-06-12 17:15:08 +0200, Carsten Schoenert wrote: > Am Sat, Mar 26, 2022 at 04:06:46PM -0400 schrieb Daniel Kahn Gillmor: >> I've just uploaded rnp 0.16.0 into debian unstable. According to >> https://bugzilla.mozilla.org/show_bug.cgi?id=1732809 the main >> development line of thunderbird now has a --with-system-rnp flag (but >> the 91esr series doesn't have it. >> >> So when new versions of thunderbird get built in debian (in experimental >> first, maybe?) please try to use --with-system-rnp. If you run into any >> reason why building against the system rnp isn't working, please don't >> hesitate to file bug reports against rnp and we'll sort them out. > > after again months of waiting for some typical build tools and a lot of > try and errors attempts I'm now able to build the current beta version > of Thunderbird (102.0~b4) together with the system package of > librnp-dev.
that's great news! thanks for doing this.
> The downside is that this requires currently the usage of the internal
> version of botan, bz2 and jsonc.
>
> I've no kowledge if upstream has plans to reenable the usage of system
> packages for these tools, maybe it's also just a misconfiguration of the
> buildsystem.
Ugh, that doesn't sound so reasonable. I'd expect those libraries to be
internal to librnp, and not directly exposed to the rest of thunderbird.
so they shouldn't be related to the build process at all, afaict.
Have you reported this upstream at all? do you have examples of the
build failures that happen when you use the system librnp that we could
work through and post where upstream can see them?
--dkg
signature.asc
Description: PGP signature
