Stream: Coq devs & plugin devs

Topic: ✔ Are static libraries really unstripped?

Julien Puydt (Nov 13 2021 at 09:49):

While packaging coq-related software (including coq), the lintian Debian tools complains about almost every .a file with the unstripped-static-library hint. That leads me to two questions:

• are the symbols detected really what lintian thinks they are, or is it a false positive?
• if they are real positive, what can I do at configure-time or build-time to strip those libs?

Julien Puydt (Nov 13 2021 at 09:58):

Do CFLAGS, CPPFLAGS, CXXFLAGS and LDFLAGS variables have any impact? They get set during the build, but if they're ignored, that might explain a few other warnings...

Emilio Jesús Gallego Arias (Nov 13 2021 at 11:39):

@Julien Puydt I think here we should follow what is done in the rest of OCAml packages, what is done on others?

Julien Puydt (Nov 13 2021 at 14:51):

Emilio Jesús Gallego Arias said:

Julien Puydt I think here we should follow what is done in the rest of OCAml packages, what is done on others?

About stripping? From looking around, that really depends on the package, but I get the impression that the more recent, the worse. Like: ocamlbuild-using packages strip, dh_ocaml-using packages don't... which could be a bug

Julien Puydt (Nov 13 2021 at 16:49):

Oh, and I see I call the make targets with STRIP=true... but there's nowhere to be seen where it's actually used!

Julien Puydt (Nov 13 2021 at 16:50):

ah, configure.ml uses it... for nothing

Paolo Giarrusso (Nov 13 2021 at 19:32):

Re CXXFLAGS and CFLAGS, those should only affect C++/C code (but I haven't studied Coq's build scripts). Not sure for the other variables you mention.

Julien Puydt (Nov 13 2021 at 22:22):

It turns out that if I call strip manually on all .a (well, I manually ask the shell to loop and do that), then things get right!

Notification Bot (Nov 13 2021 at 22:22):

Julien Puydt has marked this topic as resolved.

Last updated: Dec 05 2023 at 05:01 UTC