| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the regular ustar header that are overridden by the pax
extended attributes. As a result, it makes perfect sense to
use numeric extensions in the regular ustar header so that readers
that don't understand pax extensions but do understand some other
extensions can still get useful information out of it.
This is especially important for filesizes, as the failure to
read a file size correctly can get the reader out of sync.
This commit introduces a "non-strict" option into the internal
function to format a ustar header. In non-strict mode, the formatter
will use longer octal values (overwriting terminators) or binary
("base-256") values as needed to ensure that large file sizes,
negative mtimes, etc, have the correct values stored in the regular
ustar header.
|
|
|
|
|
| |
which is really, really dumb and just going to cause confusion among
people who understand that "ustar" is also a POSIX standard tar format.)
|
|
|
|
| |
cutoff to >= 8G, as it should be.
|
| |
|
| |
|
|
|
|
| |
it will work cleanly with autoconf.
|
| |
|
|
|
|
| |
timestamps.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
archive_version: Returns a text string, e.g., "libarchive 1.00.000"
archive_api_version: Returns the SHLIB major version
archive_api_feature: Returns a feature number useful for answering
questions such as "Is this recent enough to do XXX?"
The last two also have macros defined in archive.h, so you can compare
the compile-time and run-time environments. (In particular, you can
compare ARCHIVE_API_VERSION to archive_api_version() to detect library
version mismatches.)
With these in hand, it will soon be time to turn on the
shared-library version of libarchive... stay tuned.
|
|
|
|
|
|
|
|
| |
Thanks to: David O'Brien for pointing this out.
Also, add in a few additional portability tweaks and make a few
more things conditional on features (HAVE_XXXX macros) rather
than platform.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular, this means we can now correctly read gtar archives that
contain timestamps prior to the start of the Epoch.
Also, make the code in this area more portable. ANSI C99 headers are
not yet ubiquitous (for example, FreeBSD 4 still lacks them), so be
prepared for systems that don't have the INT64_MAX, INT64_MIN, and
UINT64_MAX macros. This version still requires int64_t and uint64_t be
defined (which can be done in archive_platform.h if necessary), but
doesn't require them to be exactly 64 bits.
|
|
|
|
| |
Noticed by: Todd Miller <Todd.Miller@courtesan.com>
|
|
|
|
| |
nwc dropping to zero.
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
instead of making repeated calls to __fgetwc().
|
|
|
|
|
|
|
| |
convenient when the source string isn't null-terminated.
Implement the other conversion functions (mbstowcs(), mbsrtowcs(), wcstombs(),
wcsrtombs()) in terms of these new functions.
|
|
|
|
| |
string instead of multiple calls to __fputwc().
|
|
|
|
|
|
|
|
| |
file as an argument, it may still fail for the same reasons that
open(2) can.
Pointed out by: Jilles Tjoelker
Apporived by: bmilekic (mentor)
|
|
|
|
|
|
|
|
| |
for statfs(2). This is false, if the pathname specified
is a regular file, then the information for the file
system that the file lives on will be returned.
Approved by: bmilekic (mentor)
|
|
|
|
| |
through mbrtowc() and wcrtomb().
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gcc is using. This fixes devstat consumers (like vmstat, iostat,
systat) so they don't print crazy zillion digit numbers for
disk transfers and bandwidth.
According to gcc, long doubles are 64-bits, rather than 128 bits
like the SVR4 ABI spec wants them to be.. Note that MacOSX also treats
long doubles as 64-bits, and not 128 bits, so we are in good company.
Reviewed by: das
Approved by: grehan
|
|
|
|
|
| |
array of one element of type struct reg. Change the argument to
libc_r_md_getgregs() accordingly.
|
| |
|
|
|
|
| |
the time being.
|
| |
|
|
|
|
| |
not the link register, which was lucky enough to work.
|
| |
|
|
|
|
| |
with "sh mkh" so it works if the script is not executable.
|
|
|
|
| |
of OANYOF sets for the moment.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- It was added to libc instead of libm. Hopefully no programs rely
on this mistake.
- It didn't work properly on large long doubles because its argument
was converted to type double, resulting in undefined behavior.
|
|
|
|
| |
for subnormals with one implementation that works.
|
|
|
|
|
|
| |
headers from libpthread that are not WARNS=2 clean for -O2 builds.
Lower the WARNS level to 1. This is the highest level possible for
now.
|
|
|
|
|
|
|
|
|
| |
notably, this restores some of the contents in thread_db.h as well
as David Xu's copyright notice. This also fixes the includes in
the MD libpthread files which Scott tried to provide a quick fix
for.
Pointy hat: marcel
|
|
|
|
| |
up now, but it appears to be the same problem and solution as sparc64.
|
| |
|
|
|
|
|
|
|
| |
of features required by the standard that the current implementation
does not support.
PR: 57911 (related)
|
|
|
|
|
|
|
| |
of features required by the standard that the current implementation
does not support.
PR: 57911
|
|
|
|
|
| |
Porting libthread_db to arm and/or powerpc is easy enough, but
we don't build gdb on those platforms yet.
|
| |
|
|
|
|
| |
libthread_db. Both headers are included seperately.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
i386, ia64 and sparc64. Add stubs for alpha, amd64, ia64 and sparc64 for
libpthread.
Restructure the source files to avoid unnecessary use of subdirectories
that also force us to use non-portable compilation flags to deal with
the uncommon compilation requirements (building archive libraries for
linkage into a shared library).
The libpthread support has been copied from the original local and
cleaned-up to make them WARNS=2 clean.
that also force us to use non-portable compilation flags to deal with
the uncommon compilation requirements (building archive libraries for
linkage into a shared library).
The libpthread support has been copied from the original local and
cleaned-up to make them WARNS=2 clean.
Tested on: amd64, i386, ia64
|
|
|
|
| |
functions.
|
|
|
|
|
| |
nearbyint(), round() and trunc() shouldn't be visible when compiling with
-D_XOPEN_SOURCE=500.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Unlike the builtin relational operators, builtin floating-point
constants were not available until gcc 3.3, so account for this.[1]
- Apparently some versions of the Intel C Compiler fallaciously define
__GNUC__ without actually being compatible with the claimed gcc
version. Account for this, too.[2]
[1] Noticed by: Christian Hiris <4711@chello.at>
[2] Submitted by: Alexander Leidinger <Alexander@Leidinger.net>
|
| |
|