From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: explicitly pass --ranlib
Date: Fri, 17 Apr 2015 00:02:11 +0200 [thread overview]
Message-ID: <55303163.4090606@mind.be> (raw)
In-Reply-To: <XnsA47EE2C9972B5berndkuhlsPkbjNfxxIA@bernd-kuhls.de>
On 16/04/15 22:17, Bernd Kuhls wrote:
> "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
> wrote in news:1429214355-29429-1-git-send-email-arnout at mind.be:
>
>> + --ranlib=$(TARGET_RANLIB) \
>
> Hi,
>
> are you sure that your patch changes the behaviour of
> http://git.videolan.org/?
> p=ffmpeg.git;a=blob;f=configure;h=c11262a66c5ce8906f1a06bb54de3ab1e964dfb0;hb
> =HEAD#l2760
>
> when testing ranlib features?
> I am asking this because the configure options are stored into script
> variables in line 3019[1], whereas the ranlib test occurs in line 2760
> already.
It doesn't change the behaviour of the ranlib_default test, but since we pass
the ranlib invocation explicitly on the commandline the default is not used. And
I did check that it solves the autobuild error (which I could reproduce locally).
Regards,
Arnout
>
> Regards, Bernd
>
> [1] http://git.videolan.org/?
> p=ffmpeg.git;a=blob;f=configure;h=c11262a66c5ce8906f1a06bb54de3ab1e964dfb0;hb
> =HEAD#l3019
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
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
next prev parent reply other threads:[~2015-04-16 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 19:59 [Buildroot] [PATCH] ffmpeg: explicitly pass --ranlib Arnout Vandecappelle
2015-04-16 20:17 ` Bernd Kuhls
2015-04-16 22:02 ` Arnout Vandecappelle [this message]
2015-04-16 21:12 ` Yann E. MORIN
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=55303163.4090606@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox