* [Buildroot] buildroot 2012.11 large file support
From: Arnout Vandecappelle @ 2012-12-12 23:47 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121212232108.261e4b29@skate>
On 12/12/12 23:21, Thomas Petazzoni wrote:
> Dear Peter Korsgaard,
>
> On Wed, 12 Dec 2012 21:15:44 +0100, Peter Korsgaard wrote:
>
>> Thomas> !largefile build is OK if we pass $(DISABLE_LARGEFILE) to
>> Thomas> gcc1 and gcc2 configure steps, so it solves the build
>> Thomas> problem. I haven't done more testing though (testing the
>> Thomas> generated code, building with largefile enabled, etc.).
>>
>> Cool, great - I'll commit that then.
>>
>> Thomas> That said, doesn't --disable-largefile disables largefile
>> Thomas> support at the level of gcc itself, rather than taking into
>> Thomas> account the fact that largefile support is not available on
>> Thomas> the target? Of course, it has the consequence that
>> Thomas> _FILE_OFFSET_BITS is no longer defined to 64 in auto-conf.h,
>> Thomas> which works around the problem. But gcc (the host binary)
>> Thomas> should be capable of being built with largefile support on a
>> Thomas> 32 bits host, even if the 32 bits target has no largefile
>> Thomas> support.
>>
>> So for the cross compiler to be able to access large files? Is that
>> really important? I doubt people are using buildroot with 2G+
>> source/object/library files?
>
> It's not that we care too much about this (even though some crazy
> library like Qt with debugging symbols reaches a very fat size, several
> hundreds of MBs in size), but the fact that it is an ugly workaround to
> use the side-effect of disabling largefile on gcc to make it play nice
> with a target system that has largefile disabled.
>
> Right now, when largefile is disabled for the target, it is disabled
> for the cross gcc, when largefile is enabled for the target, it is
> enabled for the cross gcc. Doesn't make much sense.
Indeed, it would make much more sense to disable largefile unconditionally
while building any gcc stage (uClibc won't complain if _FILE_OFFSET_BITS is
not set). At least, I guess --disable-largefile only says something about
the gcc executable, not about the crtstuff and other target support...
And it also deserves a BIG FAT comment explaining why this is needed.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
^ permalink raw reply
* [Buildroot] Random "Bus error" when building host-python
From: Thomas Petazzoni @ 2012-12-12 22:54 UTC (permalink / raw)
To: buildroot
Hello,
If you have looked at the autobuilder results recently, there are some
host-python errors sometimes:
http://autobuild.buildroot.org/results/b01a3c7233d53578961b74fb6ffb006782a43944/build-end.log
Free Electrons build server, targeting mipsel
http://autobuild.buildroot.org/results/5c59266f72f234ee9863e3d54270487b05af3612/build-end.log
gcc14 build server, targeting powerpc
http://autobuild.buildroot.org/results/3cf01dabafd47813c6fe11d0250e57ef667e8d95/build-end.log
gcc14 build server, targeting powerpc
http://autobuild.buildroot.org/results/7722a16700231a49b736fae697532013dfccfd2a/build-end.log
Free Electrons build server, targeting arm
Every time, the build fail with a "Bus error". The log is not clear
enough to really understand what process is failing with a Bus error.
As you can see, the problem is not specific to one build machine, or
one target architecture (well, since it's in host package, it's kind of
obvious, but not the build machine fact).
And the thing is that those problems are not reproducible. If you take
the exact same commit ID of Buildroot, the exact same configuration, on
the exact same build machine, the problem may or may not produce
itself. I tried to reproduce it using one of those build
configurations, and he wasn't produced.
On the other hand, I did try to reproduce some other build
configuration that failed in the autobuilders, and instead of having
the error reported by the autobuilder web interface, I felt into the
"Bus error" problem in host-python. I just restarted the build (not
from scratch, simply restarted the build), and it went on without
failing into the "Bus error" problem. So it seems like the problem is
not in the generated code (re-executing the same code sometimes work
sometimes doesn't work).
Does anyone has ideas on how to further investigate this?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply
* [Buildroot] Creating/installing images
From: Thomas Petazzoni @ 2012-12-12 22:33 UTC (permalink / raw)
To: buildroot
In-Reply-To: <CAKvQZ_37DWZxZZi5yUS3im0cdHCsDfAXKg=GChc-V8NHj6mCJQ@mail.gmail.com>
Dear Willy Lambert,
On Wed, 12 Dec 2012 22:28:10 +0100, Willy Lambert wrote:
> I was using for my embedded system a standard debian + a set of
> apt-get to get a customized OS on a 2GB on board persistent memory (so
> I have a working system, as kernel config for instance). But now I
> decided to dive into the wonderfull world of "linux from scratch" with
> the great help of busybox in order to :
> _ know exactly what's on my board
> _ reduce persistent size
> _ stop doing overkill with a 2GB system that can fit in 32Mb
>
> So I have setup busybox and spent some days into documentation and
> sandbox, but I'm stuck with the target image installation. The
> documentation stops at this point and I'm alone in the dark. I spent 2
> days in searching docs on the internet without great success.
>
> I have a successful qemu working to test the buildroot output, cause I
> don't need bootloader or proper image, just giving bzImage and
> rootfs.ext2 is enougth.
>
> But as to create something that my embedded system can boot on .... I
> really don't know what and how to do. So I would be glad if anyone
> could help me, at least in giving links or keyword for documentation.
>
> My target has an onboard flash memory. World would have been simplier
> if I could have a removable "root" memory but it's not the case. So If
> I'm correct I need to boot my target (either with an external boot
> device like usb key, or with the existing linux installed on it) and
> then replace the rootfs. What would you do in this case (knowing that
> it will happen often in the dev cycle) ?
> _ use a ram pivot_root from the current linux?
> _ use a dd from an external usb key boot ?
> _ re-partition all this to have a little 10Mb part for a "Tool OS"
> that can be used for rootfs installation ?
> _ do somethig else ?
> _ take a beer and think more ?
I would use the capacity of your board to boot over the network. Since
it is a x86 platform with a BIOS, I guess it is capable of doing PXE.
So during development, I would load the kernel using PXE, and then
mount the root filesystem over NFS.
Then, to flash the devices before they go in production in the field, I
would create a minimal Linux system, that you boot over the network
using PXE, and this Linux system downloads and flash the real Linux
system in the internal Flash of your system (which apparently is
accessed as a normal ATA hard drive). You make sure this minimal Linux
system makes all this process automatically when it is booted, so
whenever you boot one of your system on a network that has your
PXE/TFTP server on it, it will be erased and reflashed (of course, be
careful not to boot a real laptop or desktop system in the same network
segment, or it might boot over the network and get erased).
Does this helps?
For a simple PXE/TFTP server solution, I would strongly suggest using
ptftpd/pxed: <https://ssl.bulix.org/svn/ptftpd/trunk/>. It is very
simple to setup (just *one* command to have a complete PXE solution
running).
> For completness here is my board datasheet, but I don't expect anyone
> to read :-). It's an Advantech PCM-3362
> http://support.elmark.com.pl/advantech/pdf/pcm-3362man.pdf
I actually read it, and verified that your board is capable of booting
over the network, and it apparently is.
> Is it possible to use other filesystems, like ext3 or 4 ?
Yes, you just need to do some tuning of your ext2 image using tune2fs.
I really should submit a patch to add support for ext3 and ext4 image
generation in Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply
* [Buildroot] buildroot 2012.11 large file support
From: Thomas Petazzoni @ 2012-12-12 22:21 UTC (permalink / raw)
To: buildroot
In-Reply-To: <87r4mvm3gv.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 12 Dec 2012 21:15:44 +0100, Peter Korsgaard wrote:
> Thomas> !largefile build is OK if we pass $(DISABLE_LARGEFILE) to
> Thomas> gcc1 and gcc2 configure steps, so it solves the build
> Thomas> problem. I haven't done more testing though (testing the
> Thomas> generated code, building with largefile enabled, etc.).
>
> Cool, great - I'll commit that then.
>
> Thomas> That said, doesn't --disable-largefile disables largefile
> Thomas> support at the level of gcc itself, rather than taking into
> Thomas> account the fact that largefile support is not available on
> Thomas> the target? Of course, it has the consequence that
> Thomas> _FILE_OFFSET_BITS is no longer defined to 64 in auto-conf.h,
> Thomas> which works around the problem. But gcc (the host binary)
> Thomas> should be capable of being built with largefile support on a
> Thomas> 32 bits host, even if the 32 bits target has no largefile
> Thomas> support.
>
> So for the cross compiler to be able to access large files? Is that
> really important? I doubt people are using buildroot with 2G+
> source/object/library files?
It's not that we care too much about this (even though some crazy
library like Qt with debugging symbols reaches a very fat size, several
hundreds of MBs in size), but the fact that it is an ugly workaround to
use the side-effect of disabling largefile on gcc to make it play nice
with a target system that has largefile disabled.
Right now, when largefile is disabled for the target, it is disabled
for the cross gcc, when largefile is enabled for the target, it is
enabled for the cross gcc. Doesn't make much sense.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply
* [Buildroot] [PATCH] Add package for mongoose web server
From: Charles Manning @ 2012-12-12 22:03 UTC (permalink / raw)
To: buildroot
Signed-off-by: Charles Manning <cdhmanning@gmail.com>
---
package/Config.in | 1 +
package/mongoose/Config.in | 13 ++++++
package/mongoose/mongoose-3.3-init-file.patch | 44 ++++++++++++++++++++
package/mongoose/mongoose-3.3-no-auth.patch | 55 +++++++++++++++++++++++++
package/mongoose/mongoose.mk | 38 +++++++++++++++++
5 files changed, 151 insertions(+), 0 deletions(-)
create mode 100644 package/mongoose/Config.in
create mode 100644 package/mongoose/mongoose-3.3-init-file.patch
create mode 100644 package/mongoose/mongoose-3.3-no-auth.patch
create mode 100644 package/mongoose/mongoose.mk
diff --git a/package/Config.in b/package/Config.in
index 5ba1f05..a3d2590 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -603,6 +603,7 @@ source "package/linphone/Config.in"
source "package/lrzsz/Config.in"
source "package/macchanger/Config.in"
source "package/mii-diag/Config.in"
+source "package/mongoose/Config.in"
source "package/mrouted/Config.in"
source "package/msmtp/Config.in"
source "package/mutt/Config.in"
diff --git a/package/mongoose/Config.in b/package/mongoose/Config.in
new file mode 100644
index 0000000..39806f9
--- /dev/null
+++ b/package/mongoose/Config.in
@@ -0,0 +1,13 @@
+config BR2_PACKAGE_MONGOOSE
+ bool "mongoose wen server"
+ help
+ Mongoose small web server
+
+ https://github.com/valenok/mongoose
+
+config BR2_PACKAGE_MONGOOSE_NO_PUT_AUTH
+ bool "Disable PUT authorization"
+ depends on BR2_PACKAGE_MONGOOSE
+ default n
+ help
+ Sometimes you don't need PUT authorization.
diff --git a/package/mongoose/mongoose-3.3-init-file.patch b/package/mongoose/mongoose-3.3-init-file.patch
new file mode 100644
index 0000000..b62e4ca
--- /dev/null
+++ b/package/mongoose/mongoose-3.3-init-file.patch
@@ -0,0 +1,44 @@
+--- /dev/null 2012-12-10 08:42:11.241266044 +1300
++++ files/mongoose.init 2010-07-28 09:01:23.000000000 +1200
+@@ -0,0 +1,41 @@
++#!/bin/sh
++#
++# Start/stop the mongoose HTTP server
++#
++
++set -e
++
++PATH=/sbin:/bin:/usr/sbin:/usr/bin
++NAME=mongoose
++DESC="Mongoose HTTP server"
++
++DAEMON=`which mongoose`
++OPTIONS="-max_threads 3 -root /var/www -ports 80"
++
++[ -e /etc/default/mongoose ] && . /etc/default/mongoose
++
++case "$1" in
++ start)
++ echo "Starting $DESC:"
++ start-stop-daemon -S -x "$DAEMON" -b -- $OPTIONS
++ echo "$NAME."
++ ;;
++ stop)
++ echo -n "Stopping $DESC: "
++ start-stop-daemon -K -x "$DAEMON"
++ echo "$NAME."
++ ;;
++ restart|force-reload)
++ echo -n "Restarting $DESC: "
++ start-stop-daemon -K -x "$DAEMON"
++ start-stop-daemon -S -x "$DAEMON" -b -- $OPTIONS
++ echo "$NAME."
++ ;;
++ *)
++ N=/etc/init.d/$NAME
++ echo "Usage: $N {start|stop|restart|force-reload}" >&2
++ exit 1
++ ;;
++esac
++
++exit 0
diff --git a/package/mongoose/mongoose-3.3-no-auth.patch b/package/mongoose/mongoose-3.3-no-auth.patch
new file mode 100644
index 0000000..a470f5e
--- /dev/null
+++ b/package/mongoose/mongoose-3.3-no-auth.patch
@@ -0,0 +1,55 @@
+From db714636f86d79be33ffe8f2408c8731b5969208 Mon Sep 17 00:00:00 2001
+From: Charles Manning <cdhmanning@gmail.com>
+Date: Mon, 10 Dec 2012 10:14:20 +1300
+Subject: [PATCH] Add NO_PUT_AUTH option to allow put with not authorization
+
+Sometimes you really don't want the security.
+
+Signed-off-by: Charles Manning <cdhmanning@gmail.com>
+---
+ Makefile | 2 +-
+ mongoose.c | 8 +++++++-
+ 2 files changed, 8 insertions(+), 2 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index 14f986a..ae4755b 100644
+--- a/Makefile
++++ b/Makefile
+@@ -17,7 +17,7 @@ all:
+ # -DSSL_LIB=\"libssl.so.<version>\" - use system versioned SSL shared object
+ # -DCRYPTO_LIB=\"libcrypto.so.<version>\" - use system versioned CRYPTO so
+ # -DUSE_LUA - embed Lua in Mongoose (+100kb)
+-
++# -DNO_PUT_AUTH - disable authorization for PUT/DELETE
+
+ ##########################################################################
+ ### UNIX build: linux, bsd, mac, rtems
+diff --git a/mongoose.c b/mongoose.c
+index 2b5e586..327b419 100644
+--- a/mongoose.c
++++ b/mongoose.c
+@@ -64,6 +64,12 @@
+ #include <stddef.h>
+ #include <stdio.h>
+
++#ifdef NO_PUT_AUTH
++static int put_authorization_required = 0;
++#else
++static int put_authorization_required = 1;
++#endif
++
+ #if defined(_WIN32) && !defined(__SYMBIAN32__) // Windows specific
+ #define _WIN32_WINNT 0x0400 // To make it link in VS2005
+ #include <windows.h>
+@@ -4182,7 +4188,7 @@ static void handle_request(struct mg_connection *conn) {
+ send_options(conn);
+ } else if (conn->ctx->config[DOCUMENT_ROOT] == NULL) {
+ send_http_error(conn, 404, "Not Found", "Not Found");
+- } else if ((!strcmp(ri->request_method, "PUT") ||
++ } else if (put_authorization_required && (!strcmp(ri->request_method, "PUT") ||
+ !strcmp(ri->request_method, "DELETE")) &&
+ (conn->ctx->config[PUT_DELETE_PASSWORDS_FILE] == NULL ||
+ is_authorized_for_put(conn) != 1)) {
+--
+1.7.1
+
diff --git a/package/mongoose/mongoose.mk b/package/mongoose/mongoose.mk
new file mode 100644
index 0000000..ef06f41
--- /dev/null
+++ b/package/mongoose/mongoose.mk
@@ -0,0 +1,38 @@
+# Package for mongoose web server.
+# This has been patched with an extension to allow PUT with no authorization.
+#
+MONGOOSE_VERSION = 3.3
+MONGOOSE_SITE = http://github.com/valenok/mongoose/tarball/master
+MONGOOSE_LICENSE = MIT
+MONGOOSE_LICENSE_FILES = COPYING
+MONGOOSE_INSTALL_STAGING = YES
+MONGOOSE_INSTALL_TARGET = YES
+
+MONGOOSE_OPTIONAL_DEFINES = -DNO_SSL
+ifeq ($(BR2_PACKAGE_MONGOOSE_NO_PUT_AUTH),y)
+MONGOOSE_OPTIONAL_DEFINES += -DNO_PUT_AUTH
+endif
+
+define MONGOOSE_BUILD_CMDS
+ $(MAKE) CC="$(TARGET_CC)" LD="$TARGETLD)" -C $(@D) linux COPT="$(MONGOOSE_OPTIONAL_DEFINES)"
+endef
+
+define MONGOOSE_INSTALL_STAGING_CMDS
+ $(INSTALL) -d $(STAGING_DIR)/sbin
+ $(INSTALL) -d $(STAGING_DIR)/etc
+ $(INSTALL) -d $(STAGING_DIR)/etc/init.d
+ $(INSTALL) -D -m 755 $(@D)/mongoose $(STAGING_DIR)/sbin/mongoose
+ $(INSTALL) -D -m 755 $(@D)/mongoose.init $(STAGING_DIR)/etc/init.d/mongoose
+endef
+
+define MONGOOSE_INSTALL_TARGET_CMDS
+ $(INSTALL) -d $(TARGET_DIR)/sbin
+ $(INSTALL) -d $(TARGET_DIR)/etc
+ $(INSTALL) -d $(TARGET_DIR)/etc/init.d
+ $(INSTALL) -D -m 755 $(@D)/mongoose $(TARGET_DIR)/sbin/mongoose
+ $(INSTALL) -D -m 755 $(@D)/mongoose.init $(TARGET_DIR)/etc/init.d/mongoose
+endef
+
+
+$(eval $(generic-package))
+
--
1.7.1
^ permalink raw reply related
* [Buildroot] [PATCH] iproute2: bump to version 3.7.0
From: Peter Korsgaard @ 2012-12-12 21:33 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1355343847-29140-1-git-send-email-gustavo@zacarias.com.ar>
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] iproute2: bump to version 3.7.0
From: Peter Korsgaard @ 2012-12-12 21:32 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=2a26c4e17e0f0bb0c5952352bcdfffdde86005ce
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/iproute2/iproute2.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/iproute2/iproute2.mk b/package/iproute2/iproute2.mk
index 6f5ee51..7766ab8 100644
--- a/package/iproute2/iproute2.mk
+++ b/package/iproute2/iproute2.mk
@@ -4,7 +4,7 @@
#
#############################################################
-IPROUTE2_VERSION = 3.6.0
+IPROUTE2_VERSION = 3.7.0
IPROUTE2_SITE = $(BR2_KERNEL_MIRROR)/linux/utils/net/iproute2
IPROUTE2_TARGET_SBINS = ctstat genl ifstat ip lnstat nstat routef routel rtacct rtmon rtpr rtstat ss tc
IPROUTE2_LICENSE = GPLv2
^ permalink raw reply related
* [Buildroot] Creating/installing images
From: Willy Lambert @ 2012-12-12 21:28 UTC (permalink / raw)
To: buildroot
Hi all,
Short story :
I really don't know how to install the rootfs on my flash drive in my
embedded device, and, afaik, buildroots docs stops before this step. I
don't know if it is still a buildroot issue, but I think that, 1-,
it's necesary to benefit from buildroot job, 2-, they are many
embedded user here that can help, so I try my way.
Long story :
I was using for my embedded system a standard debian + a set of
apt-get to get a customized OS on a 2GB on board persistent memory (so
I have a working system, as kernel config for instance). But now I
decided to dive into the wonderfull world of "linux from scratch" with
the great help of busybox in order to :
_ know exactly what's on my board
_ reduce persistent size
_ stop doing overkill with a 2GB system that can fit in 32Mb
So I have setup busybox and spent some days into documentation and
sandbox, but I'm stuck with the target image installation. The
documentation stops at this point and I'm alone in the dark. I spent 2
days in searching docs on the internet without great success.
I have a successful qemu working to test the buildroot output, cause I
don't need bootloader or proper image, just giving bzImage and
rootfs.ext2 is enougth.
But as to create something that my embedded system can boot on .... I
really don't know what and how to do. So I would be glad if anyone
could help me, at least in giving links or keyword for documentation.
My target has an onboard flash memory. World would have been simplier
if I could have a removable "root" memory but it's not the case. So If
I'm correct I need to boot my target (either with an external boot
device like usb key, or with the existing linux installed on it) and
then replace the rootfs. What would you do in this case (knowing that
it will happen often in the dev cycle) ?
_ use a ram pivot_root from the current linux?
_ use a dd from an external usb key boot ?
_ re-partition all this to have a little 10Mb part for a "Tool OS"
that can be used for rootfs installation ?
_ do somethig else ?
_ take a beer and think more ?
For completness here is my board datasheet, but I don't expect anyone
to read :-). It's an Advantech PCM-3362
http://support.elmark.com.pl/advantech/pdf/pcm-3362man.pdf
Is it possible to use other filesystems, like ext3 or 4 ?
^ permalink raw reply
* [Buildroot] [PATCH 1/2] libhid: replace patch on configure by patch on configure.ac
From: Peter Korsgaard @ 2012-12-12 21:25 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1355341123-7974-1-git-send-email-thomas.petazzoni@free-electrons.com>
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> In order to fix some other build problem of libhid, we'll need to do
Thomas> modifications to the configure.ac. Therefore, let's first convert the
Thomas> current patch on configure to a patch on configure.ac, and mark the
Thomas> package as AUTORECONF=YES.
Committed both, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] libhib: fix build on PowerPC
From: Peter Korsgaard @ 2012-12-12 21:25 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=d813f707411d525a493b3d91c8266cc516e56dc8
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Add a patch to remove some stupid configure.ac that does completely
crazy things with the CFLAGS and CXXFLAGS leading to build failures
like:
http://autobuild.buildroot.org/results/7beec6b72652cc118240c959ed744ee5f2991c12/build-end.log
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
.../libhid-dont-fiddle-with-debug-flags.patch | 29 ++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/package/libhid/libhid-dont-fiddle-with-debug-flags.patch b/package/libhid/libhid-dont-fiddle-with-debug-flags.patch
new file mode 100644
index 0000000..139357b
--- /dev/null
+++ b/package/libhid/libhid-dont-fiddle-with-debug-flags.patch
@@ -0,0 +1,29 @@
+Don't do horrible magic with CFLAGS and CXXFLAGS
+
+The purpose of the lines being removed is to suppress the
+-g<something> option from the CFLAGS or CXXFLAGS, when --enable-debug
+is not used. This is stupid because it is up to the user to pass these
+flags or not.
+
+But it is not only stupid, but utterly broken: if your CFLAGS contains
+a flags like -mfloat-gprs=double, then this option gets truncated to
+-mfloat simply because the option contained the -g string!
+
+Completely ridiculous piece of code, so get rid of it.
+
+Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
+
+Index: libhid-0.2.16/m4/md_conf_debugging.m4
+===================================================================
+--- libhid-0.2.16.orig/m4/md_conf_debugging.m4 2004-11-08 18:16:25.000000000 +0100
++++ libhid-0.2.16/m4/md_conf_debugging.m4 2012-12-12 20:24:50.000000000 +0100
+@@ -1,7 +1,7 @@
+ AC_DEFUN([MD_CONF_DEBUGGING],
+ [
+- CFLAGS=$(echo $CFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
+- CXXFLAGS=$(echo $CXXFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
++# CFLAGS=$(echo $CFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
++# CXXFLAGS=$(echo $CXXFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
+ MD_CHECK_ARG_ENABLE(debug,
+ [
+ DEBUG_FLAG=-g
^ permalink raw reply related
* [Buildroot] [git commit] libhid: replace patch on configure by patch on configure.ac
From: Peter Korsgaard @ 2012-12-12 21:24 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=31341e8d40ec6c926419ebce8a71daba98a6ff9e
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
In order to fix some other build problem of libhid, we'll need to do
modifications to the configure.ac. Therefore, let's first convert the
current patch on configure to a patch on configure.ac, and mark the
package as AUTORECONF=YES.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
.../libhid/libhid-0.2.16-fix-configure-typo.patch | 24 --------------------
package/libhid/libhid-no-newline-in-ldflags.patch | 22 ++++++++++++++++++
package/libhid/libhid.mk | 1 +
3 files changed, 23 insertions(+), 24 deletions(-)
diff --git a/package/libhid/libhid-0.2.16-fix-configure-typo.patch b/package/libhid/libhid-0.2.16-fix-configure-typo.patch
deleted file mode 100644
index 870ecf2..0000000
--- a/package/libhid/libhid-0.2.16-fix-configure-typo.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-[PATCH] fix typo in configure
-
-Somehow a newline character has gotten inserted in the middle of the
-LDFLAGS assignment, breaking the build.
-
-Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
----
- configure | 3 +--
- 1 file changed, 1 insertion(+), 2 deletions(-)
-
-Index: libhid-0.2.16/configure
-===================================================================
---- libhid-0.2.16.orig/configure
-+++ libhid-0.2.16/configure
-@@ -23050,8 +23050,7 @@ echo "$as_me: doxygen disabled by config
- CPPFLAGS=$(echo $CPPFLAGS)
- CFLAGS=$(echo $OS_CFLAGS $LIBUSB_CFLAGS $CFLAGS)
- CXXFLAGS=$(echo $CXXFLAGS)
-- LDFLAGS=$(echo $OS_LDFLAGS $LIBUSB_LIBS
-- $LDFLAGS)
-+ LDFLAGS=$(echo $OS_LDFLAGS $LIBUSB_LIBS $LDFLAGS)
-
-
-
diff --git a/package/libhid/libhid-no-newline-in-ldflags.patch b/package/libhid/libhid-no-newline-in-ldflags.patch
new file mode 100644
index 0000000..df845ee
--- /dev/null
+++ b/package/libhid/libhid-no-newline-in-ldflags.patch
@@ -0,0 +1,22 @@
+Fix improper usage of macro that introduces a wrong newline
+
+The MD_CONF_FLAGS() macro was used with a final newline that
+introduces an invalid newline in the middle of the macro expansion
+when defining LDFLAGS.
+
+Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
+
+Index: libhid-0.2.16/configure.ac
+===================================================================
+--- libhid-0.2.16.orig/configure.ac 2007-04-01 22:32:10.000000000 +0200
++++ libhid-0.2.16/configure.ac 2012-12-12 20:24:03.000000000 +0100
+@@ -102,8 +102,7 @@
+ [],
+ [$OS_CFLAGS $LIBUSB_CFLAGS],
+ [],
+- [$OS_LDFLAGS $LIBUSB_LIBS]
+-)
++ [$OS_LDFLAGS $LIBUSB_LIBS])
+
+ MD_CONF_DB2MAN
+
diff --git a/package/libhid/libhid.mk b/package/libhid/libhid.mk
index bad014b..484cdcc 100644
--- a/package/libhid/libhid.mk
+++ b/package/libhid/libhid.mk
@@ -9,6 +9,7 @@ LIBHID_SOURCE = libhid-$(LIBHID_VERSION).tar.gz
LIBHID_SITE = http://alioth.debian.org/frs/download.php/1958
LIBHID_DEPENDENCIES = libusb-compat libusb
LIBHID_INSTALL_STAGING = YES
+LIBHID_AUTORECONF = YES
# configure runs libusb-config for cflags/ldflags. Ensure it picks up
# the target version
LIBHID_CONF_ENV = PATH=$(STAGING_DIR)/usr/bin:$(TARGET_PATH)
^ permalink raw reply related
* [Buildroot] Getting It into Compact Flash
From: Richard Braun @ 2012-12-12 20:49 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121212162225.GA15887@mail.sceen.net>
On Wed, Dec 12, 2012 at 05:22:26PM +0100, Richard Braun wrote:
> On Wed, Dec 12, 2012 at 04:12:49PM -0000, Ted Wood wrote:
> > It starts up OK, loads the kernel and uncompresses it.
> >
> > It mounts sda and sda1
> >
> > Then "No filesystem could mount root, tried ext3 vfat msdos iso9660"
>
> Buildroot doesn't take care of the partition table.
>
> See http://lists.busybox.net/pipermail/buildroot/2012-August/057536.html
> (and the next message for the unspoiled attached script).
If your problem has nothing to do with the partition table, feel free to
give us more information about it, like the boot log (so that we can see
what is actually mounted).
--
Richard Braun
^ permalink raw reply
* [Buildroot] [PATCH] gadgetfs-test: requires thread support
From: Peter Korsgaard @ 2012-12-12 20:48 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1355337862-6519-1-git-send-email-thomas.petazzoni@free-electrons.com>
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Fixes:
Thomas> http://autobuild.buildroot.org/results/012914ed010eac94a2f7bfe18d8375cdb2fe9f06/build-end.log
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] gadgetfs-test: requires thread support
From: Peter Korsgaard @ 2012-12-12 20:48 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=5d4e00bd04183463f878d5c57b3a3dc47fbb2333
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Fixes:
http://autobuild.buildroot.org/results/012914ed010eac94a2f7bfe18d8375cdb2fe9f06/build-end.log
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/gadgetfs-test/Config.in | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/package/gadgetfs-test/Config.in b/package/gadgetfs-test/Config.in
index 276ec54..a582db6 100644
--- a/package/gadgetfs-test/Config.in
+++ b/package/gadgetfs-test/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_GADGETFS_TEST
bool "gadgetfs-test"
+ depends on BR2_TOOLCHAIN_HAS_THREADS
help
Test program for gadgetfs from linux-usb.org
@@ -10,3 +11,6 @@ config BR2_PACKAGE_GADGETFS_TEST_USE_AIO
help
Select this to have gadgetfs-test do asynchronous I/O using
the libaio library.
+
+comment "gadgetfs-test requires thread support in toolchain"
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
^ permalink raw reply related
* [Buildroot] [PATCH 1/2] samba: bump to version 3.6.10
From: Peter Korsgaard @ 2012-12-12 20:24 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1355336485-22792-1-git-send-email-gustavo@zacarias.com.ar>
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Committed both, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] squid: bump to version 3.2.5
From: Peter Korsgaard @ 2012-12-12 20:24 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=f610bf0c89d036a0451ecde4dd5627fbe2687ef2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/squid/squid.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/squid/squid.mk b/package/squid/squid.mk
index 3c08c39..43e2d24 100644
--- a/package/squid/squid.mk
+++ b/package/squid/squid.mk
@@ -4,7 +4,7 @@
#
#############################################################
-SQUID_VERSION = 3.2.4
+SQUID_VERSION = 3.2.5
SQUID_SITE = http://www.squid-cache.org/Versions/v3/3.2
SQUID_LICENSE = GPLv2+
SQUID_LICENSE_FILES = COPYING
^ permalink raw reply related
* [Buildroot] [git commit] samba: bump to version 3.6.10
From: Peter Korsgaard @ 2012-12-12 20:24 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=53f2c75754ad7cd5958d9156e01156fe9c8fce53
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/samba/samba.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/samba/samba.mk b/package/samba/samba.mk
index 4f87917..161e507 100644
--- a/package/samba/samba.mk
+++ b/package/samba/samba.mk
@@ -4,7 +4,7 @@
#
#############################################################
-SAMBA_VERSION = 3.6.9
+SAMBA_VERSION = 3.6.10
SAMBA_SITE = http://ftp.samba.org/pub/samba/stable
SAMBA_SUBDIR = source3
SAMBA_INSTALL_STAGING = YES
^ permalink raw reply related
* [Buildroot] [PATCH] iproute2: bump to version 3.7.0
From: Gustavo Zacarias @ 2012-12-12 20:24 UTC (permalink / raw)
To: buildroot
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
---
package/iproute2/iproute2.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/iproute2/iproute2.mk b/package/iproute2/iproute2.mk
index 6f5ee51..7766ab8 100644
--- a/package/iproute2/iproute2.mk
+++ b/package/iproute2/iproute2.mk
@@ -4,7 +4,7 @@
#
#############################################################
-IPROUTE2_VERSION = 3.6.0
+IPROUTE2_VERSION = 3.7.0
IPROUTE2_SITE = $(BR2_KERNEL_MIRROR)/linux/utils/net/iproute2
IPROUTE2_TARGET_SBINS = ctstat genl ifstat ip lnstat nstat routef routel rtacct rtmon rtpr rtstat ss tc
IPROUTE2_LICENSE = GPLv2
--
1.7.8.6
^ permalink raw reply related
* [Buildroot] [git commit] toolchain/gcc: also disable largefile for pass 1/2 if needed
From: Peter Korsgaard @ 2012-12-12 20:22 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=7ce93438c12ca68c9bb12ed28c4d15d1fa840c94
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Fixes issue with !BR2_LARGEFILE builds on Ubuntu 12.04 and GCC 4.6+
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/gcc/gcc-uclibc-4.x.mk | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/toolchain/gcc/gcc-uclibc-4.x.mk b/toolchain/gcc/gcc-uclibc-4.x.mk
index 7a0b4ca..b0d741b 100644
--- a/toolchain/gcc/gcc-uclibc-4.x.mk
+++ b/toolchain/gcc/gcc-uclibc-4.x.mk
@@ -308,6 +308,7 @@ $(GCC_BUILD_DIR1)/.configured: $(GCC_DIR)/.patched
$(GCC_DECIMAL_FLOAT) \
$(SOFT_FLOAT_CONFIG_OPTION) \
$(GCC_WITH_ABI) $(GCC_WITH_ARCH) $(GCC_WITH_TUNE) $(GCC_WITH_CPU) \
+ $(DISABLE_LARGEFILE) \
$(EXTRA_GCC_CONFIG_OPTIONS) \
)
touch $@
@@ -373,6 +374,7 @@ $(GCC_BUILD_DIR2)/.configured: $(GCC_DIR)/.patched
$(GCC_DECIMAL_FLOAT) \
$(SOFT_FLOAT_CONFIG_OPTION) \
$(GCC_WITH_ABI) $(GCC_WITH_ARCH) $(GCC_WITH_TUNE) $(GCC_WITH_CPU) \
+ $(DISABLE_LARGEFILE) \
$(EXTRA_GCC_CONFIG_OPTIONS) \
)
touch $@
^ permalink raw reply related
* [Buildroot] [git commit] package: remove explicit --disable-doc* passing
From: Peter Korsgaard @ 2012-12-12 20:20 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=e10cfb1e766441dd6b268e27ca97436f8b5ed0d1
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Now that it is handled globally (pkg-infra: pass --disable-doc if
documentation is not enabled).
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/efl/libevas/libevas.mk | 5 -----
package/fontconfig/fontconfig.mk | 1 -
package/sysstat/sysstat.mk | 4 ----
package/x11r7/xlib_libSM/xlib_libSM.mk | 5 -----
package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk | 2 --
package/x11r7/xlib_xtrans/xlib_xtrans.mk | 2 --
6 files changed, 0 insertions(+), 19 deletions(-)
diff --git a/package/efl/libevas/libevas.mk b/package/efl/libevas/libevas.mk
index 402aa48..2e9e930 100644
--- a/package/efl/libevas/libevas.mk
+++ b/package/efl/libevas/libevas.mk
@@ -210,10 +210,5 @@ else
LIBEVAS_CONF_OPT += --disable-font-loader-eet
endif
-# documentation
-ifneq ($(BR2_HAVE_DOCUMENTATION),y)
-LIBEVAS_CONF_OPT += --disable-doc
-endif
-
$(eval $(autotools-package))
$(eval $(host-autotools-package))
diff --git a/package/fontconfig/fontconfig.mk b/package/fontconfig/fontconfig.mk
index 9845656..6762126 100644
--- a/package/fontconfig/fontconfig.mk
+++ b/package/fontconfig/fontconfig.mk
@@ -24,7 +24,6 @@ FONTCONFIG_CONF_OPT = --with-arch=$(GNU_TARGET_NAME) \
FONTCONFIG_DEPENDENCIES = freetype expat
HOST_FONTCONFIG_CONF_OPT = \
- --disable-docs \
--disable-static
$(eval $(autotools-package))
diff --git a/package/sysstat/sysstat.mk b/package/sysstat/sysstat.mk
index 83609a0..0513998 100644
--- a/package/sysstat/sysstat.mk
+++ b/package/sysstat/sysstat.mk
@@ -9,10 +9,6 @@ SYSSTAT_SOURCE = sysstat-$(SYSSTAT_VERSION).tar.bz2
SYSSTAT_SITE = http://pagesperso-orange.fr/sebastien.godard
SYSSTAT_CONF_OPT = --disable-man-group --disable-sensors
-ifneq ($(BR2_HAVE_DOCUMENTATION),y)
-SYSSTAT_CONF_OPT += --disable-documentation
-endif
-
ifeq ($(BR2_NEEDS_GETTEXT_IF_LOCALE),y)
SYSSTAT_DEPENDENCIES += gettext
SYSSTAT_MAKE_OPT += CFLAGS+=-lintl
diff --git a/package/x11r7/xlib_libSM/xlib_libSM.mk b/package/x11r7/xlib_libSM/xlib_libSM.mk
index bdbda3f..a8d1eff 100644
--- a/package/x11r7/xlib_libSM/xlib_libSM.mk
+++ b/package/x11r7/xlib_libSM/xlib_libSM.mk
@@ -11,9 +11,4 @@ XLIB_LIBSM_INSTALL_STAGING = YES
XLIB_LIBSM_DEPENDENCIES = xlib_libICE xlib_xtrans xproto_xproto
XLIB_LIBSM_CONF_OPT = --without-libuuid
-ifneq ($(BR2_HAVE_DOCUMENTATION),y)
-# documentation generation is slow
-XLIB_LIBSM_CONF_OPT += --disable-docs
-endif
-
$(eval $(autotools-package))
diff --git a/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk b/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
index 7177ae8..5a702e5 100644
--- a/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
+++ b/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
@@ -9,8 +9,6 @@ XLIB_LIBXDMCP_SOURCE = libXdmcp-$(XLIB_LIBXDMCP_VERSION).tar.bz2
XLIB_LIBXDMCP_SITE = http://xorg.freedesktop.org/releases/individual/lib
XLIB_LIBXDMCP_INSTALL_STAGING = YES
XLIB_LIBXDMCP_DEPENDENCIES = xutil_util-macros xproto_xproto
-XLIB_LIBXDMCP_CONF_OPT = $(if $(BR2_HAVE_DOCUMENTATION),,--disable-docs)
-HOST_XLIB_LIBXDMCP_CONF_OPT = --disable-docs
$(eval $(autotools-package))
$(eval $(host-autotools-package))
diff --git a/package/x11r7/xlib_xtrans/xlib_xtrans.mk b/package/x11r7/xlib_xtrans/xlib_xtrans.mk
index d47a0ed..8582985 100644
--- a/package/x11r7/xlib_xtrans/xlib_xtrans.mk
+++ b/package/x11r7/xlib_xtrans/xlib_xtrans.mk
@@ -8,8 +8,6 @@ XLIB_XTRANS_VERSION = 1.2.6
XLIB_XTRANS_SOURCE = xtrans-$(XLIB_XTRANS_VERSION).tar.bz2
XLIB_XTRANS_SITE = http://xorg.freedesktop.org/releases/individual/lib
XLIB_XTRANS_INSTALL_STAGING = YES
-XLIB_XTRANS_CONF_OPT = $(if $(BR2_HAVE_DOCUMENTATION),,--disable-docs)
-HOST_XLIB_XTRANS_CONF_OPT = --disable-docs
$(eval $(autotools-package))
$(eval $(host-autotools-package))
^ permalink raw reply related
* [Buildroot] buildroot 2012.11 large file support
From: Peter Korsgaard @ 2012-12-12 20:15 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121212183204.718be669@skate>
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Hmm, we already pass --disable-largefile to the gcc configure script,
>> except for the first 2 passes. Does it work if we add
>> $(DISABLE_LARGEFILE) to the gcc1 / gcc2 configure steps?
Thomas> !largefile build is OK if we pass $(DISABLE_LARGEFILE) to gcc1 and gcc2
Thomas> configure steps, so it solves the build problem. I haven't done more
Thomas> testing though (testing the generated code, building with largefile
Thomas> enabled, etc.).
Cool, great - I'll commit that then.
Thomas> That said, doesn't --disable-largefile disables largefile support at
Thomas> the level of gcc itself, rather than taking into account the fact that
Thomas> largefile support is not available on the target? Of course, it has the
Thomas> consequence that _FILE_OFFSET_BITS is no longer defined to 64 in
Thomas> auto-conf.h, which works around the problem. But gcc (the host
Thomas> binary) should be capable of being built with largefile support on a 32
Thomas> bits host, even if the 32 bits target has no largefile support.
So for the cross compiler to be able to access large files? Is that
really important? I doubt people are using buildroot with 2G+
source/object/library files?
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] usb_modeswitch and lsusb yield Segmentation fault
From: Peter Korsgaard @ 2012-12-12 19:44 UTC (permalink / raw)
To: buildroot
In-Reply-To: <7EE27C3F912F450282DD2DE63A6A7FED@JohanW7>
>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
Sagaert> Hi
Sagaert> I was using the newer pthreads implementation,
Sagaert> The old/stable pthreads are working for both lsusb (usbutils) and for usb_modeswitch with uClibc 0.9.33
Sagaert> I did not try NTPL since this breaks the build of GDB.
Really? I don't recall any issues with GDB and NTPL? Could you provide
more details, please?
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [PATCH 2/2] libhib: fix build on PowerPC
From: Thomas Petazzoni @ 2012-12-12 19:38 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1355341123-7974-1-git-send-email-thomas.petazzoni@free-electrons.com>
Add a patch to remove some stupid configure.ac that does completely
crazy things with the CFLAGS and CXXFLAGS leading to build failures
like:
http://autobuild.buildroot.org/results/7beec6b72652cc118240c959ed744ee5f2991c12/build-end.log
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
.../libhid-dont-fiddle-with-debug-flags.patch | 29 ++++++++++++++++++++
1 file changed, 29 insertions(+)
create mode 100644 package/libhid/libhid-dont-fiddle-with-debug-flags.patch
diff --git a/package/libhid/libhid-dont-fiddle-with-debug-flags.patch b/package/libhid/libhid-dont-fiddle-with-debug-flags.patch
new file mode 100644
index 0000000..139357b
--- /dev/null
+++ b/package/libhid/libhid-dont-fiddle-with-debug-flags.patch
@@ -0,0 +1,29 @@
+Don't do horrible magic with CFLAGS and CXXFLAGS
+
+The purpose of the lines being removed is to suppress the
+-g<something> option from the CFLAGS or CXXFLAGS, when --enable-debug
+is not used. This is stupid because it is up to the user to pass these
+flags or not.
+
+But it is not only stupid, but utterly broken: if your CFLAGS contains
+a flags like -mfloat-gprs=double, then this option gets truncated to
+-mfloat simply because the option contained the -g string!
+
+Completely ridiculous piece of code, so get rid of it.
+
+Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
+
+Index: libhid-0.2.16/m4/md_conf_debugging.m4
+===================================================================
+--- libhid-0.2.16.orig/m4/md_conf_debugging.m4 2004-11-08 18:16:25.000000000 +0100
++++ libhid-0.2.16/m4/md_conf_debugging.m4 2012-12-12 20:24:50.000000000 +0100
+@@ -1,7 +1,7 @@
+ AC_DEFUN([MD_CONF_DEBUGGING],
+ [
+- CFLAGS=$(echo $CFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
+- CXXFLAGS=$(echo $CXXFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
++# CFLAGS=$(echo $CFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
++# CXXFLAGS=$(echo $CXXFLAGS | sed -e 's,-g[[^[:space:]]]*,,g')
+ MD_CHECK_ARG_ENABLE(debug,
+ [
+ DEBUG_FLAG=-g
--
1.7.9.5
^ permalink raw reply related
* [Buildroot] [PATCH 1/2] libhid: replace patch on configure by patch on configure.ac
From: Thomas Petazzoni @ 2012-12-12 19:38 UTC (permalink / raw)
To: buildroot
In order to fix some other build problem of libhid, we'll need to do
modifications to the configure.ac. Therefore, let's first convert the
current patch on configure to a patch on configure.ac, and mark the
package as AUTORECONF=YES.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
.../libhid/libhid-0.2.16-fix-configure-typo.patch | 24 --------------------
package/libhid/libhid-no-newline-in-ldflags.patch | 22 ++++++++++++++++++
package/libhid/libhid.mk | 1 +
3 files changed, 23 insertions(+), 24 deletions(-)
delete mode 100644 package/libhid/libhid-0.2.16-fix-configure-typo.patch
create mode 100644 package/libhid/libhid-no-newline-in-ldflags.patch
diff --git a/package/libhid/libhid-0.2.16-fix-configure-typo.patch b/package/libhid/libhid-0.2.16-fix-configure-typo.patch
deleted file mode 100644
index 870ecf2..0000000
--- a/package/libhid/libhid-0.2.16-fix-configure-typo.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-[PATCH] fix typo in configure
-
-Somehow a newline character has gotten inserted in the middle of the
-LDFLAGS assignment, breaking the build.
-
-Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
----
- configure | 3 +--
- 1 file changed, 1 insertion(+), 2 deletions(-)
-
-Index: libhid-0.2.16/configure
-===================================================================
---- libhid-0.2.16.orig/configure
-+++ libhid-0.2.16/configure
-@@ -23050,8 +23050,7 @@ echo "$as_me: doxygen disabled by config
- CPPFLAGS=$(echo $CPPFLAGS)
- CFLAGS=$(echo $OS_CFLAGS $LIBUSB_CFLAGS $CFLAGS)
- CXXFLAGS=$(echo $CXXFLAGS)
-- LDFLAGS=$(echo $OS_LDFLAGS $LIBUSB_LIBS
-- $LDFLAGS)
-+ LDFLAGS=$(echo $OS_LDFLAGS $LIBUSB_LIBS $LDFLAGS)
-
-
-
diff --git a/package/libhid/libhid-no-newline-in-ldflags.patch b/package/libhid/libhid-no-newline-in-ldflags.patch
new file mode 100644
index 0000000..df845ee
--- /dev/null
+++ b/package/libhid/libhid-no-newline-in-ldflags.patch
@@ -0,0 +1,22 @@
+Fix improper usage of macro that introduces a wrong newline
+
+The MD_CONF_FLAGS() macro was used with a final newline that
+introduces an invalid newline in the middle of the macro expansion
+when defining LDFLAGS.
+
+Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
+
+Index: libhid-0.2.16/configure.ac
+===================================================================
+--- libhid-0.2.16.orig/configure.ac 2007-04-01 22:32:10.000000000 +0200
++++ libhid-0.2.16/configure.ac 2012-12-12 20:24:03.000000000 +0100
+@@ -102,8 +102,7 @@
+ [],
+ [$OS_CFLAGS $LIBUSB_CFLAGS],
+ [],
+- [$OS_LDFLAGS $LIBUSB_LIBS]
+-)
++ [$OS_LDFLAGS $LIBUSB_LIBS])
+
+ MD_CONF_DB2MAN
+
diff --git a/package/libhid/libhid.mk b/package/libhid/libhid.mk
index bad014b..484cdcc 100644
--- a/package/libhid/libhid.mk
+++ b/package/libhid/libhid.mk
@@ -9,6 +9,7 @@ LIBHID_SOURCE = libhid-$(LIBHID_VERSION).tar.gz
LIBHID_SITE = http://alioth.debian.org/frs/download.php/1958
LIBHID_DEPENDENCIES = libusb-compat libusb
LIBHID_INSTALL_STAGING = YES
+LIBHID_AUTORECONF = YES
# configure runs libusb-config for cflags/ldflags. Ensure it picks up
# the target version
LIBHID_CONF_ENV = PATH=$(STAGING_DIR)/usr/bin:$(TARGET_PATH)
--
1.7.9.5
^ permalink raw reply related
* [Buildroot] [PATCH] gadgetfs-test: requires thread support
From: Thomas Petazzoni @ 2012-12-12 18:44 UTC (permalink / raw)
To: buildroot
Fixes:
http://autobuild.buildroot.org/results/012914ed010eac94a2f7bfe18d8375cdb2fe9f06/build-end.log
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
package/gadgetfs-test/Config.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/gadgetfs-test/Config.in b/package/gadgetfs-test/Config.in
index 276ec54..a582db6 100644
--- a/package/gadgetfs-test/Config.in
+++ b/package/gadgetfs-test/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_GADGETFS_TEST
bool "gadgetfs-test"
+ depends on BR2_TOOLCHAIN_HAS_THREADS
help
Test program for gadgetfs from linux-usb.org
@@ -10,3 +11,6 @@ config BR2_PACKAGE_GADGETFS_TEST_USE_AIO
help
Select this to have gadgetfs-test do asynchronous I/O using
the libaio library.
+
+comment "gadgetfs-test requires thread support in toolchain"
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
--
1.7.9.5
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox