All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Solares <solca@guug.org>
To: sparclinux@vger.kernel.org
Subject: Re: SILO 1.4.2 released
Date: Thu, 29 Jan 2004 22:58:03 +0000	[thread overview]
Message-ID: <20040129225803.GD14503@guug.org> (raw)
In-Reply-To: <20040129182954.GK532@phunnypharm.org>

On Thu, Jan 29, 2004 at 04:01:03PM -0500, Ben Collins wrote:
> Read the fucking email. I want people to test the _old_ smaller kernels
> _first_. I would rather the larger kernels be broken than for the new
> SILO to not work with the older kernels.

Sorry, i think the point was test larger kernels.  Anyway
my older kernels boots properly with the new second.b. Newer
larger kernel 2.6.2-rc2-bk3 4M boots perfectly too on 3
different machines.

FYI compiling silo-1.4.3 from source:

gcc -m32 -Os -Wall -I. -I../include -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000 -DLARGE_RELOC=0x380000 -c fs/ufs.c -o fs/ufs.o
In file included from /usr/include/linux/fs.h:16,
                 from /usr/include/linux/ufs_fs.h:34,
                 from fs/ufs.c:36:
/usr/include/linux/list.h:594:2: warning: #warning "don't include kernel headers in userspace"
In file included from /usr/include/linux/fs.h:20,
                 from /usr/include/linux/ufs_fs.h:34,
                 from fs/ufs.c:36:
/usr/include/linux/radix-tree.h: In function `radix_tree_preload_end':
/usr/include/linux/radix-tree.h:54: error: invalid type argument of `->'
/usr/include/linux/radix-tree.h:54: error: `TIF_NEED_RESCHED' undeclared (first use in this function)
/usr/include/linux/radix-tree.h:54: error: (Each undeclared identifier is reported only once
/usr/include/linux/radix-tree.h:54: error: for each function it appears in.)
make: *** [fs/ufs.o] Error 1

-solca


  parent reply	other threads:[~2004-01-29 22:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
2004-01-29 20:13 ` Mustafa Hussein
2004-01-29 20:18 ` Ben Collins
2004-01-29 20:30 ` Ben Collins
2004-01-29 20:34 ` Otto Solares
2004-01-29 20:37 ` Ben Collins
2004-01-29 20:55 ` Otto Solares
2004-01-29 21:01 ` Ben Collins
2004-01-29 22:20 ` dree
2004-01-29 22:58 ` Otto Solares [this message]
2004-01-30  0:22 ` Erlend Aasland
2004-01-30 10:37 ` Christian
2004-01-30 17:04 ` Ben Collins
2004-01-30 17:37 ` Ben Collins
2004-01-30 17:39 ` Meelis Roos
2004-01-30 17:46 ` Meelis Roos
2004-01-30 17:48 ` Ben Collins
2004-01-30 18:19 ` Ben Collins
2004-01-30 18:20 ` Meelis Roos
2004-01-30 18:30 ` Meelis Roos
2004-01-30 18:40 ` Ben Collins
2004-01-30 18:49 ` Meelis Roos
2004-01-30 19:17 ` Meelis Roos
2004-01-30 19:21 ` Ben Collins
2004-01-30 19:30 ` Meelis Roos
2004-01-30 19:32 ` Ciaran McCreesh
2004-01-30 19:43 ` Ben Collins
2004-01-30 19:47 ` Meelis Roos
2004-01-30 19:52 ` Christian
2004-01-30 19:59 ` Meelis Roos
2004-01-30 20:06 ` Ben Collins
2004-01-30 20:19 ` Ben Collins
2004-01-30 20:35 ` Meelis Roos
2004-01-30 20:55 ` Ciaran McCreesh
2004-01-31  8:34 ` Ralph Mitchell
2004-01-31 13:14 ` Meelis Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040129225803.GD14503@guug.org \
    --to=solca@guug.org \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.