[Xenomai-core] [PATCH forge] Fix build for relative invocations of configure

[Xenomai-core] [PATCH forge] Fix build for relative invocations of configure

[Jan Kiszka]

This fixes build setups like '../configure'.

Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
---
 configure.in |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/configure.in b/configure.in
index c0a7d17..0bdced8 100644
--- a/configure.in
+++ b/configure.in
@@ -547,7 +547,7 @@ LD_FILE_OPTION=$ac_cv_ld_file_option
 AC_SUBST(LD_FILE_OPTION)
 
 if test x$rtcore_type = xcobalt; then
-   XENO_USER_CFLAGS="-I$srcdir/include/cobalt $XENO_USER_CFLAGS"
+   XENO_USER_CFLAGS="-I`cd $srcdir && pwd`/include/cobalt $XENO_USER_CFLAGS"
    if [[ $ac_cv_ld_file_option = yes ]]; then
 	XENO_POSIX_WRAPPERS="-Wl,@`cd $srcdir && pwd`/lib/cobalt/posix.wrappers"
    else
-- 
1.7.3.4

Re: [Xenomai-core] [PATCH forge] Fix build for relative invocations of configure

[Philippe Gerum]

On 02/07/2012 04:43 PM, Jan Kiszka wrote:
> This fixes build setups like '../configure'.
>

Merged, thanks.

> Signed-off-by: Jan Kiszka<jan.kiszka@domain.hid>
> ---
>   configure.in |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure.in b/configure.in
> index c0a7d17..0bdced8 100644
> --- a/configure.in
> +++ b/configure.in
> @@ -547,7 +547,7 @@ LD_FILE_OPTION=$ac_cv_ld_file_option
>   AC_SUBST(LD_FILE_OPTION)
>
>   if test x$rtcore_type = xcobalt; then
> -   XENO_USER_CFLAGS="-I$srcdir/include/cobalt $XENO_USER_CFLAGS"
> +   XENO_USER_CFLAGS="-I`cd $srcdir&&  pwd`/include/cobalt $XENO_USER_CFLAGS"
>      if [[ $ac_cv_ld_file_option = yes ]]; then
>   	XENO_POSIX_WRAPPERS="-Wl,@`cd $srcdir&&  pwd`/lib/cobalt/posix.wrappers"
>      else


-- 
Philippe.

[Xenomai-core] high duration of __ipipe_handle_irq

[Roberto Bielli]

[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]

Hi,

i have this problem with xenomai ( 2.5.6 - arm freescale imx25 ):

I have a xenomai application that uses more rt_tasks, and i have a 
strange behaviour.
When i run my application the period of *__ipipe_handle_irq* is very 
long ( ~3ms in some cases ) in the moment
that come the *__ipipe_mach_timerint *interrupt and so the other 
interrupts are very late.

Do you know something about this ?

Thanks for all


-- 
+------------------------------------------------------------------------------------------------+
							
Roberto Bielli
Sviluppo Software					
Axel S.r.l.					
							
Via Del Cannino, 3 				
21020 Crosio Della Valle			
Varese - Italy					
							
Telefono: +39 0332 949600			
Fax:      +39 0332 969315			
							
E-mail:   roberto.bielli@domain.hid	
Web Site: www.axelsw.it

+------------------------------------------------------------------------------------------------+

Si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario.
Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie.
Informativa sul trattamento dei dati personali (D. Lgs. 196/2003).
I dati utilizzati per la spedizione del presente messaggio sono utilizzati da Axel S.r.l., titolare del trattamento,
per l'invio delle comunicazioni dei diversi settori aziendali, non essendo autorizzata la divulgazione a terzi.
Potrete rivolgere alla seguente mail richieste di verifica, rettifica o cancellazione dei Vostri dati: info@domain.hid

This e-mail and any attachments is confidential and may contain privileged information
intended for the addressee(s) only. Dissemination, copying, printing or use by anybody
else is unauthorised. If you are not the intended recipient,
please delete this message and any attachments and advise the sender
by return e-mail.Thank you.  			
							
+------------------------------------------------------------------------------------------------+


[-- Attachment #2: Type: text/html, Size: 2624 bytes --]

Re: [Xenomai-core] high duration of __ipipe_handle_irq

[Gilles Chanteperdrix]

On 03/01/2012 07:03 PM, Roberto Bielli wrote:
> Hi,
> 
> i have this problem with xenomai ( 2.5.6 - arm freescale imx25 ):
> 
> I have a xenomai application that uses more rt_tasks, and i have a 
> strange behaviour.
> When i run my application the period of *__ipipe_handle_irq* is very 
> long ( ~3ms in some cases ) in the moment
> that come the *__ipipe_mach_timerint *interrupt and so the other 
> interrupts are very late.
> 
> Do you know something about this ?

I am sorry, but I do not understand your mail. __ipiep_handle_irq is not
periodic and this sentence:

When i run my application the period of *__ipipe_handle_irq* is very
long ( ~3ms in some cases ) in the moment
that come the *__ipipe_mach_timerint *interrupt and so the other

is not understandable.

Please try to describe your problem more clearly, or better, use the
I-pipe tracer and record a trace of the problem, and post the relevant
part of the trace here.

-- 
					    Gilles.