Skip to content
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

meson and Makefile buildsystems install conmon on different locations #304

Open
dilyanpalauzov opened this issue Oct 8, 2021 · 2 comments

Comments

@dilyanpalauzov
Copy link

dilyanpalauzov commented Oct 8, 2021

Using the meson build system, calling ninja install prints on my system:

[0/1] Installing files.
Installing conmon to /usr/local/libexec/podman

Using the make build system, calling make install prints:

install  -D -m 755 bin/conmon /usr/local/bin/conmon
make -C tools
make[1]: Entering directory '/src/containers/conmon-2.0.30/tools'
make[1]: Leaving directory '/src/containers/conmon-2.0.30/tools'
make -C docs
make[1]: Entering directory '/src/containers/conmon-2.0.30/docs'
../tools/build/go-md2man -in conmon.8.md -out conmon.8
make[1]: Leaving directory '/src/containers/conmon-2.0.30/docs'
make -C docs install
make[1]: Entering directory '/src/containers/conmon-2.0.30/docs'
install -d //usr/local/share/man/man8
install -m 0644 conmon*.8 //usr/local/share/man/man8
make[1]: Leaving directory '/src/containers/conmon-2.0.30/docs'

So the one build system install under /usr/local/bin/conmon, the other build system installs under /usr/local/libexec/podman . This makes no sense. I see no point to install conmon under /usr/local/libexec, when it will be called by cri-o.

@rhatdan
Copy link
Member

rhatdan commented Oct 12, 2021

Care to open a PR to fix?

@dilyanpalauzov
Copy link
Author

No. Honestly, I even do not know how this can be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants