-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] 4.99.0 - Installs liblsof.a even when --disable-static is mentioned #299
Comments
It seems to be a limitation of libtool. Can we workaround it? |
subnut
added a commit
to subnut/lsof
that referenced
this issue
Nov 14, 2023
subnut
added a commit
to subnut/lsof
that referenced
this issue
Nov 14, 2023
subnut
added a commit
to subnut/lsof
that referenced
this issue
Nov 14, 2023
subnut
added a commit
to subnut/lsof
that referenced
this issue
Nov 14, 2023
I've tried my hand at a possible workaround in #300 This is my first time interacting with autoconf/automake, so there may be mistakes.. |
subnut
added a commit
to subnut/lsof
that referenced
this issue
Nov 14, 2023
It's disabled by default since liblsof is still in alpha stage
jiegec
pushed a commit
that referenced
this issue
Nov 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
configure --disable-static --disable-shared
should result in neither the static nor the shared libraries to be installed. And since the libraries aren't being installed, the header files shouldn't be installed either.Currently, it behaves as if
--disable-static
was never mentioned, i.e. installing bothliblsof.a
and the header files (lsof.h
,lsof_fields.h
)To Reproduce
Steps to reproduce the behavior:
configure --enable-security --disable-static --disable-shared
make
make install
Expected behavior
Libraries and Header files not being installed
Actual behaviour
Static library is installed. Header files are installed
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: