similar to: Any Alpha users...

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,

When I compile klibc on little-endian mips, I get: KLIBCLD klibc/libc.so ld: klibc/arch/mips/crt0.o: compiled for a little endian system and target is big endian ld: klibc/arch/mips/crt0.o: endianness incompatible with that of the selected emulation ld: failed to merge target specific data of file klibc/arch/mips/crt0.o When I change "elf32-tradbigmips" to

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:

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

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

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

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

Package: xen Version: 4.6.0-1+nmu2 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > mkdir -p compat > grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \ > python /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py

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:

Package: xen Version: 4.6.0-1 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation 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

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~

I was wondering if it would be possible to add a cpio (extraction) implementation to klibc. Maybe this can be done in a way that the code could bet shared between klibc and init/initramfs.c in the kernel. Background of what I'm trying to do: I want to load an initramfs from flash on a number of different devices. The devices are quite similar but the partition in flash where the initramfs

I'm supporting a number of consumer devices (e.g. small NAS devices) in Debian. They typically don't export the serial console and don't have any other output devices. We perform the installation via SSH on such devices and start SSH automatically when the system boots so people can login. This works pretty well but sometimes a device stops to boot for no good reason. This is

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

We've seen the integer overflow problem in ks.test before, easily solved. The help page says x and y must be numeric, so this is user error. I've added tests to the code. Why do people file bug reports without reading the help/man page? On Tue, 14 Jan 2003 bates@stat.wisc.edu wrote: > This was filed as a bug report on the Debian r-base package. It is > more properly a bug

It might be a bit faster to do matrix indexing: R> tbm <- as.matrix(tb) # turn it into a character matrix R> tmat[cbind(match(tbm[,2], rownames(tmat)), match(tbm[,1], colnames(tmat)))] <- 1 > tmat Apple Orange Mango Grape Star A 1 1 1 0 0 O 1 1 0 0 0 M 0 0 1 0 0 G 0 0 0 0 0 S 1 1 1 0

Package: xen-3.0 Version: 3.0.2+hg9681-1 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 gcc-snapshot

Hi, On Thu, Jun 23, 2016 at 12:59 PM, Martin Michlmayr <tbm at cyrius.com> wrote: > 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