[e2fsprogs-1.45.6] Installation error when MKDIR_P uses config/install-sh #51
Comments
tytso
added a commit
that referenced
this issue
Oct 5, 2020
In the case where mkdir -p is not thread-safe (for example, if the build environment is using busybox's mkdir) the configure script will fall back to the slow (but safe) install-sh script. In that case MKDIR_P will be using a relative pathname; so we can't use speed optimization of defining configure substitutions in MCONFIG.in, since the substitution will be different depending on depth of the subdirectory in the Makefile.in file. #51 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
|
Thanks for the bug report! See the explanation of the root cause in the fix which I just pushed to the maint branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While attempting a cross-compiler build in a busybox environment, the package configuration script deemed the busybox "mkdir -p" not thread safe and therefore selects the config/install-sh script instead for the Makefile MKDIR_P command variable. The e2fsprogs package is built successfully, however during subdirectory installation 'make' is unable to find the script that resides in the config directory of the parent and not in the current subdirectory.
Installing the GNU coreutils mkdir to replace the busybox version is a workaround and demonstrates that the issue resides with the MKDIR_P selection.
The text was updated successfully, but these errors were encountered: