buildroot/package/avrdude, branch 2016.02

package/elfutils: fix dependency on C library

2015-08-09T09:22:08+00:00

As Thomas puts it: The comment can only be visible when a toolchain that is *not* uclibc and *not* glibc is used. I.e, the comment is now only visible when musl is used. Which is not what we want. Indeed, I completely borked the conditions. When a glibc or uClibc toolchain is selected, the comment is entirely hidden, and we don;t get the extra requirements (wchar, !static). Fix that with the solution proposed by Thomas. Reported-by: Thomas Petazzoni Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/elfutils: does not build with musl

2015-08-08T08:56:11+00:00

elfutils uses so many GNUisms in so many places that patching them out is a tedious task which would make us diverge so much from upstream that it would become a nightmare to bump elfutils in the future. Furthermore, elfutils needs argp, which is missing in musl, so it would need argp-standalone too (as when using a uClibc toolchain). Make elfutils depend on either glibc or uClibc. argp-standalone is already required when using a uClibc toolchain, but since we do not support musl, no need to add that to the condition. Fixes (configure failures due to missing argp): http://autobuild.buildroot.org/results/743/7432ccd0d060a70bc35f0ac21ec92ae0071592ae/ http://autobuild.buildroot.org/results/cc9/cc90bd9312f30f91daa50af4253629f58b82c486/ http://autobuild.buildroot.org/results/d5e/d5e583c695afbc2e686e3002765ce9e1937aa0d5/ [...] Fixes (build failures due to GNUisms): http://autobuild.buildroot.org/results/ee7/ee7eaf80247dd96548d66be9884b179e20204a98/ http://autobuild.buildroot.org/results/3f2/3f242853e600bb6bec6ce2f0598d304751ceb81a/ http://autobuild.buildroot.org/results/7f0/7f0c7c9cb746104f93907544247bc1008d6ad0dc/ [...] Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

packages: remove (non-)lfs dependencies and tweaks

2015-04-01T20:47:22+00:00

Now that largefile is mandatory removes package dependencies and conditionals. Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

package/avrdude: optionally depends on libftdi or libftdi1

2015-03-20T22:29:49+00:00

Avrdude supports both libftdi and libftdi1. Because libftdi is already an optional dependency, this patch adds libftdi1 as optional dependency as well, but privileges libftdi1 over libftdi (accdording to what is done in avrdude's configure script). Signed-off-by: Samuel Martin Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

packages: all salute the passing of avr32

2015-02-14T16:43:11+00:00

Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS

2014-12-11T21:48:13+00:00

Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN"

elfutils: disable for static builds

2014-11-07T07:55:34+00:00

Even when doing static builds, a shared library is built. This causes a build failure under some circumstances, for instance when building for MIPS + uClibc + static. After asking upstream if it would be possible to add a configure option to not build the shared library, the answer was that doing a static build is not a good idea. Here is a small snippet of the conversation: "Note that fully static builds are problematic. elfutils uses dlopen to open the EBL backends (the CPU-specific support snippets), so even if you link statically, the final binaries are still considerably dynamic." Related: https://lists.fedorahosted.org/pipermail/elfutils-devel/2014-November/004223.html Fixes: http://autobuild.buildroot.net/results/691/6913f5af6519463fbed39ef37b6a40ecf6a67b54/ Signed-off-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

avrdude: Depend on elfutils instead of libelf to get the libelf library

2014-09-13T22:00:59+00:00

The elfutils package provides a more recent version of the libelf, so let's use it. It will allow to remove the libelf package and to avoid conflicts with two packages providing the same library. [Peter: adjust toolchain options comment to match] Signed-off-by: Gregory CLEMENT Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

avrdude: add license information

2014-06-26T21:03:13+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

package: remove the empty trailing line(s)

2014-01-04T09:39:29+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard