Re: Delete cris architecture?

[Dan Kegel <dank at kegel dot com>]

Hi Mikael,
Your message popped up again for some reason, so I tried
building crosstool-0.28-rc29 targeting cris with linux-2.6.7 / gcc-3.4.1 / glibc-2.2.5.
It failed with

../sysdeps/unix/sysv/linux/pread.c: In function `__libc_pread':
../sysdeps/unix/sysv/linux/pread.c:52: error: `__NR_pread' undeclared (first use in this function)
../sysdeps/unix/sysv/linux/pread.c:52: error: (Each undeclared identifier is reported only once
../sysdeps/unix/sysv/linux/pread.c:52: error: for each function it appears in.)

so I imagine some update is needed.  I'm no cris user,
though, so maybe I'll let someone else look into it...
- Dan

Mikael Starvik wrote:
> Hi!
>
> The CRIS architecture is very much alive and locally we are running 2.6.6.
> It is true that I haven't submitted any patches since 2.5.74 or 
> something like that. It is my intention to send in a patch asap,
> hopefully this week.
>
> I will submit 2.6 patches more often in the future. Later this year 
> we will also add support for a new CRIS subarchitecture.
>
> /Mikael (CRIS maintainer)
>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Sam Ravnborg
> Sent: Monday, May 31, 2004 8:42 PM
> To: Björn Wesén
> Cc: Dan Kegel; Mikael Starvik; linux-kernel@vger.kernel.org
> Subject: Re: Delete cris architecture?
>
>
> On Mon, May 31, 2004 at 06:14:02PM +0200, Bjorn Wesen wrote:
>
> > The CRIS architecture is stable and supported by Axis Communications 
> > officially in 2.4, but the 2.6 port is work-in-progress, thus you could 
> > expect problems building it from the vanilla kernel source. It works 
> > in-house on 2.6, but perhaps all patches have not trickled out to the 
> > official kernel yet (although they should have I think, so it's good that 
> > you mention stuff like this).
>
>
> When grepping the source and even doing cross architecture changes it is
> nice to have a ratehr up-to-date version in the main stream kernel.
>
> It would be nice if Axis could at least drop an update of the tree for
> each kernel release (provided there are any changes).
> This would allow all of us to get a better overview, and in some cases
> we may even introduce new stuff / fix errors.
>
> So please start to feed Andrew (or Linus) regularly with updates.
>
> 	Sam
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com