All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] ncftp: fix cross-compilation test
Date: Wed, 26 Feb 2014 22:23:25 +0100	[thread overview]
Message-ID: <530E5B4D.3090205@mind.be> (raw)
In-Reply-To: <530E56FC.20608@openwide.fr>

On 26/02/14 22:05, Romain Naour wrote:
> I wonder if any other packages can be affected by this issue ?
> At least we know that autoconf 2.13 is not safe for cross-compilation...

 The first autoconf version after 2.13 is 2.50, and this solves the
cross-compilation issue (see release notes). 2.50 was released on May 21,
2001. Seems unlikely that there are many packages that are distributed
with such an ancient autoconf...

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2014-02-26 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 21:00 [Buildroot] [PATCH v3 1/1] ncftp: fix cross-compilation test Romain Naour
2014-02-21 22:57 ` Thomas Petazzoni
2014-02-21 23:41 ` Peter Korsgaard
2014-02-23 22:23 ` Arnout Vandecappelle
2014-02-23 22:52   ` Romain Naour
2014-02-25 17:13     ` Arnout Vandecappelle
2014-02-26 21:05       ` Romain Naour
2014-02-26 21:23         ` Arnout Vandecappelle [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=530E5B4D.3090205@mind.be \
    --to=arnout@mind.be \
    --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 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.