| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
When glibc is built with --enable-static-nss, the warning that
using NSS symbols requires the nss shared objects to be present
is no longer true, as those symbols are built into libc. Suppress
the warning for those symbols by providing a new macro
(nss_interface_function) for the NSS functions that is defined as
static_link_warning in the normal case, and empty for static NSS.
|
| |
|
|
|
|
| |
14152, 14783).
|
| |
|
|
|
|
|
|
|
|
| |
* elf/Makefile (tests): Remove conditional for have-initfini-array
since this is now always required and the variable does not exist
anymore.
(tests-static): Likewise.
(modules-names): Likewise.
|
| |
|
|
|
|
|
|
|
|
| |
* elf/tst-array1.c (fini_array): Make writeable so that it can be
merged with constructor/destructor.
(init_array): Likewise.
* elf/tst-array2dep.c (fini_array): Likewise.
(init_array): Likewise.
|
|
|
|
|
|
|
|
|
|
|
| |
Putting @cartouche inside of @smallexample does not work with HTML output
as the former produces a <table> while the latter produces a <pre>. You
cannot nest a <table> in a <pre> as the contents are no longer formatted.
Since it's entirely unnecessary, and none of the other examples do this,
just drop the cartouche.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
| |
Handle the case of the fd port implementing a stub (EOPNOTSUPP),
properly returning EINVAL.
|
|
|
|
|
| |
Check that _POSIX_REALTIME_SIGNALS is greater than zero to assume realtime
signals are supported, instead of any non-zero value (including -1).
|
|
|
|
|
|
|
|
|
|
|
| |
* sysdeps/unix/sysv/linux/x86/bits/fcntl.h (__O_LARGEFILE)
[!__x86_64]: Do not define, take value from <bits/fcntl-linux.h>.
* sysdeps/unix/sysv/linux/s390/bits/fcntl.h (__O_LARGEFILE):
[__WORDSIZE != 64]: Likewise.
* sysdeps/unix/sysv/linux/generic/bits/fcntl.h: (__O_LARGEFILE)
[__WORDSIZE != 64]: Do not define, take value from
<bits/fcntl-linux.h>.
|
| |
|
|
|
|
|
|
|
|
|
| |
* sysdeps/sparc/sparc64/multiarch/memcpy.S: Add comments for
ifunc-impl-list.c
* sysdeps/sparc/sparc64/multiarch/memset.S: Likewise.
* sysdeps/sparc/sparc64/multiarch/ifunc-impl-list.c: New file.
* sysdeps/sparc/sparc32/sparcv9/multiarch/ifunc-impl-list.c: New
file.
|
|
|
|
|
|
| |
* sysdeps/unix/sysv/linux/sparc/sparc64/get_clockfreq.c
(__get_clockfreq_via_proc_openprom): Use strtoumax instead
of strtoull.
|
|
|
|
| |
__get_clockfreq_via_proc_openprom.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test currently tests the binutils frontend support which passes for
all versions of binutils we currently require (2.20+). It doesn't test
the backend which is required for ifunc to actually work, and which most
targets don't yet support.
Change the assembly code so that when we link it, we get a file that has
ifunc relocations if the backend supports it. That way we can test to
see if binutils supports everything we need.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
| |
We don't currently want to rely on the -q option to grep.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* io/fcntl.h: Always define mode_t, off_t, pid_t and use these
types for creat, creat64, lockf, posix_fadvise, posix_fallocate.
[__USE_LARGEFILE64 && !__off64_t_defined]: Define off64_t.
[__USE_LARGEFILE64]: Use off64_t in declaration of lock64,
posix_fadvise64, posix_fallocate64.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
run-via-rtld-prefix.
|
|
|
|
| |
(O_RSYNC): Define to __O_RSYNC if it exists, otherwise to O_SYNC.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(F_GETLK, F_SETLK, F_SETLKW) [!F_GETLK]: Define values for [!__USE_FILE_OFFSET64].
|
| |
|
| |
|
|
|
|
|
| |
Remove all definitions and declarations that are provided by
<bits/fcntl-linux.h> and include <bits/fcntl-linux.h>.
|
| |
|
|
|
|
|
|
|
| |
Create a new bits/fcntl-linux.h that contains Linux generic code and a
include it from the architecture specific bits/fcntl.h.
Architectures done: x86, SPARC, s390
|
|
|
|
| |
Move include of <bits/types.h> to the top and include it unconditionally.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
[BZ #13601]
A read operation could return less than requested data for a number of
reasons.
|
| |
|
| |
|
| |
|
| |
|