similar to: build failure with linux-2.6.0-test7

Displaying 20 results from an estimated 2000 matches similar to: "build failure with linux-2.6.0-test7"

2005 Jan 19
1
build klibc with gcc 2.96 fails
I get the following error: make[1]: Entering directory `/home/greg/src/klibc/klibc-0.196/klibc' gcc -Wp,-MT,__static_init.o,-MD,./.__static_init.o.d -march=i386 -Os -g -malign-functions=0 -malign-jumps=0 -malign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I.. /include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -I ../linux/include
2003 Jul 31
3
Trying to test with 2.6.0-test2
Hi folks, I haven't tested initramfs with klibc before and am having trouble getting going. I tried to pull from the klibc-2.5 bk repository but it doesn't merge with 2.6t2. Also i downloaded the .80 version and tried to compile but got a stream of errors and warnings. It looks like it needs to be compiled from within the kernel tree but i couldn't find any docs about the
2003 Oct 13
5
initramfs as an initrd replacement
Hi , One of the things I am working on requires me to have a kernel and an initrd (as root filesystem , based on busybox) in one single image. I am trying to use initramfs for this, but there are a few things that I just can't figure out. As a test, I made a cpio archive of my own for the kernel source (plain 2.6.0-test5). Everything gets unpacked just fine during boot. Somehow I was
2003 Oct 15
2
link failure in snapshot 0.81
Im using snapshot 0.81. make[1]: Entering directory `/home/rogelio/src/klibc-0.81/klibc' gcc -Wp,-MD,./.getenvtest.d -march=i386 -Os -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -I../klibc -I../klibc/arch/i386/include -I../klibc/include/bits32 -D__KLIBC__ -DBITSIZE=32 -I../klibc/include -I../linux/include -W -Wall -Wpointer-arith -Wwrite-strings
2002 Aug 24
1
klibc 0.57 trouble
Hi, I just tried compiling the latest release, but found some new problems: - Some versions of binutils could not link any shared binaries. One example for a broken version is 2.11.92.0.12.3, while 2.13.90.0.4 works. The error message looks like: tests/nfs_no_rpc.o: In function `root_nfs_parse': tests/nfs_no_rpc.o(.text+0x8): undefined reference to `strchr'
2002 Jun 03
1
build fails dumping R code in 'methods' on i686-pc-linux-gnu (PR#1630)
Using the same settings in config.site as were used for R-1.4.1, R-1.5.0 fails to build. ./configure --enable-R-shlib Using defaults and using PPro optimizations, the build failed in package methods: dumping R code in package 'methods' gmake[4]: *** [../../../library/methods/R/all.rda] Error 139 gmake[4]: Leaving directory `/mnt/Data/src/install/R-1.5.0/src/library/methods' The
2004 May 11
1
Problem building 1.0-test7 : missing header
Greetings, I recently rolled out Dovecot in our small (<30 people) company, and have been mightily impressed by the quality, performance and ease of use. I was hoping to use the new versions soon, as I'd like to start using CRAM-MD5 (much more common in mail clients than DIGEST-MD5), but found the 0.99.11 versions too unstable. So, I tried to build last nights CVS snapshot (May
2003 Sep 04
1
still getting weird .{inbox} folder creations with latest -test7
Hi, I am still getting strange creation and mailbox lookups from 0.99.11-test7. dovecot creates in ~/Maildir/ .INBOX/ .imap.index .imap.index.cache .imap.index.log .customflags dovecot-uidlist .INBOX seems to be a reference to ~/Maildir/{cur,new,tmp} yet I
2003 Oct 28
1
EXT3-fs error on 2.6.0-test7-bk4 (and -test9)
ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal
2002 Jul 18
1
debian potato cvs wine segfaults on compile
Hi, I'm trying to compile Wine cvs on this system: debian potato libc6 2.1.3 gcc 2.95.3 (upgraded) binutils 2.12.2 (upgraded) X 4.2 (upgraded) Nvidia drivers from Nvidias website (libGL 1.3) I get the following errors, I've tryied to compile this several times with tools/wineinstall and also 'configure && make depend && make', with and without these CLFAGS
2007 Sep 11
2
Bug#441249: Bug#441249: xen-hypervisor-3.0.3-1-i386-pae: "Problems using XEN when Quagga is running"
Hi, > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? Toying with the vif-route script, I might have found a workaround for this issue. If I disable the ifconfig and ip route commands from vif-route script, and bring up vif interface by hand later on, everything seems to work. In other works,
2018 Dec 13
2
[PATCH] kbuild, x86: revert macros in extended asm workarounds
Revert the following commits: - 5bdcd510c2ac9efaf55c4cbd8d46421d8e2320cd ("x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs") - d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2 ("x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs") - 0474d5d9d2f7f3b11262f7bf87d0e7314ead9200. ("x86/extable: Macrofy inline assembly
2018 Dec 13
2
[PATCH] kbuild, x86: revert macros in extended asm workarounds
Revert the following commits: - 5bdcd510c2ac9efaf55c4cbd8d46421d8e2320cd ("x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs") - d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2 ("x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs") - 0474d5d9d2f7f3b11262f7bf87d0e7314ead9200. ("x86/extable: Macrofy inline assembly
2007 Apr 25
2
[LLVMdev] Work in progress patch to speed up andersen's implementation
Hi guys, i'm not going to have time to work on this for a month or two, so i figured i'd post it. This patch 1. reworks the andersen's implementation to support field sensitivity (though field-sensitive constraints are not generated directly yet), and uses it to do indirect function call support. 2. Rewrites the solver to be state of the art in terms of speed. kimwitu++ used to take
2003 Feb 20
1
0.99.8-test7
OK, I really should release 0.99.8 final soon, but not just yet :) Mostly just documentation updates left I think. There's a few recent changes that might have some nasty bugs: - problems with copying messages from mbox to another should be fixed now - LIST and subscription handling rewritten. - "mail_read_mmaped = no" used to corrupt mboxes when expunging messages. It now enabled
2003 May 28
0
0.99.10-test7
- APPEND memory leak fixed - maildir syncing crash / some other errors fixed - pop3 mail fetching fixed - pop3 didn't advertise STLS in capabilities before http://dovecot.procontrol.fi/test/
2003 Oct 04
1
mbox/maildir/directories [was: Re: still getting weird .{inbox} folder creations with latest -test7]
This is a bit of a late reply, but still: On Thu, 2003-09-04 at 15:06, Timo Sirainen wrote: > CVS has been optimized to assume all files beginning with a dot (except > .subscriptions currently) are mailboxes. This is faster since it doesn't > have to stat() each file to figure out if it's a directory or not. > Perhaps that should be optional. New Linux systems (maybe others
2016 Sep 14
2
com.jcraft.jsch.JSchException: Auth fail
Hi, I've come across some messages from sshd (OpenSSH 6.7) in my auth.log that I hadn't noticed before: sshd[32008]: error: Received disconnect from x.x.x.x: 3: \ com.jcraft.jsch.JSchException: Auth fail [preauth] I was kinda puzzled why sshd would emit some JCraft[0] messages and the best explanation I found was this Serverfault[1] answer, quoting a snippet from packet.c:1965
2004 May 10
2
1.0-test7
http://dovecot.org/test/ Lots of bugfixes related to syncing. There's still some left. Somewhat working mbox support: - combined syncing/rewriting uses much less disk I/O than with older mbox code - expunges aren't working yet - last-uid field in X-IMAPbase header isn't updated - it's currently syncing the whole mbox constantly even if it hasn't changed - it
2002 Jun 04
0
build fails dumping R code in 'methods' on i686-pc-linux-gnu (PR#1632)
aa056@chebucto.ca wrote: > > Using the same settings in config.site as were used for R-1.4.1, > R-1.5.0 fails to build. > > ./configure --enable-R-shlib > > Using defaults and using PPro optimizations, the build failed in > package methods: > > dumping R code in package 'methods' > gmake[4]: *** [../../../library/methods/R/all.rda] Error 139 >