Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncftp: fix host/target confusion
Date: Wed, 1 Mar 2017 21:48:00 +0100	[thread overview]
Message-ID: <20170301214800.1a6c3405@free-electrons.com> (raw)
In-Reply-To: <1488322477-25447-1-git-send-email-thomas.petazzoni@free-electrons.com>

Hello,

On Tue, 28 Feb 2017 23:54:37 +0100, Thomas Petazzoni wrote:
> The ncftp build process tries to build and run a small program called
> ccdv to beautify the build process output. If it manages to build and
> run it, then it uses it.
> 
> Unfortunately, this doesn't work well when the target architecture is
> close to the host architecture, but not exactly the same. Because both
> architectures are close to each other, the test run of ccdv succeeds,
> but real use of ccdv during ncftp build process causes an Illegal
> instruction issue.
> 
> This for example happens with the CodeSourcery AMD64 toolchain, on a
> build machine running an i7-4600U, and has been detected in the
> autobuilders since the CodeSourcery AMD64 toolchain was upgraded at
> the end of January:
> 
>   http://autobuild.buildroot.net/?reason=ncftp-3.2.6
> 
> The issue was also reported by Christopher Arguin back in July 2016:
> 
>   http://lists.busybox.net/pipermail/buildroot/2016-July/168026.html
> 
> and at the time, we identified that simply disabling the ccdv tool, by
> passing --disable-ccdv, was enough to solve the issue. But Christopher
> never submitted the patch, so the problem remained unfixed.
> 
> Therefore, we pass --disable-ccdv to the configure script, which
> fixes:
> 
>   http://autobuild.buildroot.net/results/6eadad0e879ca70bb07b13b4196d42c64b11699f/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  package/ncftp/ncftp.mk | 1 +
>  1 file changed, 1 insertion(+)

Applied to master, thanks. Peter, I believe this one qualifies for the
LTS branch.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2017-03-01 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 22:54 [Buildroot] [PATCH] ncftp: fix host/target confusion Thomas Petazzoni
2017-03-01 20:13 ` Yann E. MORIN
2017-03-01 20:48 ` Thomas Petazzoni [this message]
2017-03-02 16:28   ` Peter Korsgaard
2017-03-02 19:07     ` Danomi Manchego
2017-03-02 20:43       ` Thomas Petazzoni
2017-03-03 20:50         ` Peter Korsgaard
2017-03-03 22:04           ` Arnout Vandecappelle
2017-03-03 22:08             ` Peter Korsgaard
2017-03-07 16:48           ` Peter Korsgaard
2017-03-07 20:10             ` Thomas Petazzoni
2017-03-07 21:10               ` Peter Korsgaard
2017-04-14 22:35                 ` Arnout Vandecappelle
2017-04-26  6:48                   ` Peter Korsgaard

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=20170301214800.1a6c3405@free-electrons.com \
    --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