@@ -25,7 +25,7 @@ HOST_GCC_INITIAL_POST_PATCH_HOOKS += HOST_GCC_COMMON_APPLY_PATCHES
# subdirectory in the gcc sources, and build from there.
HOST_GCC_INITIAL_SUBDIR = build
-HOST_GCC_INITIAL_PRE_CONFIGURE_HOOKS += HOST_GCC_COMMON_CONFIGURE_SYMLINK
+HOST_GCC_INITIAL_POST_PATCH_HOOKS += HOST_GCC_COMMON_CONFIGURE_SYMLINK
HOST_GCC_INITIAL_CONF_OPTS = \
$(HOST_GCC_COMMON_CONF_OPTS) \
@@ -43,7 +43,7 @@ HOST_GCC_POST_PATCH_HOOKS += HOST_GCC_COMMON_APPLY_PATCHES
# subdirectory in the gcc sources, and build from there.
HOST_GCC_SUBDIR = build
-HOST_GCC_PRE_CONFIGURE_HOOKS += HOST_GCC_COMMON_CONFIGURE_SYMLINK
+HOST_GCC_POST_PATCH_HOOKS += HOST_GCC_COMMON_CONFIGURE_SYMLINK
# We want to always build the static variants of all the gcc libraries,
# of which libstdc++, libgomp, libmudflap...
Currently, running make legal-info on an otherwise clean (but configured) tree will yield a spurious error message: find: ‘/home/ymorin/dev/buildroot/O/build/host-gcc-4.9.3/build’: No such file or directory However, creating that symlink in fact really prepares the gcc source tree to be configured. As such, it rather belongs to either the extract or patch steps. Make it a post-patch hook. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> --- package/gcc/gcc-initial/gcc-initial.mk | 2 +- package/gcc/gcc/gcc.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)