similar to: [mips] doesn't compile on little-endian

If you have access to an Alpha, please test klibc-1.3.21; in particular, anything which uses pipes... Thanks, -hpa

This was filed as a bug report on the Debian r-base package. It is more properly a bug report on the ctest package in R. The default method for wilcox.test manipulates x and y without checking the class or data.class of these objects. Possible solutions are - create wilcox.test.factor (if appropriate) - check the class and/or data.class of x and y in wilcox.test.default and produce error

Processing commands for control@bugs.debian.org: > reassign 368417 xen-hypervisor-3.0.2-1-i386 Bug#368417: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD Warning: Unknown package 'xen-hypervisor-3.0-i386' Bug reassigned from package `xen-hypervisor-3.0-i386' to `xen-hypervisor-3.0.2-1-i386'. > reassign 380333 xen-hypervisor-3.0.2-1-i386 Bug#380333:

We have NFS mounted drives. I first build an clang/llvm hosted compiler for Mips linux using the clang/llvm linux x86 compiler. Call this clang1. then in directory recurse on Mips host, I place this clang1 compiler and build clang2. then i rename recurse to recurse1 and create a new recurse directory. in recurse I copy clang2 from recurse1 to a recurse but name it clang1. then i build

I see the following on a Jetson TK1: [ 9.495425] [TTM] Initializing DMA pool allocator [ 9.495513] nouveau 57000000.gpu: DRM: VRAM: 0 MiB [ 9.495520] nouveau 57000000.gpu: DRM: GART: 1048576 MiB [ 9.508076] nouveau 57000000.gpu: DRM: failed to create ce channel, -22 A Google search suggests that I'm not the only one with this, but I don't see it being discussed anywhere. Is

Hello all, I really want to support vfork() in klibc, mostly because uClinux *has* to use it. Unfortunately vfork() isn't allowed to use the stack *at all* across the system call -- including return address -- which means it needs an assembly wrapper on most architectures. I have tried implementing wrappers for most architectures, but I don't know parisc or s390/s390x well enough,

Package: xen-unstable Version: 3.0-unstable+hg11292-2 Your package fails to build with GCC 4.2. Version 4.2 has not been released yet but I'm building with a snapshot in order to find errors and give people an advance warning. The bug below is in your package though and not because I'm using a snapshot of the compiler so please take a look at it. You can reproduce this with the

This fixes a long standing issue where it was not possible to do "make usr/klibc/arch/x86_64/longjmp.o" in the kernel. The principle is that all .o files to be part of klibc are listed with klib-y. For each directory a klib.list file is made that specify all .o file and the final AR then adds all .o files to create libc.a. This patch introduce the infrastructure and converts x86_64 to

On Wed, Apr 05, 2006 at 10:45:51PM +0200, maximilian attems wrote: [Received a forward of this mail and I had deleted the original one. So your reply-chain is broken]. > > sparc still needed to build with gcc-3.3 > belows makes use of the exported CC variable. > > also export the binutils for consistency, > added the missing ones too for klcc. > > > diff --git

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 +++

I'd like to use linear and quadratic trend analysis in order to find out a change in slope. Basically, I need to solve a similar problem as discussed in http://www.gseis.ucla.edu/courses/ed230bc1/cnotes4/trend1.html My subjects have counted dots: one dot, two dots, etc. up to 9 dots. The reaction time increases with increasing dots. The theory is that 1 up to 3 or 4 points can be counted

I have just pushed out a git tree which actually has the root-mounting code removed from the kernel. Since there are any number of strange boot configurations out there, I would really appreciate any help in testing this stuff out. I have *NOT* implemented support for the following, which I'm hoping has fallen out of use by now: -> Setting boot flags via rdev, as opposed to on the

Stop makeklcc.pl from hardcoding paths of cc, ld and strip in the klcc script it generates. Using hardcoded paths is generally a bad idea. First, the whole idea of $PATH is that you don't need to hardcode paths. Second, klcc is a Perl script but my hardcoding the paths you make it less portable. Signed-off-by: Martin Michlmayr <tbm@cyrius.com> --- klibc-1.1.16/klcc/makeklcc.pl~

Pipe doesn't work in dash on mips/mipsel - everything delivered to a pipe is shown on stdout: mipsel: $ echo foo | cat > ~/d foo <ctrl-c pressed manually> $ cat ~/d $ i386: $ echo foo | cat > ~/d $ cat ~/d foo $ This may be related to the following warnings during compilation but I'm not sure: klibc/arch/mips/syscall.S: Assembler messages: klibc/arch/mips/syscall.S:12:

Basic infrastructure for building klibc. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 5bba564a5c133369b3e83e5827d053a98cb3c59a tree 11f2acc1f9d845e8764fa790f522b79ea1106b80 parent 378abd8f4d39024ea6c87eb5b54155238f647f0d author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08

Package: blktap Version: 2.0.90-4 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

sparc still needs gcc-3.3 for a working run-init. belows makes use of the exported CC var. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index 66e16e7..70e4071 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -72,7 +72,7 @@ KLIBCROSS := $(CROSS_COMPILE) # binutils KLIBCLD := $(KLIBCROSS)ld

LLD uses "-R" as an alias for "-rpath", while LD uses "-R" as an alias for "--just-symbols". Use "--just-symbols" so that it's correctly supported for both linkers. See Linux commit 3c1918c8f54166598195d938564072664a8275b1 (riscv: fix vdso build with lld). Signed-off-by: Bill Wendling <morbo at google.com> --- scripts/Kbuild.klibc | 2

new klibc sparc build failure against gcc 4.2 ----- Forwarded message from Kilian Krause <kilian at debian.org> ----- Subject: Bug#440721: FTBFS on sparc while linking usr/klibc/libc.so From: Kilian Krause <kilian at debian.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Date: Mon, 03 Sep 2007 23:35:23 +0200 Package: klibc Version: 1.5.6-2 Severity: serious

From: Maciej ?enczykowski <maze at google.com> This adds a new setting: KBUILD_REPRODUCIBLE If it is non-empty, ar and ranlib will be called in such a way that timestamps do not affect the build output. This allows one to get perfectly reproducible builds. Signed-off-by: Maciej ?enczykowski <maze at google.com> --- scripts/Kbuild.klibc | 14 +++++++++----- usr/klibc/Kbuild |