similar to: Re: [PATCH] klibc

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

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

Hi, I?ve gone through the mailing list archives and hereby want to resubmit my pending patches. Most are independent of each other, except the m68k patch which will only be complete if sigsuspend is also fixed. (It can be applied before that, though.) http://www.zytor.com/pipermail/klibc/2012-January/003173.html [PATCH] fix m68k support Resubmitted here as 0005. While there was a question from

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

please pull from git://charm.itp.tuwien.ac.at/mattems/klibc/.git branch maks. arch/mips/klibc/archconfig.h | 3 +++ klibc/sysconfig.h | 10 ++++++++++ sys/vfs.h | 17 +++++++++++++++++ 3 files changed, 30 insertions(+)

Hello all, I get unresolved external symbol __muloti4 when attempting to compile GNU m4 for Windows commandline. See details in bug: https://bugs.llvm.org/show_bug.cgi?id=16404#c22 Looking into this, I see that some parts of compiler-rt are disabled for Windows due to the __LP64__ define. The code seem not portable as is to the MS compiler, but according to my tests the code compiles and links

Hi, I've posted this question on OpenSS7 mailing list but I didn't get a clear answer. I have a system running asterisk using Digium T400P card. Can this same card be used with OpenSS7 project to carry SS7 links? Is there any difference between these two cards? -- Matteo D'Amato Network/Telecom Administrator Intelco Communication Inc

tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: c5db5a8d998da36ada7287aa53b4ed501a0a2b2b commit: b1b0d638e6f93b91cf34585350bb00035d066989 [13/15] mm: Introduce Reported pages config: ia64-defconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 7.4.0 reproduce: wget

This patch adds a macro abstracting the condition under which the silk math macros use opus_int64-based calculations rather than opus_int32. No substantive change, but will make it easier to adjust if additional such platforms are found in the future. --- silk/macros.h | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/silk/macros.h b/silk/macros.h index

Clang patch for X32 support. Applies against current trunk. --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6 backward compatibility">; def m3dnowa : Flag<["-"], "m3dnowa">,

On 11/08/2013 09:12 AM, Steve Capper wrote: > diff --git a/usr/klibc/open64.c b/usr/klibc/open64.c > new file mode 100644 > index 0000000..6ca603e > --- /dev/null > +++ b/usr/klibc/open64.c > @@ -0,0 +1,22 @@ > +/* > + * open64.c > + * > + * For 64 bit systems without the open syscall, pass straight > + * through into openat. > + */ > + > +#define

Hi, Is this card the same as the T410P, after all, it's made by Digium. There's one prior reference on the mailint list[1] but it didn't answer the question. There was also an SS7 status report[2] last June but it's doesn't seem to have lead anywhere either. There was post saying an SS7 release was immenent last September[3], but then silence. Any info anyone would like to

Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64

This is a klibc port to x32 architecture. I tried to reuse as many existing files as possible, hence, a script making symlinks to x86-64 files. I was running this on Debian for about six months and hopefully, found any close to surface bugs. Of course, there are plenty left. Please help with testing. To build you need to run: make ARCH=x32 Makefile | 15 ++--

Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:

Frontends are expected to write their protocol ABI to xenstore. Since the protocol ABI defaults to the backend's native ABI, things work fine without that as long as the frontend's native ABI is identical to the backend's native ABI. This is not the case for xen-blkfront running 32-on-64, because its ABI differs between 32 and 64 bit, and thus needs this fix. Based on

Frontends are expected to write their protocol ABI to xenstore. Since the protocol ABI defaults to the backend's native ABI, things work fine without that as long as the frontend's native ABI is identical to the backend's native ABI. This is not the case for xen-blkfront running 32-on-64, because its ABI differs between 32 and 64 bit, and thus needs this fix. Based on

--- celt/arch.h | 5 +++++ silk/macros.h | 4 +--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/celt/arch.h b/celt/arch.h index 9f74ddd..670527b 100644 --- a/celt/arch.h +++ b/celt/arch.h @@ -78,6 +78,11 @@ static OPUS_INLINE void _celt_fatal(const char *str, const char *file, int line) #define UADD32(a,b) ((a)+(b)) #define USUB32(a,b) ((a)-(b)) +/* Set this if opus_int64

This patch is still not creating elf32_x86_64 objects. No idea why. :( It does however, fix elf_x86_64 (-m64) code generation on x32 hosts which is nice. :) --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6