From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] pptp-linux: bump to version 1.8.0
Date: Fri, 4 Apr 2014 23:50:55 +0200 [thread overview]
Message-ID: <20140404235055.39b4ce52@skate> (raw)
In-Reply-To: <1396300329-12942-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 31 Mar 2014 18:12:09 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> .../pptp-linux/pptp-linux-001-susv3-legacy.patch | 43 +++++++++++----------
> .../pptp-linux/pptp-linux-002-drop-stropts.patch | 26 -------------
> ...tch => pptp-linux-002-fix-parallel-build.patch} | 0
> package/pptp-linux/pptp-linux-003-ip-path.patch | 44 ----------------------
> package/pptp-linux/pptp-linux.mk | 5 ++-
> 5 files changed, 27 insertions(+), 91 deletions(-)
> delete mode 100644 package/pptp-linux/pptp-linux-002-drop-stropts.patch
> rename package/pptp-linux/{pptp-linux-004-fix-parallel-build.patch => pptp-linux-002-fix-parallel-build.patch} (100%)
> delete mode 100644 package/pptp-linux/pptp-linux-003-ip-path.patch
Seems to break the build on ARM:
http://autobuild.buildroot.org/results/5bd/5bdfcf544a83e18d12e27c598084c0ad520d6164/build-end.log
{standard input}: Assembler messages:
{standard input}:225: Error: bad instruction `rorw $8,'
{standard input}:225: Error: bad instruction `rorl $16,r2'
{standard input}:225: Error: bad instruction `rorw $8,'
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-04 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 21:12 [Buildroot] [PATCHv2] pptp-linux: bump to version 1.8.0 Gustavo Zacarias
2014-04-03 18:20 ` Thomas Petazzoni
2014-04-04 21:50 ` Thomas Petazzoni [this message]
2014-04-04 22:40 ` Gustavo Zacarias
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=20140404235055.39b4ce52@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox