Re: symbols-File for Library
Hi Eriberto,
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"
Just in case I want to use this opportunity to get a feeling for symbols
files, can I also specify architectures for which a line holds, like:
(arch=!arm64)(c++)"gensios::gensio_cpp_vlog_handler(gensios::gensio_os_funcs*, gensios::gensio_log_levels, char const*, __va_list_tag*)@Base" 2.5.1
(arch=arm64)(c++)"gensios::gensio_cpp_vlog_handler(gensios::gensio_os_funcs*, gensios::gensio_log_levels, char const*, __va_list_tag*)@Base" 2.5.1
dpkg-gensymbols does not seem to be willing to grok the second line
("gensio_log_levels, not a valid version").
Also, the arch extension does not seem to be in deb-symbols(5).
What am I missing here?
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: