From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Marcel Vornholt <Marcel.Vornholt@gmx.net>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai build for Raspberry Pi
Date: Wed, 27 Jan 2016 23:25:21 +0100 [thread overview]
Message-ID: <20160127222521.GD3685@hermes.click-hack.org> (raw)
In-Reply-To: <trinity-bd1a5d81-52a6-42b4-b2f3-5dcc1648aa1b-1453929363385@3capp-gmx-bs50>
On Wed, Jan 27, 2016 at 10:16:03PM +0100, Marcel Vornholt wrote:
> Hi,
> I have got a problem with the patch that Mathieu Rondonneau wrote two
> months ago.
> So first to the Situation and sorry for my bad english but I hope you
> can help me.
> I've got a RPI2 and want to build a kernel with xenomai. So I
> downloaded the "rpi-3.18.y" kernel, and xenomai 3.0.
> After a lot of time where i tryed to build the kernel without the Patch
> from Mathieu i was really desperated.
> So yesterday i found the patch and first thank you that some one had
> time for that ;)
> First I prepared the Cobal Kernel with the
> ipipe-core-3.18.20-arm-6.patch
> But when I try to use the patch i get the error:
> ~/Rasp/linux-rpi-3.18.y $ patch -p1 <
> rpi-ipipe-core-3.18-arm-1.patch
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file arch/arm/Kconfig
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file arch/arm/mach-bcm2709/armctrl.c
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file arch/arm/mach-bcm2709/bcm2708_gpio.c
> Hunk #3 succeeded at 295 with fuzz 2 (offset -1 lines).
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file arch/arm/mach-bcm2709/bcm2709.c
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file arch/arm/mach-bcm2709/include/mach/entry-macro.S
> patch unexpectedly ends in middle of line
>
> So what can I do against it?
> Or was it wrong that I prepared the Cobalt Kernel first?
>
> I hope that I used the mailing list right and have a nice evening
As the error messages say, your patch is borked, doubly so even:
- it probably has been downloaded with a machine which added ms-dos
line breaks;
- additional line breaks have probably been added by whatever
software you used to retrieve the patch.
The only fix is to get a proper patch.
--
Gilles.
https://click-hack.org
prev parent reply other threads:[~2016-01-27 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 1:10 [Xenomai] Xenomai build for Raspberry Pi Elmar Grom
2016-01-25 15:16 ` Nicolas SCHURANDO
2016-01-25 15:29 ` Gilles Chanteperdrix
2016-01-25 15:30 ` Elmar Grom
2016-01-27 21:16 ` Marcel Vornholt
2016-01-27 22:25 ` Gilles Chanteperdrix [this message]
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=20160127222521.GD3685@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Marcel.Vornholt@gmx.net \
--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.