Re: symbols-File for Library
On Fri, Aug 12, 2022 at 12:43:23AM -0300, Eriberto Mota wrote:
> I suggest uploading new upstream releases to experimental to know the
> behavior in each architecture. For MISSING lines, an easy fix is to
> exclude the fault architectures. E.g. to exclude i386 and x32:
>
> (arch=!i386 !x32)(c++)"gensios::gensio_cpp_vlog_handler(gensios::gensio_os_funcs*,
> gensios::gensio_log_levels, char const*, __va_list_tag*)@Base"
But isn't that as bad as maintaining a package.symbols.$ARCH for every
arch?
And what's the benefit in having a symbols file? People on IRC tell me
that's only important for big libs with a huge number of reverse
dependencies.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Reply to: