From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] faad2: fix broken build with binutils 2.22+
Date: Sun, 11 Dec 2011 17:46:18 +0100 [thread overview]
Message-ID: <20111211174618.109ec5a6@skate> (raw)
In-Reply-To: <1323617160-4360-3-git-send-email-gustavo@zacarias.com.ar>
Le Sun, 11 Dec 2011 12:25:58 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> +FAAD2_CONF_ENV = LIBS="-lm"
Instead of this, wouldn't it be better to carry a patch against the
package that makes the necessary modification ? I think a patch has
more chance to get removed appropriately when a new upstream version
that fixes the problem has been released.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-11 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 15:25 [Buildroot] [PATCH 1/5] squid: bump to version 3.1.18 Gustavo Zacarias
2011-12-11 15:25 ` [Buildroot] [PATCH 2/5] vsftpd: bump to version 2.3.4 Gustavo Zacarias
2011-12-11 21:54 ` Peter Korsgaard
2011-12-11 15:25 ` [Buildroot] [PATCH 3/5] faad2: fix broken build with binutils 2.22+ Gustavo Zacarias
2011-12-11 16:46 ` Thomas Petazzoni [this message]
2011-12-11 15:25 ` [Buildroot] [PATCH 4/5] wavpack: " Gustavo Zacarias
2011-12-11 15:26 ` [Buildroot] [PATCH 5/5] xf86-video-sis: bump to version 0.10.3 Gustavo Zacarias
2011-12-11 21:55 ` Peter Korsgaard
2011-12-11 21:53 ` [Buildroot] [PATCH 1/5] squid: bump to version 3.1.18 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=20111211174618.109ec5a6@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 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.