All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wim <wim@hidof.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Kernel compilation error due to Adeos patch error in 'io_apic.c'
Date: Thu, 27 Dec 2012 20:35:31 +0100	[thread overview]
Message-ID: <50DCA303.7090303@xenomai.org> (raw)
In-Reply-To: <loom.20121227T200150-371@post.gmane.org>

On 12/27/2012 08:06 PM, Wim wrote:

>  
>> Vanilla Kernel: 3.2.21
>> Adeos Patch: ipipe-core-3.2.21-x86-1.patch
>> gcc --version: 4.7.0
>> Xenomai Version: 2.6.1
>>
>> Patch applies itself cleanly.
>>
>> Compilation error during initial kernel 'make':
>> arch/x86/kernel/apic/io_apic.c: In function
>> ‘irq_remap_modify_chip_defaults’:
>> arch/x86/kernel/apic/io_apic.c:2763:1: error: expected expression before
>> ‘}’ token
>>
>> Problem:
>> Commas instead of semi-colons at the end of lines inside CONFIG_IPIPE 'if'
>> directives in 'io_apic.c'.
> 
> 
> 
> Thanks Steve, this really helped!  
> 
> I can confirm that this problem still exists with yesterday's  
> stable Xenomai release 2.6.2, ipipe-core-3.2.21-x86-2.patch, a vanilla 3.2.21 
> kernel, ang gcc 4.6.3 on Ubuntu 12.04.


Ok, do you have the issue with I-pipe core 3.4 and 3.5 ?


-- 
                                                                Gilles.



  reply	other threads:[~2012-12-27 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 11:00 [Xenomai] Kernel compilation error due to Adeos patch error in 'io_apic.c' Stephen Bryant
2012-12-27 19:06 ` Wim
2012-12-27 19:35   ` Gilles Chanteperdrix [this message]
2012-12-27 20:15     ` Philippe Gerum
     [not found]     ` <CAAq7VdD_rrspRMqE8MVfLLnwPi+wOj87QedkdiSAto5YBG76Kw@mail.gmail.com>
2012-12-27 21:42       ` Gilles Chanteperdrix
2012-12-28 16:49         ` Jeff Webb
2012-12-28 18:32         ` Wim Meeussen

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=50DCA303.7090303@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=wim@hidof.com \
    --cc=xenomai@xenomai.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.