GLIBC 2.24 declared readdir_r as deprecated and suggests to use readdir.
uClibc-ng's readdir is thread-safe as well.
Signed-off-by: Alexey Neyman <stilor@att.net>
The patch provided by the original submitter did not apply cleanly to 4.9.3; had a fuzz 2.
We only allow fuzz 1. Fix up the patch.
Signed-off-by: Alexey Neyman <stilor@att.net>
Old series of patches:
1) update configure with old patch for 4.5.18
2) update configure.ac
3) update configure again, effectively reverting changes
from 1).
Remove patch 1) and regenerate patch 3)
Signed-off-by: Kirill K. Smirnov <kirill.k.smirnov@gmail.com>
User cannot choose D.U.M.A. versions prior to 2.5.15 in config,
so remove useless patches.
Signed-off-by: Kirill K. Smirnov <kirill.k.smirnov@gmail.com>
Fixed compile error for DUMA 2.5.15 due to different function prototypes
for new operator in c++03 vs c++11
Signed-off-by: Yogesh Sharma <ysharm01@harris.com>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69959
...was observed while trying to build gcc-5.3.0 on latest (at the time
of this change) archlinux using gcc-6.1.1.
This patch fixes the issue.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Currently, native GDB 7.11 fails to build with uClibc-ng due to
undefined reference to _obstack_free.
On IRC
[http://crosstool-ng.osuosl.org/download/ibot-logs/2016-02-28.html], it
has been suggested to disable obstack in uClibc configuration. I think
it is a workaround rather than a fix: if another library/app needs
obstack, this leaves no viable configuration. IMO, if uClibc seeks to
mimic the glibc API, it should also provide _obstack_free call (an
alias for which it already has, even though commented out).
Signed-off-by: Alexey Neyman <stilor@att.net>
There is invalid assembly in dmalloc for PowerPC. The issue is that
'stw' expects a memory operand, and =g constraint allows both registers
and memory. Newer GCC tends to choose register even at -O0, resulting in
invalid assembly. Instead, force a register constraint in 'mflr' and let
GCC decide if it wants to store it into memory at all.
Reported this upstream.
Signed-off-by: Alexey Neyman <stilor@att.net>
CFLAGS_FOR_TARGET and CXXFLAGS_FOR_TARGET are rewritten in gcc-4.8.x and
gcc-4.9.x, so libstdc++ does not get any flags passed to gcc configure.
Backport fixes for config/mt-gnu and config/mt-ospace that preserve these
flags. With these fixes libstdc++ gets built with flags specified in
CT_TARGET_CFLAGS.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Despite the documentation and the comment in xtensa_move_literals, in
the presence of --text-section-literals and --auto-litpools literals are
moved from the separate literal sections into .init and .fini, because
the check in the xtensa_move_literals is incorrect.
This fixes build errors seen with projects that have .init/.fini and use
text-section-literals.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Binutils change 1058c7532d0b "Use signed data type for R_XTENSA_DIFF*
relocation offsets." changed signedness of BFD_RELOC_XTENSA_DIFF*
relocations substituted for BFD_RELOC_*. This made it impossible to
encode arbitrary 8-, 16- and 32-bit values, which broke e.g. debug info
encoding by .loc directive. Revert this part and add test.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
This updates patches for 2.26. Most notably, the removal of the xtensa
patches which seem to be upstream in binutils now.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
