From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] ncftp: fix cross-compilation test
Date: Wed, 19 Feb 2014 13:10:44 +0100 (CET) [thread overview]
Message-ID: <1036423664.6634177.1392811844408.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20140219002849.1afd4436@skate>
Hi Thomas,
----- Mail original -----
| De: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
| ?: "Romain Naour" <romain.naour@openwide.fr>
| Cc: buildroot at busybox.net
| Envoy?: Mercredi 19 F?vrier 2014 00:28:49
| Objet: Re: [Buildroot] [PATCH v2 1/1] ncftp: fix cross-compilation test
|
| Dear Romain Naour,
|
| On Wed, 19 Feb 2014 00:18:42 +0100, Romain Naour wrote:
|
| > Ok, it works.
| > The configure script is regenerated correctly.
|
| Cool. Does it fix the original problem? I only quickly looked at the
| generated configure script to verify that the cross compiling test is
| correct, but I did not verify that the original problem was really
| solved.
This is what I meant by "it works".
I tested in a Debian chroot where ncurses is not installed.
So, the original problem is solved :)
|
| > I had problems using NCFTP_AUTORECONF = YES
| > what is the difference?
|
| ncftp is not fully autotools based: it uses autoconf, but not
| automake.
| And the autoconf invocation needs a special -I path to find the
| aclocal.m4, since it cannot be re-generated using aclocal, because it
| uses some funky m4 macros and I have no idea where are the original
| m4
| files with these macros.
Thanks for your explanations,
I am not yet familiar with autotools but I progress :)
Best regards,
Romain
prev parent reply other threads:[~2014-02-19 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 22:31 [Buildroot] [PATCH v2 1/1] ncftp: fix cross-compilation test Romain Naour
2014-02-18 22:59 ` Thomas Petazzoni
2014-02-18 23:18 ` Romain Naour
2014-02-18 23:28 ` Thomas Petazzoni
2014-02-19 12:10 ` Romain Naour [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=1036423664.6634177.1392811844408.JavaMail.root@openwide.fr \
--to=romain.naour@openwide.fr \
--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