Open praedicow opened 2 years ago
Hi @praedicow,
Thanks for pointing this out. This seems to be a mistake happened in SVDConv.
Do you have any issues with latest PackChk 1.3.95 as well? PackChk is built with -static-libc++
so only the libc
is used dynamically. Is this sufficient or do we need to use -static
instead to force full static linkage?
Cheers, Jonatan
Hey Jonatan,
thank you for your fast reply. We do not have the issue in PackChk 1.3.95, so dynamic linkage of libc
is okay for us, but to reduce dependencies, full static linkage may be more robust.
The older versions of PackChk and SVDConv used full static linkage.
Best regards Alex
Hi Alex,
Yes, that's true. Thanks for confirming that libc
is okay for you. We need to discuss potential other side-effects.
But I think we will at least add -static-libc++
for SVDConv.
Cheers, Jonatan
Hello,
currently we're using KEIL Utilities v 5.8.0 for our KEIL-Pack generation flow on a Linux server. I tried to update our flow to the latest KEIL Utilities (SVDConv and PackChk) to Version 5.9.0, but the problem occurred, that there are some dependencies which our system can not resolve.
This didn't occur in any of the older versions of these tools. So my question is, if it's possible, that you could switch back these tools to static linked executables?
Thank you for your support. Alex