Hello Sebastian,

I'll look into & study your commit.

I typically maintain two local repos, one forked from github rtems, in which I 
do most of my work. And the other pulled from git.rtems.org, that remains 
intact.

I'm getting this percpu.h error in the latest git master updated from rtems.org 
site. Please have a look.


Regards
Vipul Nayyar 



________________________________
 From: Sebastian Huber <[email protected]>
To: Vipul Nayyar <[email protected]> 
Cc: Joel Sherrill <[email protected]>; Cynthia Rempel 
<[email protected]>; "[email protected]" <[email protected]> 
Sent: Thursday, 8 August 2013 11:44 AM
Subject: Re: Updating legacy code in arm nds
 

Hello Vipul,

for a conversion example please have a look at

http://git.rtems.org/rtems/commit/?id=f4dc319a8f92190c6efac916fb8b9b651d89df7c

read also the comments in "irq-generic.h".

On 2013-08-06 19:34, Vipul Nayyar wrote:
>
>   Hello,
>
> As suggested, I studied the working of interrupt controller. So, I've made
> implementations of install & remove methods from libnds to change to Interrupt
> API. This is a small patch for arm nds. Just checking if going in the right
> direction.
>
> Fair warning: the compilation of arm nds gives an error, but not due to my
> changes.  The error given is :
>
> ../../../../cpukit/../../../nds/lib/include/rtems/score/percpu.h:25:34: fatal
> error: rtems/score/assert.h: No such file or directory
>     #include <rtems/score/assert.h>
>                                    ^
> compilation terminated.

Do you get this error with the latest Git master?

>
> I'll be happy to fix this error, that's already present in the rtems tree. The
> path to assert.h seems to be fine. Need guidance.
>
>
> Regards
> Vipul Nayyar
>


-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : [email protected]
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
[email protected]
http://www.rtems.org/mailman/listinfo/rtems-devel

Reply via email to