similar to: klibc-0.124 released with 64-bit off_t and struct statfs64

From: Steve Langasek <vorlon@debian.org> Fix the definition of struct statfs64, required for run-init to work on alpha. verified to have no regressions on amd64. Signed-off-by: maximilian attems <janitor@sternwelten.at> Signed-off-by: Frederik Sch?ler <fschueler-guest@costa.debian.org> --- klibc-1.1.1.orig/include/sys/vfs.h +++ klibc-1.1.1/include/sys/vfs.h @@ -32,17 +32,17

Commit-ID: 11bd4ea5f3d960c4d208180deae91d88aa940149 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=11bd4ea5f3d960c4d208180deae91d88aa940149 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 21 Jan 2019 03:39:34 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 03:45:04 +0000 [klibc] fcntl: Fix struct flock

Here's an assortment of build and run-time fixes for various architectures that we've applied in Debian. Ben. Aurelien Jarno (1): ppc64: fix struct stat Ben Hutchings (2): MIPS: Update archfcntl.h syscalls: Override detection of direct socket syscalls on i386, m68k, s390 Helge Deller (1): Add pread and pwrite 32bit syscall wrappers for parisc Mauricio Faria de Oliveira

From: Sjoerd Simons <sjoerd@spring.luon.net> It seems that klibc uses __sparc64__ to determine if it's compiled in 64 bit mode on sparc, unfortunatly gcc doesn't define __sparc64__ :) It does define __arch64__ though. Signed-off-by: maximilian attems <maks@sternwelten.at> --- klibc-1.2.2.orig/include/sys/vfs.h 2006-02-15 18:32:10.000000000 +0100 +++

It seems that klibc uses __sparc64__ to determine if it's compiled in 64 bit mode on sparc, gcc doesn't define __sparc64__ use __sparc_v9__ instead as proposed by Kyle McMartin <kyle@parisc-linux.org>, based on a patch by Sjoerd Simons <sjoerd@spring.luon.net> Signed-off-by: maximilian attems <maks@sternwelten.at> --- resend --- klibc-1.2.2.orig/include/sys/vfs.h

Hold on to your hats, because the world is about to break... I have been trying to figure out for a while now how to migrate klibc to a 64-bit off_t, and to handle other things like getuid32(). The final decision is that the _syscall*() macros just got to go; they aren't flexible enough, and the hope that they would make it easier to port between platforms hasn't worked out -

If you export two subvolumes of a btrfs filesystem, they will both be given the same uuid so lookups will be confused. blkid cannot differentiate the two, so we must use the fsid from statfs64 to identify the filesystem. We cannot tell if blkid or statfs is best without knowing internal details of the filesystem in question, so we need to encode specific knowledge of btrfs in mountd. This is

We are trying to enable large file support for everything built for ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version for compatibility with open64. When looking into enabling the large file support flags, I noticed: `void start_progress_meter(const char *, off_t, off_t *);` in progressmeter.h which would have different ABIs with and without large file support. You all

On Wed, 22 Mar 2023, Allen Webb wrote: > We are trying to enable large file support for everything built for > ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version > for compatibility with open64. When looking into enabling the large > file support flags, I noticed: > > `void start_progress_meter(const char *, off_t, off_t *);` > > in progressmeter.h

Hi, is there a DD-accessible porterbox somewhere (slow would be ok, as this is smallish software) with an up-to-date sid (enough to install the recently-built libklibc-dev 2.0~rc5-1 and all other B-D of mksh 40.9.20120518-1, as well as strace and gdb-minimal)? Similarily to http://www.zytor.com/pipermail/klibc/2012-May/003229.html I found klibc-compiled programmes on Alpha to fail (SIGSEGV

Hi! Now that there are usable userspace headers, we should use the data from those. In this case, the workaround in usr/include/sys/types.h was missing some header definitions. Rather than adding the definitions, I figured that the most correct thing to do was to just use them from the kernel. Build tested on i386 and x86_64. Signed-Off-By: Jeff Bailey <jbailey at ubuntu.com> -- Jeff

Hi, I have experimentally done a branch of klibc with buffered stdio support. It seems to add about 1.5K of code (for x86-64), which isn't so bad, except that it means that *every* program now pulls in stdio, which in turn depends on malloc() and some other pieces of code. I have not yet implemented fscanf(), however, which may cause additional bloat. As of this point, I'm a bit

Commit-ID: 3cb3ceea23ecbf2c804bf732e8234552d097b94f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3cb3ceea23ecbf2c804bf732e8234552d097b94f Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 18 Jan 2019 18:39:21 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 18:46:45 +0000 [klibc] fcntl: Fix file locking

Commit-ID: 454901a0c733986bee36da111a08fe7df0ff0b98 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=454901a0c733986bee36da111a08fe7df0ff0b98 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Fri, 28 Aug 2020 19:48:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 20:22:50 +0100 [klibc] ia64: Fix sigaction struct

Hello All, Attached is a patch against the portable openssh sources found at openssh at anoncvs.at.openbsd.org:/cvs. The majority of the size of the patch comes from changes to the build system to supply the required format specifications if they are not provided by the OS. These patches remove the following warnings found during a 64-bit compile: hostfile.c: In function

Commit-ID: ce358438679db7488f36706feaf64d6d5ab84ad6 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ce358438679db7488f36706feaf64d6d5ab84ad6 Author: Aurelien Jarno <aurelien at aurel32.net> AuthorDate: Wed, 6 Jan 2016 00:44:16 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:45:55 -0800 [klibc] ppc64: fix struct stat

Commit-ID: 12f259dda1ef59b5f1f2fb67631dcbf94c18c56c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=12f259dda1ef59b5f1f2fb67631dcbf94c18c56c Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 4 Jan 2023 01:34:39 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 4 Jan 2023 01:34:39 +0100 [klibc] mips64: Fix struct stat

Hi, I am trying to build Klibc on a 64-bit Ubuntu on a x86 machine. Here are the steps I followed: 1. Got the source wget https://launchpad.net/ubuntu/+archive/primary/+files/klibc_2.0.1.orig.tar.gz tar xvzf klibc_2.0.1.orig.tar.gz wget https://launchpad.net/ubuntu/+archive/primary/+files/klibc_2.0.1-3.1ubuntu1.debian.tar.gz tar xvzf

On Sat, Jan 14, 2023, at 23:03, klibc-bot for Ben Hutchings wrote: > > #include <klibc/extern.h> > +#include <klibc/endian.h> > #include <stddef.h> > #include <sys/types.h> > -#include <linux/time.h> > + > +struct timespec { > + __kernel_time64_t tv_sec; > +#if __BYTE_ORDER == __BIG_ENDIAN && __BITS_PER_LONG == 32 > + long

I have released a patch for klibc which changes off_t to 64 bits, and hopefully deals with most of the rest of the fallout. We shouldn't be using any obsolescent types anymore, except for struct statfs (I intend to hack that next so we use statfs64() and fstatfs64()). We're still using some older system calls, like sigaction() instead of rt_sigaction() where available, but