Am 18.08.19 um 03:13 schrieb أحمد المحمودي:

> And a bit of access to architecturesthat I don't have access to (arm64 
> for example)

Even if you are not a DD you can get access to the porterboxes. For
exactly this reason like here.

https://dsa.debian.org/doc/guest-account/

If this is all to much work for you drop me a note you need help with
the symbols file. I'll have a look at this of course. systemc isn't
moving that fast this additional work isn't possible for me.

BTW: The main mess with the symbols file would go away it upstream would
use versioned symbols! That would decrease the amount of content within
the symbols file to a minimum.

> As far as I understand the symnols files is to track symbol changes due 
> to changes in the library itself, not the compiler used to build that 
> library !

To track symbol changes within the library itself it isn't really
helpful if these changes aren't visible for other tools. So the main
goal is that dh-mkshlibdeps can get information about the depending
minimal version for the depending library while building the list of the
depending libraries for a package.

This all has nothing to do directly with the used compiler or linker.

The libsystemc package isn't a central library like libc e.g. for sure,
otoh it's not that complicated to keep track of the symbol name changes
and provide a symbols file.

-- 
Regards
Carsten Schoenert

Reply via email to