in order to work around GCC reordering compares across the TLS
descriptor sequence (GCC PR61545.) Committing a (temporary) fix here
allows us to avoid rebuilding the world with gcc 4.9.0-11.fc21.
Following commit upstream removed the definition for elfobjdir in
favour of elf-objpfx. Adjust rtkaio to build with this.
commit 4134b50d6789c333707b1861a32314805bd0de5e
Author: Joseph Myers <joseph@codesourcery.com>
Date: Wed May 21 16:52:08 2014 +0000
Consistently use $(elf-objpfx).
As previously noted
<https://sourceware.org/ml/libc-alpha/2013-05/msg00696.html>,
$(elf-objpfx) and $(elfobjdir) are redundant and should be
consolidated. This patch consolidates on $(elf-objpfx) (for
consistency with $(csu-objpfx)), also changing direct uses of
$(common-objpfx)elf/ to use $(elf-objpfx).
After each test run we output all of the test results
to the build logs. This includes PASS, FAIL, XPASS,
XFAIL results and the original error codes of the tests.
Without this fix the new upstream PASS/FAIL support
hides the test results from the build logs.
Currently the nscd service is installed in systemd as a simple
service, which means that it is able to handle its own errors and does
not quit. Since nscd does not fit that description, i.e. it can exit
on errors like, say, failing to parse nscd.conf, it should be declared
as forking instead.
The call to open_tmpl_archive was being passed a pointer to an
object allocated on the stack. The object on the stack is not
guaranteed to be initialized to zero so we need to minimally
initialize `fname' in the struct locarhandle to ensure that
open_tml_archive loads the default tempalte.
This error was seen while debugging glibc installs in a qemu
VM where it is more likely the stack pages were dirty. It has
not been reported on non-VM systems.
Usage:
1. Invoke the script as follows:
./sync-upstream.sh upstream-repo
where upstream-repo is the path to the synced upstream git repo.
2. Watch the script run. If it proceeds to building the package, then
everything seems good and you just need to test the build after it
is complete. If it exits before the build (you'll know if you read
the output of the script) then manual intervention is required to
complete the sync. This will typically happen when a patch fails
to apply on the new sources.