https://sourceware.org/bugzilla/show_bug.cgi?id=32254
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
(In reply to rdiez-2006 from comment #0)
> After upgrading to binutils 2.43 and 2.43.1, I have sporadic build errors
> like this:
> GEN doc/asconfig.texi
> chmod: cannot access 'doc/asconfig.texi': No such file or directory
> Can someone help?
This sounds like there is a race condition somewhere in the binutils make
system. It may not even be related to the 2.43 sources per se. It may just be
that the 2.43 sources are more prone to exposing the problem.
Are you running make with the "-j" option specified ? If so, does the problem
go away if you omit this option or use "-j 1" ?
In theory there should not be any need for you to regenerate the
doc/asconfig.texi file, but there is a problem when you are building from a
source tarball. Since the last-modified timestamp on the .info files matches
that on the .texi files, the build system thinks that it needs to regenerate
all of the documentation, including the doc/asconfig.texi file.
To avoid this problem you need to add an extra step after extracting the
tarball. So for example in the Makefile.txt file on the DebugDee site there
is:
$(BINUTILS_UNTAR_SENTINEL): $(CROSS_TOOLCHAIN_BUILD_DIR_SENTINEL)
echo && \
echo "Unpacking $(BINUTILS_TAR_FILE) ..." && \
if [ -d "$(BINUTILS_SRC_DIR)" ]; then rm -rf -- "$(BINUTILS_SRC_DIR)";
fi && \
pushd "$(CROSS_TOOLCHAIN_BUILD_DIR)" >/dev/null && \
tar xfa "$(TARBALLS_DOWNLOAD_DIR)/$(BINUTILS_TAR_FILE)" && \
popd >/dev/null && \
echo "Unpacking Binutils finished." >"$(BINUTILS_UNTAR_SENTINEL)" && \
echo "Unpacking Binutils finished."
If instead this was:
$(BINUTILS_UNTAR_SENTINEL): $(CROSS_TOOLCHAIN_BUILD_DIR_SENTINEL)
echo && \
echo "Unpacking $(BINUTILS_TAR_FILE) ..." && \
if [ -d "$(BINUTILS_SRC_DIR)" ]; then rm -rf -- "$(BINUTILS_SRC_DIR)";
fi && \
pushd "$(CROSS_TOOLCHAIN_BUILD_DIR)" >/dev/null && \
tar xfa "$(TARBALLS_DOWNLOAD_DIR)/$(BINUTILS_TAR_FILE)" && \
find . -name *.info -exec touch {} && \
popd >/dev/null && \
echo "Unpacking Binutils finished." >"$(BINUTILS_UNTAR_SENTINEL)" && \
echo "Unpacking Binutils finished."
(Ie, a find command is run after the tar xfa)
Then this might also solve your problem.
I hope that this helps.
--
You are receiving this mail because:
You are on the CC list for the bug.
