LPIC-1 Linux Installation and Package Management Practice Question
A user compiling software from source successfully runs './configure' and 'make', but the resulting binaries are not in the PATH. Which command should be run to install them system-wide?
⚠ Common exam trap
LPIC-1 often tests the confusion between the compile stage ('make') and the install stage ('make install'), catching candidates who assume that a successful 'make' automatically places binaries in PATH.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
make install
After './configure' and 'make' compile the source code, the binaries are built but remain in the local build directory. The 'make install' target copies the compiled binaries, libraries, and configuration files to their system-wide destinations (typically /usr/local/bin, /usr/local/lib, etc.) as defined by the Makefile's install prefix. Without running 'make install', the binaries exist only in the source tree and are not accessible via PATH.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
make
Why it's wrong here
Running 'make' again only recompiles; it never copies binaries into system directories. The install target, typically 'make install', performs that copy. 'make' is tempting because it builds the software, which is the visible step before installation, and it would suffice if the goal were merely to rebuild after a source change.
- ✗
make all
Why it's wrong here
`make all` merely rebuilds every default target, leaving the compiled binaries in the build directory rather than copying them into system locations such as /usr/local/bin. It tempts because `all` is conventionally the default build target, so it is the correct invocation when you need to compile all targets after editing sources, not to install them.
- ✗
make clean
Why it's wrong here
'make clean' deletes object files and build artefacts from the source tree, leaving nothing to install, so it cannot place binaries in a system directory. It is tempting because it is the routine way to reset a build before recompiling after a failed or stale compile, which is a build-hygiene task rather than installation.
- ✓
make install
Why this is correct
'make' compiles but does not place binaries in system directories. 'make install' runs the install target defined in the Makefile, copying the built binaries to their configured system-wide locations such as /usr/local/bin, making them available on the PATH.
Go deeper
Related to this question
About these practice questions
This LPIC-1 question is part of Courseiva's 402-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official LPI exam blueprint
This LPIC-1 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-1 exam.