Why doesn't install-strip strip shared libraries sometimes

. What might prevent install-strip from stripping liblink-grammar.so? Thanks, Yuri

How does one report bugs for automake?

I recently reported a bug about install-strip not stripping the shared library for one particular project, and there is no answer. Is this ML the right place to report bugs? Thanks, Yuri

Re: Why does one shared library cause the project to fail: Warning: Linking the executable x against the loadable module

On 03/30/18 22:52, Yuri wrote: This project (calf studio) fails to build for me. Here is the Makefile.am that seems to cause a problem: https://github.com/calf-studio-gear/calf/blob/master/src/Makefile.am It builds the shared library calf.so. The library is built, but later it fails when

Why does one shared library cause the project to fail: Warning: Linking the executable x against the loadable module

-frame-pointer -std=c++11 -Wall  -L/usr/local/lib -fstack-protector -o calfmakerdf makerdf.o calf.la *** Warning: Linking the executable calfmakerdf against the loadable module *** calf.so is not portable! What is wrong with this library? Yuri

Project "calf-studio" fails with Warning: Linking the executable calfmakerdf against the loadable module

issues/156 has stalled. This issue exists in multiple systems: ||OpenMandriva, Gentoo, FreeBSD. What is wrong in this project that causes it to fail like this? Thank you, Yuri |