make install fails when INSTALL_DIR is defined #911
Labels
No labels
announcement
bug
build
CI
dependencies
documentation
duplicate
enhancement
experience feedback
feature request
github_actions
help wanted
install
invalid
Long-term
optimization
portability
question
target-specific
test issue
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Cyan4973/xxHash#911
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since v0.8.2 the build fails, when
INSTALL_DIRenv variable is definedThe build is broken by
836f4e7The following line in Makefile must be omitted
and to create target directories, the use of
$(Q)$(INSTALL_DIR)must be replaced by$(Q)$(INSTALL) -d -m 755as before.Notes:
INSTALL_DIRis a common variable for make, similar toDESTDIRand may not be used by Makefile for any other purpose.It may very well be true, but It's a pity I can't find any information on this
INSTALL_DIRvariable.In contrast,
DESTDIRis very well documented.Is there a reference place where these variables are listed ?
@Cyan4973 sorry,
INSTALL_DIRis not related to make, but it is common for cmake for external projects (for example https://cmake.org/cmake/help/latest/module/ExternalProject.html)I faced this issue in the spksrc project, where we build native packages for synology diskstation devices.
We have one environment to build packages with make, cmake, rust, go, meson, etc.
In this environment
INSTALL_DIRis always defined.To build
rsyncthat depends onxxhashI added a patch for the Makefile to use the former version to create target folders (seecross/xxhash/patches/001-fix_Makefile.patchin https://github.com/SynoCommunity/spksrc/pull/5985/commits/6e2b9b6021081310ec1d515be85130224c7c0a2e)Since
INSTALL_DIRwas introduced in xxHash Makefile without documenting a reason what this is for, I think it could be reverted to the former version - or you could use a different variable name likeINSTALL_DIRECTORYorCREATE_DIRECTORYto avoid such side effects.