* [Buildroot] [git commit] xlib_libXdmcp: only build documentation if explicitly requested
From: Peter Korsgaard @ 2012-12-04 2:20 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=68cdb5e2d7b0e8211708012c31dd109e069c098d
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk b/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
index 5a702e5..7177ae8 100644
--- a/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
+++ b/package/x11r7/xlib_libXdmcp/xlib_libXdmcp.mk
@@ -9,6 +9,8 @@ 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))
^ permalink raw reply related
* [Buildroot] Chances in skeleton don't appear in filesystem
From: Woody Wu @ 2012-12-04 2:16 UTC (permalink / raw)
To: buildroot
Hi, list
After some intial builds, I come up with idea to make chances in the
default filesystem contents. Then I change the config to use customized
filesystem skeleton (fs/skeleton) and changed the
fs/skeleton/network/interfaces with expection that change could appear
in the generated target file system. After another run of make,
however, I did not see my chances by untar the rootfs.tar.bz2. Then I
tried to remove the output/target directory, this time I even got
another error, 'output/target/etc/hosts: no such file or directory'.
What's the correct method to modify the defualt filesystem? Thanks.
--
woody
I can't go back to yesterday - because I was a different person then.
^ permalink raw reply
* [Buildroot] How to handle modularity in buildroot?
From: Charles Manning @ 2012-12-03 23:49 UTC (permalink / raw)
To: buildroot
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C610B824F7@ex-mb1.corp.adtran.com>
On Tuesday 04 December 2012 12:17:13 ANDY KENNEDY wrote:
> >
> > Is there an easy way to have modular/hierarchical projects? For
> > example I would like to have a base file system that holds common
> > stuff but then have variants (eg. production vs development).
> >
> > In OE this is easy: just create a "basic system" package which is
> > included in the recipes for each of the variants.
> >
> > How would this be tackled in buildroot?
>
> I believe what you are looking for is 'make defconfig'. This will
> provide a basic set of configuration options to get you going, then
> you'll have to edit the things like processor family, processor type,
> whether you want uClibc vs {e,}glibc, etc.
>
> The default config is usually okay for a first attempt, however, I like
> to provide to others in my company a set of config files to choose from.
> Those, I derive from just cranking through the menuconfig and save the
> options off when I get done.
>
> If you are looking for more than this, there are a few other default
> config files to attempt. To list those config files do a 'make help'.
>
> Hope this helps!
Thanks Andy
I am aware of this mechanism but I don't think it really gets me what I am
after.
I think that with defconfig, I would be able to make defconfig, then tweak the
config to get a variant. But now if I change the base config, I then have to
go through the process again for the variant.
What I would like is the ability to have:
* A base package
* Production rootfs = base + production files.
* Development rootfs = base + development files.
Then a change to the base package automatically flows through the production +
development rootfs.
Is there a way to accomplish that?
Thanks
Charles
^ permalink raw reply
* [Buildroot] How to handle modularity in buildroot?
From: ANDY KENNEDY @ 2012-12-03 23:17 UTC (permalink / raw)
To: buildroot
In-Reply-To: <CAE21AQpHdjzrJYnUBY6qwVBvd1HKpFGcKoTAsWcHyOFpua-yeA@mail.gmail.com>
> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] On Behalf Of Charles
> Manning
> Sent: Monday, December 03, 2012 4:01 PM
> To: buildroot at busybox.net
> Subject: [Buildroot] How to handle modularity in buildroot?
>
> Hello All
>
> Ok, first off... I must absolutely congratulate and thank everyone for
> a really useful build system.
>
> Until now I had been using openembedded to build smaller file systems
> for embedded systems. OE is way overkill for most embedded systems and
> is like trying to use a chainsaw to cut butter. Buildroot is much
> faster than OE and is way easier to navigate.
>
> There are a few things I could do in OE that I am struggling with in
> buildroot - no doubt mainly due to my learner status. One of these is
> handling modularity.
>
> Is there an easy way to have modular/hierarchical projects? For
> example I would like to have a base file system that holds common
> stuff but then have variants (eg. production vs development).
>
> In OE this is easy: just create a "basic system" package which is
> included in the recipes for each of the variants.
>
> How would this be tackled in buildroot?
I believe what you are looking for is 'make defconfig'. This will
provide a basic set of configuration options to get you going, then
you'll have to edit the things like processor family, processor type,
whether you want uClibc vs {e,}glibc, etc.
The default config is usually okay for a first attempt, however, I like
to provide to others in my company a set of config files to choose from.
Those, I derive from just cranking through the menuconfig and save the
options off when I get done.
If you are looking for more than this, there are a few other default
config files to attempt. To list those config files do a 'make help'.
Hope this helps!
Andy
>
> Thanks
>
> Charles
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
^ permalink raw reply
* [Buildroot] elfutils and the perf userspace tool
From: Bogdan Radulescu @ 2012-12-03 22:20 UTC (permalink / raw)
To: buildroot
Hello everybody,
I am using buildroot for generating a distro for ARM. I am able to add additional packages to buildroot or to use arm-linux-gcc directly to compile simple C programs.
Still I haven't yet understood how to cross compile the perf userspace tool and I think it would be a very nice addition to buildroot.
The perf tool requires elfutils and the kernel sources it comes with.
My first problem is that elfutils will not successfully compile, as you can see here:
http://pastie.org/pastes/5474687/text
My elfutils.mk file looks like this http://pastie.org/pastes/5474697/text
Please tell me how do I move further from this.
Thanks,
Bogdan
^ permalink raw reply
* [Buildroot] How to handle modularity in buildroot?
From: Charles Manning @ 2012-12-03 22:00 UTC (permalink / raw)
To: buildroot
Hello All
Ok, first off... I must absolutely congratulate and thank everyone for
a really useful build system.
Until now I had been using openembedded to build smaller file systems
for embedded systems. OE is way overkill for most embedded systems and
is like trying to use a chainsaw to cut butter. Buildroot is much
faster than OE and is way easier to navigate.
There are a few things I could do in OE that I am struggling with in
buildroot - no doubt mainly due to my learner status. One of these is
handling modularity.
Is there an easy way to have modular/hierarchical projects? For
example I would like to have a base file system that holds common
stuff but then have variants (eg. production vs development).
In OE this is easy: just create a "basic system" package which is
included in the recipes for each of the variants.
How would this be tackled in buildroot?
Thanks
Charles
^ permalink raw reply
* [Buildroot] [PATCH] Add support for dtb file in /boot directory on target
From: Gary Coulbourne @ 2012-12-03 21:43 UTC (permalink / raw)
To: buildroot
Howdy!
I'm using u-boot, and loading both the kernel image and the dtb from /boot
on my target. I added support for this, and am
submitting the patch should it be useful to anyone else.
---
linux/Config.in | 6 ++++++
linux/linux.mk | 7 +++++++
2 files changed, 13 insertions(+)
diff --git a/linux/Config.in b/linux/Config.in
index f408ad5..d5ffa57 100644
--- a/linux/Config.in
+++ b/linux/Config.in
@@ -283,6 +283,12 @@ config BR2_LINUX_KERNEL_INSTALL_TARGET
/boot in the target root filesystem, as is typically done on
x86/x86_64 systems.
+config BR2_LINUX_DEVICE_TREE_INSTALL_TARGET
+ bool "Install Device Tree to /boot in target"
+ depends on BR2_LINUX_KERNEL_DTS_SUPPORT
+ help
+ Select this option to have the device tree installed to
+ /boot in the target root filesystem.
# Linux extensions
source "linux/Config.ext.in"
diff --git a/linux/linux.mk b/linux/linux.mk
index c4bdf90..8778c35 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -208,6 +208,12 @@ define LINUX_APPEND_DTB
endef
endif
+ifeq ($(BR2_LINUX_DEVICE_TREE_INSTALL_TARGET),y)
+define LINUX_DEVICE_TREE_INSTALL_TARGET
+ install -m 0644 -D $(KERNEL_ARCH_PATH)/boot/$(KERNEL_DTS_NAME).dtb
$(TARGET_DIR)/boot/$(KERNEL_DTS_NAME).dtb
+endef
+endif
+
# Compilation. We make sure the kernel gets rebuilt when the
# configuration has changed.
define LINUX_BUILD_CMDS
@@ -244,6 +250,7 @@ endef
define LINUX_INSTALL_TARGET_CMDS
$(LINUX_INSTALL_KERNEL_IMAGE_TO_TARGET)
$(LINUX_INSTALL_DTB)
+ $(LINUX_DEVICE_TREE_INSTALL_TARGET)
# Install modules and remove symbolic links pointing to build
# directories, not relevant on the target
@if grep -q "CONFIG_MODULES=y" $(@D)/.config; then \
--
1.7.10.4
Peace,
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121203/89b6ad10/attachment-0001.html>
^ permalink raw reply related
* [Buildroot] Problem with NFS boot
From: Santhosh Ramani @ 2012-12-03 20:28 UTC (permalink / raw)
To: buildroot
In-Reply-To: <50BB309F.606@relinux.de>
Hello Stephen,
Thanks for your reply again, yes the rootfs are the same and the Linux
kernel is also the same since I tar the kernel and then buildroot uses that
as my custom kernel.
The only reason to not use the buildroot system to create the kernel image
is that it builds clean and this increases the build times. I would like to
get to a point where I can fix the rootfs temporarily, get the linux kernel
cleaned up and then go to the rootfs fixup.
Any thoughts on this one? In either case, the buildroot process should
create an identical kernel as compared to the TI -sdk should it not - if
the configurations are the same. Which I'm sure they are...
Thank you
Regards
Santhosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121203/97476e61/attachment.html>
^ permalink raw reply
* [Buildroot] [PATCH] package/crosstool-ng: update to 1.17.0
From: Carsten Schoenert @ 2012-12-03 19:47 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354564065-24388-1-git-send-email-c.schoenert@t-online.de>
From: Carsten Schoenert <c.schoenert@t-online.de>
Updating current crosstool-ng config files to 1.17.0
crosstool-ng.config-eglibc
crosstool-ng.config-glibc
crosstool-ng.config-uClibc
Signed-off-by: Carsten Schoenert <c.schoenert@t-online.de>
---
package/crosstool-ng/crosstool-ng.mk | 2 +-
.../crosstool-ng.config-eglibc | 73 ++++++++++++++-----
.../crosstool-ng.config-glibc | 74 +++++++++++++++-----
.../crosstool-ng.config-uClibc | 71 ++++++++++++++-----
4 files changed, 165 insertions(+), 55 deletions(-)
diff --git a/package/crosstool-ng/crosstool-ng.mk b/package/crosstool-ng/crosstool-ng.mk
index 5bc65e1..3b207a2 100644
--- a/package/crosstool-ng/crosstool-ng.mk
+++ b/package/crosstool-ng/crosstool-ng.mk
@@ -1,4 +1,4 @@
-CROSSTOOL_NG_VERSION = 1.16.0
+CROSSTOOL_NG_VERSION = 1.17.0
CROSSTOOL_NG_SOURCE = crosstool-ng-$(CROSSTOOL_NG_VERSION).tar.bz2
CROSSTOOL_NG_SITE = http://crosstool-ng.org/download/crosstool-ng/
CROSSTOOL_NG_INSTALL_TARGET = NO
diff --git a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-eglibc b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-eglibc
index 6c55921..1b523ec 100644
--- a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-eglibc
+++ b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-eglibc
@@ -1,12 +1,10 @@
#
# Automatically generated make config: don't edit
-# crosstool-NG 1.16.0 Configuration
-# Sun Aug 5 20:02:42 2012
+# crosstool-NG 1.17.0 Configuration
+# Mon Dec 3 20:10:26 2012
#
CT_CONFIGURE_has_xz=y
-CT_CONFIGURE_has_cvs=y
CT_CONFIGURE_has_svn=y
-CT_BACKEND=y
CT_MODULES=y
#
@@ -18,15 +16,16 @@ CT_MODULES=y
#
# CT_OBSOLETE is not set
# CT_EXPERIMENTAL is not set
+# CT_DEBUG_CT is not set
#
# Paths
#
CT_LOCAL_TARBALLS_DIR=""
-CT_SAVE_TARBALLS=y
CT_WORK_DIR="${CT_TOP_DIR}/.build"
CT_PREFIX_DIR=""
CT_INSTALL_DIR="${CT_PREFIX_DIR}"
+CT_RM_RF_PREFIX_DIR=y
CT_REMOVE_DOCS=y
# CT_INSTALL_DIR_RO is not set
# CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES is not set
@@ -58,16 +57,15 @@ CT_PATCH_ORDER="bundled"
#
# Build behavior
#
-
-#
-# Build options hiden
-#
CT_PARALLEL_JOBS=0
CT_LOAD=0
CT_USE_PIPES=y
CT_EXTRA_FLAGS_FOR_HOST=""
-CT_CONFIG_SHELL_CUSTOM_PATH="/bin/sh"
-CT_CONFIG_SHELL="/bin/sh"
+# CT_CONFIG_SHELL_SH is not set
+# CT_CONFIG_SHELL_ASH is not set
+CT_CONFIG_SHELL_BASH=y
+# CT_CONFIG_SHELL_CUSTOM is not set
+CT_CONFIG_SHELL="${bash}"
#
# Logging
@@ -111,8 +109,27 @@ CT_ARCH_BITNESS=32
CT_ARCH_FLOAT_SW=y
CT_TARGET_CFLAGS=""
CT_TARGET_LDFLAGS=""
+# CT_ARCH_alpha is not set
CT_ARCH_arm=y
+# CT_ARCH_avr32 is not set
+# CT_ARCH_blackfin is not set
+# CT_ARCH_mips is not set
+# CT_ARCH_powerpc is not set
+# CT_ARCH_sh is not set
+# CT_ARCH_sparc is not set
+# CT_ARCH_x86 is not set
+CT_ARCH_alpha_AVAILABLE=y
CT_ARCH_arm_AVAILABLE=y
+CT_ARCH_avr32_AVAILABLE=y
+CT_ARCH_blackfin_AVAILABLE=y
+CT_ARCH_m68k_AVAILABLE=y
+CT_ARCH_microblaze_AVAILABLE=y
+CT_ARCH_mips_AVAILABLE=y
+CT_ARCH_powerpc_AVAILABLE=y
+CT_ARCH_s390_AVAILABLE=y
+CT_ARCH_sh_AVAILABLE=y
+CT_ARCH_sparc_AVAILABLE=y
+CT_ARCH_x86_AVAILABLE=y
#
# Generic target options
@@ -178,24 +195,31 @@ CT_BUILD_SUFFIX=""
#
CT_KERNEL_SUPPORTS_SHARED_LIBS=y
CT_KERNEL="linux"
-CT_KERNEL_VERSION="3.5"
+CT_KERNEL_VERSION="3.6.3"
+# CT_KERNEL_bare_metal is not set
CT_KERNEL_linux=y
+CT_KERNEL_bare_metal_AVAILABLE=y
CT_KERNEL_linux_AVAILABLE=y
-CT_KERNEL_V_3_5=y
-# CT_KERNEL_V_3_4_7 is not set
+CT_KERNEL_V_3_6_3=y
+# CT_KERNEL_V_3_6_2 is not set
+# CT_KERNEL_V_3_6_1 is not set
+# CT_KERNEL_V_3_6 is not set
+# CT_KERNEL_V_3_5_7 is not set
+# CT_KERNEL_V_3_4_15 is not set
# CT_KERNEL_V_3_3_8 is not set
-# CT_KERNEL_V_3_2_25 is not set
+# CT_KERNEL_V_3_2_32 is not set
# CT_KERNEL_V_3_1_10 is not set
-# CT_KERNEL_V_3_0_39 is not set
+# CT_KERNEL_V_3_0_48 is not set
# CT_KERNEL_V_2_6_39_4 is not set
# CT_KERNEL_V_2_6_38_8 is not set
# CT_KERNEL_V_2_6_37_6 is not set
# CT_KERNEL_V_2_6_36_4 is not set
# CT_KERNEL_V_2_6_33_20 is not set
-# CT_KERNEL_V_2_6_32_59 is not set
+# CT_KERNEL_V_2_6_32_60 is not set
# CT_KERNEL_V_2_6_31_14 is not set
# CT_KERNEL_V_2_6_27_62 is not set
# CT_KERNEL_LINUX_CUSTOM is not set
+CT_KERNEL_mingw32_AVAILABLE=y
#
# Common kernel options
@@ -235,6 +259,7 @@ CT_BINUTILS_LINKER_LD=y
CT_BINUTILS_LINKERS_LIST="ld"
CT_BINUTILS_LINKER_DEFAULT="bfd"
CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
+# CT_BINUTILS_FOR_TARGET is not set
#
# C compiler
@@ -242,6 +267,7 @@ CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
CT_CC="gcc"
CT_CC_VERSION="4.4.6"
CT_CC_gcc=y
+# CT_CC_V_4_7_2 is not set
# CT_CC_V_4_6_3 is not set
# CT_CC_V_4_6_2 is not set
# CT_CC_V_4_6_1 is not set
@@ -323,6 +349,8 @@ CT_CC_GCC_LDBL_128=m
CT_LIBC="eglibc"
CT_LIBC_VERSION="2_12"
CT_LIBC_eglibc=y
+# CT_LIBC_glibc is not set
+# CT_LIBC_uClibc is not set
CT_LIBC_eglibc_AVAILABLE=y
# CT_LIBC_EGLIBC_V_2_16 is not set
# CT_LIBC_EGLIBC_V_2_15 is not set
@@ -343,6 +371,11 @@ CT_EGLIBC_REVISION="HEAD"
# CT_EGLIBC_CHECKOUT is not set
CT_EGLIBC_OPT_SIZE=y
# CT_EGLIBC_CUSTOM_CONFIG is not set
+CT_LIBC_glibc_AVAILABLE=y
+CT_LIBC_mingw_AVAILABLE=y
+CT_LIBC_newlib_AVAILABLE=y
+CT_LIBC_none_AVAILABLE=y
+CT_LIBC_uClibc_AVAILABLE=y
CT_LIBC_SUPPORT_THREADS_ANY=y
CT_LIBC_SUPPORT_NPTL=y
CT_LIBC_SUPPORT_LINUXTHREADS=y
@@ -393,12 +426,16 @@ CT_LIBC_ADDONS_LIST=""
# CT_LIBC_GLIBC_KERNEL_VERSION_NONE is not set
CT_LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS=y
# CT_LIBC_GLIBC_KERNEL_VERSION_CHOSEN is not set
-CT_LIBC_GLIBC_MIN_KERNEL="3.5"
+CT_LIBC_GLIBC_MIN_KERNEL="3.6.3"
#
# Debug facilities
#
+# CT_DEBUG_dmalloc is not set
+# CT_DEBUG_duma is not set
# CT_DEBUG_gdb is not set
+# CT_DEBUG_ltrace is not set
+# CT_DEBUG_strace is not set
#
# Companion libraries
diff --git a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-glibc b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-glibc
index 3910bdb..026c7fd 100644
--- a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-glibc
+++ b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-glibc
@@ -1,12 +1,10 @@
#
# Automatically generated make config: don't edit
-# crosstool-NG 1.16.0 Configuration
-# Sun Aug 5 21:39:12 2012
+# crosstool-NG 1.17.0 Configuration
+# Mon Dec 3 20:16:52 2012
#
CT_CONFIGURE_has_xz=y
-CT_CONFIGURE_has_cvs=y
CT_CONFIGURE_has_svn=y
-CT_BACKEND=y
CT_MODULES=y
#
@@ -18,15 +16,16 @@ CT_MODULES=y
#
# CT_OBSOLETE is not set
# CT_EXPERIMENTAL is not set
+# CT_DEBUG_CT is not set
#
# Paths
#
CT_LOCAL_TARBALLS_DIR=""
-CT_SAVE_TARBALLS=y
CT_WORK_DIR="${CT_TOP_DIR}/.build"
CT_PREFIX_DIR=""
CT_INSTALL_DIR="${CT_PREFIX_DIR}"
+CT_RM_RF_PREFIX_DIR=y
CT_REMOVE_DOCS=y
# CT_INSTALL_DIR_RO is not set
# CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES is not set
@@ -58,16 +57,15 @@ CT_PATCH_ORDER="bundled"
#
# Build behavior
#
-
-#
-# Build options hiden
-#
CT_PARALLEL_JOBS=0
CT_LOAD=0
CT_USE_PIPES=y
CT_EXTRA_FLAGS_FOR_HOST=""
-CT_CONFIG_SHELL_CUSTOM_PATH="/bin/sh"
-CT_CONFIG_SHELL="/bin/sh"
+# CT_CONFIG_SHELL_SH is not set
+# CT_CONFIG_SHELL_ASH is not set
+CT_CONFIG_SHELL_BASH=y
+# CT_CONFIG_SHELL_CUSTOM is not set
+CT_CONFIG_SHELL="${bash}"
#
# Logging
@@ -111,8 +109,27 @@ CT_ARCH_BITNESS=32
CT_ARCH_FLOAT_SW=y
CT_TARGET_CFLAGS=""
CT_TARGET_LDFLAGS=""
+# CT_ARCH_alpha is not set
CT_ARCH_arm=y
+# CT_ARCH_avr32 is not set
+# CT_ARCH_blackfin is not set
+# CT_ARCH_mips is not set
+# CT_ARCH_powerpc is not set
+# CT_ARCH_sh is not set
+# CT_ARCH_sparc is not set
+# CT_ARCH_x86 is not set
+CT_ARCH_alpha_AVAILABLE=y
CT_ARCH_arm_AVAILABLE=y
+CT_ARCH_avr32_AVAILABLE=y
+CT_ARCH_blackfin_AVAILABLE=y
+CT_ARCH_m68k_AVAILABLE=y
+CT_ARCH_microblaze_AVAILABLE=y
+CT_ARCH_mips_AVAILABLE=y
+CT_ARCH_powerpc_AVAILABLE=y
+CT_ARCH_s390_AVAILABLE=y
+CT_ARCH_sh_AVAILABLE=y
+CT_ARCH_sparc_AVAILABLE=y
+CT_ARCH_x86_AVAILABLE=y
#
# Generic target options
@@ -178,24 +195,31 @@ CT_BUILD_SUFFIX=""
#
CT_KERNEL_SUPPORTS_SHARED_LIBS=y
CT_KERNEL="linux"
-CT_KERNEL_VERSION="3.5"
+CT_KERNEL_VERSION="3.6.3"
+# CT_KERNEL_bare_metal is not set
CT_KERNEL_linux=y
+CT_KERNEL_bare_metal_AVAILABLE=y
CT_KERNEL_linux_AVAILABLE=y
-CT_KERNEL_V_3_5=y
-# CT_KERNEL_V_3_4_7 is not set
+CT_KERNEL_V_3_6_3=y
+# CT_KERNEL_V_3_6_2 is not set
+# CT_KERNEL_V_3_6_1 is not set
+# CT_KERNEL_V_3_6 is not set
+# CT_KERNEL_V_3_5_7 is not set
+# CT_KERNEL_V_3_4_15 is not set
# CT_KERNEL_V_3_3_8 is not set
-# CT_KERNEL_V_3_2_25 is not set
+# CT_KERNEL_V_3_2_32 is not set
# CT_KERNEL_V_3_1_10 is not set
-# CT_KERNEL_V_3_0_39 is not set
+# CT_KERNEL_V_3_0_48 is not set
# CT_KERNEL_V_2_6_39_4 is not set
# CT_KERNEL_V_2_6_38_8 is not set
# CT_KERNEL_V_2_6_37_6 is not set
# CT_KERNEL_V_2_6_36_4 is not set
# CT_KERNEL_V_2_6_33_20 is not set
-# CT_KERNEL_V_2_6_32_59 is not set
+# CT_KERNEL_V_2_6_32_60 is not set
# CT_KERNEL_V_2_6_31_14 is not set
# CT_KERNEL_V_2_6_27_62 is not set
# CT_KERNEL_LINUX_CUSTOM is not set
+CT_KERNEL_mingw32_AVAILABLE=y
#
# Common kernel options
@@ -235,6 +259,7 @@ CT_BINUTILS_LINKER_LD=y
CT_BINUTILS_LINKERS_LIST="ld"
CT_BINUTILS_LINKER_DEFAULT="bfd"
CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
+# CT_BINUTILS_FOR_TARGET is not set
#
# C compiler
@@ -242,6 +267,7 @@ CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
CT_CC="gcc"
CT_CC_VERSION="4.4.6"
CT_CC_gcc=y
+# CT_CC_V_4_7_2 is not set
# CT_CC_V_4_6_3 is not set
# CT_CC_V_4_6_2 is not set
# CT_CC_V_4_6_1 is not set
@@ -322,9 +348,11 @@ CT_CC_GCC_LDBL_128=m
#
CT_LIBC="glibc"
CT_LIBC_VERSION="2.9"
+# CT_LIBC_eglibc is not set
CT_LIBC_glibc=y
+# CT_LIBC_uClibc is not set
+CT_LIBC_eglibc_AVAILABLE=y
CT_LIBC_glibc_AVAILABLE=y
-CT_LIBC_GLIBC_TARBALL=y
# CT_LIBC_GLIBC_V_2_14_1 is not set
# CT_LIBC_GLIBC_V_2_14 is not set
# CT_LIBC_GLIBC_V_2_13 is not set
@@ -335,6 +363,10 @@ CT_LIBC_GLIBC_TARBALL=y
# CT_LIBC_GLIBC_V_2_10_1 is not set
CT_LIBC_GLIBC_V_2_9=y
# CT_LIBC_GLIBC_V_2_8 is not set
+CT_LIBC_mingw_AVAILABLE=y
+CT_LIBC_newlib_AVAILABLE=y
+CT_LIBC_none_AVAILABLE=y
+CT_LIBC_uClibc_AVAILABLE=y
CT_LIBC_SUPPORT_THREADS_ANY=y
CT_LIBC_SUPPORT_NPTL=y
CT_THREADS="nptl"
@@ -359,7 +391,7 @@ CT_LIBC_ADDONS_LIST=""
# CT_LIBC_GLIBC_KERNEL_VERSION_NONE is not set
CT_LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS=y
# CT_LIBC_GLIBC_KERNEL_VERSION_CHOSEN is not set
-CT_LIBC_GLIBC_MIN_KERNEL="3.5"
+CT_LIBC_GLIBC_MIN_KERNEL="3.6.3"
#
# glibc other options
@@ -388,7 +420,11 @@ CT_LIBC_GLIBC_MIN_KERNEL="3.5"
#
# Debug facilities
#
+# CT_DEBUG_dmalloc is not set
+# CT_DEBUG_duma is not set
# CT_DEBUG_gdb is not set
+# CT_DEBUG_ltrace is not set
+# CT_DEBUG_strace is not set
#
# Companion libraries
diff --git a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-uClibc b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-uClibc
index 5155e6c..8ad481f 100644
--- a/toolchain/toolchain-crosstool-ng/crosstool-ng.config-uClibc
+++ b/toolchain/toolchain-crosstool-ng/crosstool-ng.config-uClibc
@@ -1,12 +1,10 @@
#
# Automatically generated make config: don't edit
-# crosstool-NG 1.16.0 Configuration
-# Sun Aug 5 17:33:46 2012
+# crosstool-NG 1.17.0 Configuration
+# Mon Dec 3 20:17:58 2012
#
CT_CONFIGURE_has_xz=y
-CT_CONFIGURE_has_cvs=y
CT_CONFIGURE_has_svn=y
-CT_BACKEND=y
CT_MODULES=y
#
@@ -18,15 +16,16 @@ CT_MODULES=y
#
# CT_OBSOLETE is not set
# CT_EXPERIMENTAL is not set
+# CT_DEBUG_CT is not set
#
# Paths
#
CT_LOCAL_TARBALLS_DIR=""
-CT_SAVE_TARBALLS=y
CT_WORK_DIR="${CT_TOP_DIR}/.build"
CT_PREFIX_DIR=""
CT_INSTALL_DIR="${CT_PREFIX_DIR}"
+CT_RM_RF_PREFIX_DIR=y
CT_REMOVE_DOCS=y
# CT_INSTALL_DIR_RO is not set
# CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES is not set
@@ -58,16 +57,15 @@ CT_PATCH_ORDER="bundled"
#
# Build behavior
#
-
-#
-# Build options hiden
-#
CT_PARALLEL_JOBS=0
CT_LOAD=0
CT_USE_PIPES=y
CT_EXTRA_FLAGS_FOR_HOST=""
-CT_CONFIG_SHELL_CUSTOM_PATH="/bin/sh"
-CT_CONFIG_SHELL="/bin/sh"
+# CT_CONFIG_SHELL_SH is not set
+# CT_CONFIG_SHELL_ASH is not set
+CT_CONFIG_SHELL_BASH=y
+# CT_CONFIG_SHELL_CUSTOM is not set
+CT_CONFIG_SHELL="${bash}"
#
# Logging
@@ -111,8 +109,27 @@ CT_ARCH_BITNESS=32
CT_ARCH_FLOAT_SW=y
CT_TARGET_CFLAGS=""
CT_TARGET_LDFLAGS=""
+# CT_ARCH_alpha is not set
CT_ARCH_arm=y
+# CT_ARCH_avr32 is not set
+# CT_ARCH_blackfin is not set
+# CT_ARCH_mips is not set
+# CT_ARCH_powerpc is not set
+# CT_ARCH_sh is not set
+# CT_ARCH_sparc is not set
+# CT_ARCH_x86 is not set
+CT_ARCH_alpha_AVAILABLE=y
CT_ARCH_arm_AVAILABLE=y
+CT_ARCH_avr32_AVAILABLE=y
+CT_ARCH_blackfin_AVAILABLE=y
+CT_ARCH_m68k_AVAILABLE=y
+CT_ARCH_microblaze_AVAILABLE=y
+CT_ARCH_mips_AVAILABLE=y
+CT_ARCH_powerpc_AVAILABLE=y
+CT_ARCH_s390_AVAILABLE=y
+CT_ARCH_sh_AVAILABLE=y
+CT_ARCH_sparc_AVAILABLE=y
+CT_ARCH_x86_AVAILABLE=y
#
# Generic target options
@@ -178,24 +195,31 @@ CT_BUILD_SUFFIX=""
#
CT_KERNEL_SUPPORTS_SHARED_LIBS=y
CT_KERNEL="linux"
-CT_KERNEL_VERSION="3.5"
+CT_KERNEL_VERSION="3.6.3"
+# CT_KERNEL_bare_metal is not set
CT_KERNEL_linux=y
+CT_KERNEL_bare_metal_AVAILABLE=y
CT_KERNEL_linux_AVAILABLE=y
-CT_KERNEL_V_3_5=y
-# CT_KERNEL_V_3_4_7 is not set
+CT_KERNEL_V_3_6_3=y
+# CT_KERNEL_V_3_6_2 is not set
+# CT_KERNEL_V_3_6_1 is not set
+# CT_KERNEL_V_3_6 is not set
+# CT_KERNEL_V_3_5_7 is not set
+# CT_KERNEL_V_3_4_15 is not set
# CT_KERNEL_V_3_3_8 is not set
-# CT_KERNEL_V_3_2_25 is not set
+# CT_KERNEL_V_3_2_32 is not set
# CT_KERNEL_V_3_1_10 is not set
-# CT_KERNEL_V_3_0_39 is not set
+# CT_KERNEL_V_3_0_48 is not set
# CT_KERNEL_V_2_6_39_4 is not set
# CT_KERNEL_V_2_6_38_8 is not set
# CT_KERNEL_V_2_6_37_6 is not set
# CT_KERNEL_V_2_6_36_4 is not set
# CT_KERNEL_V_2_6_33_20 is not set
-# CT_KERNEL_V_2_6_32_59 is not set
+# CT_KERNEL_V_2_6_32_60 is not set
# CT_KERNEL_V_2_6_31_14 is not set
# CT_KERNEL_V_2_6_27_62 is not set
# CT_KERNEL_LINUX_CUSTOM is not set
+CT_KERNEL_mingw32_AVAILABLE=y
#
# Common kernel options
@@ -234,6 +258,7 @@ CT_BINUTILS_LINKER_LD=y
CT_BINUTILS_LINKERS_LIST="ld"
CT_BINUTILS_LINKER_DEFAULT="bfd"
CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
+# CT_BINUTILS_FOR_TARGET is not set
#
# C compiler
@@ -241,6 +266,7 @@ CT_BINUTILS_EXTRA_CONFIG_ARRAY=""
CT_CC="gcc"
CT_CC_VERSION="4.4.6"
CT_CC_gcc=y
+# CT_CC_V_4_7_2 is not set
# CT_CC_V_4_6_3 is not set
# CT_CC_V_4_6_2 is not set
# CT_CC_V_4_6_1 is not set
@@ -321,7 +347,14 @@ CT_CC_GCC_LDBL_128=m
#
CT_LIBC="uClibc"
CT_LIBC_VERSION="0.9.33.2"
+# CT_LIBC_eglibc is not set
+# CT_LIBC_glibc is not set
CT_LIBC_uClibc=y
+CT_LIBC_eglibc_AVAILABLE=y
+CT_LIBC_glibc_AVAILABLE=y
+CT_LIBC_mingw_AVAILABLE=y
+CT_LIBC_newlib_AVAILABLE=y
+CT_LIBC_none_AVAILABLE=y
CT_LIBC_uClibc_AVAILABLE=y
CT_LIBC_UCLIBC_V_0_9_33_2=y
# CT_LIBC_UCLIBC_V_0_9_33_1 is not set
@@ -369,7 +402,11 @@ CT_LIBC_UCLIBC_WCHAR=y
#
# Debug facilities
#
+# CT_DEBUG_dmalloc is not set
+# CT_DEBUG_duma is not set
# CT_DEBUG_gdb is not set
+# CT_DEBUG_ltrace is not set
+# CT_DEBUG_strace is not set
#
# Companion libraries
--
1.7.10.4
^ permalink raw reply related
* [Buildroot] [PATCH 0/1] Update Crosstool-NG to 1.17.0
From: Carsten Schoenert @ 2012-12-03 19:47 UTC (permalink / raw)
To: buildroot
Hello,
this is an update for the package crosstool-ng to 1.17.0.
Yann wrote he didn't try to push the latest version of crosstool-ng to
buildroot because it was to late. Here are the my try to send a
patch to improve the usage of buildroot.
If something is still wrong, please let me know, this is my first
contribution to buildroot.
Sp far I can test it here the build of a gcc 4.7.2 for armv6 for
cxa2450x CPU from Nexperia is working here.
Regards
Carsten
^ permalink raw reply
* [Buildroot] [PATCH 14/14] ltrace: bump to version 0.7.1
From: Thomas Petazzoni @ 2012-12-03 18:52 UTC (permalink / raw)
To: buildroot
In-Reply-To: <50BCEC3F.2090300@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 03 Dec 2012 15:15:27 -0300, Gustavo Zacarias wrote:
> On 12/03/2012 01:45 PM, Thomas Petazzoni wrote:
>
> > And, unrelated to the commit itself, did you try this ltrace version? I
> > have never been able to get ltrace 0.6 to work on ARM/uClibc.
>
> It still seems broken unfortunately :-/
Ok, too bad. Thanks a lot for testing, though!
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 14/14] ltrace: bump to version 0.7.1
From: Gustavo Zacarias @ 2012-12-03 18:15 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121203174545.475969fe@skate>
On 12/03/2012 01:45 PM, Thomas Petazzoni wrote:
> And, unrelated to the commit itself, did you try this ltrace version? I
> have never been able to get ltrace 0.6 to work on ARM/uClibc.
It still seems broken unfortunately :-/
Regards.
^ permalink raw reply
* [Buildroot] [PATCH 05/51] package/libiscsi: new package
From: Yann E. MORIN @ 2012-12-03 18:11 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121129093925.69619997@skate>
Thomas, All,
On Thursday 29 November 2012 Thomas Petazzoni wrote:
> On Thu, 29 Nov 2012 00:54:04 +0100, Yann E. MORIN wrote:
> > +LIBISCSI_AUTORECONF = YES
> > +# Having a m4/ directory is mandatory for autoreconf to work
> > +define LIBISCSI_CREATE_M4_DIR
> > + mkdir -p $(@D)/m4
> > +endef
> > +LIBISCSI_PRE_CONFIGURE_HOOKS += LIBISCSI_CREATE_M4_DIR
>
> I think the reason why AUTORECONF=YES is needed should be mention with
> a comment on top of it. You don't have any patch touching
> configure.{ac,in} or Makefile.am, so the need for AUTORECONF=YES
> doesn't seem very obvious.
Works like a charm without autoreconf. Probably a leftover from debugging
the initial packaging. Thanks!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply
* [Buildroot] [PATCH 03/51] package/dtc: add option to install programs
From: Yann E. MORIN @ 2012-12-03 18:10 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121129094031.3173b9a0@skate>
Thomas, All,
On Thursday 29 November 2012 Thomas Petazzoni wrote:
> On Thu, 29 Nov 2012 00:54:02 +0100, Yann E. MORIN wrote:
> > There is some (minor?) issues wrt the licensing terms.
> > The libfdt library is dual-licensed GPLv2+/BSD-2c, and the
> > executables are licensed GPLv2+.
> >
> > There is no way in BR to properly convey this information.
> > So I decided to add some explanatory comments in the .mk
> > file, in retaliation. ;-)
>
> As per the discussion during the Developers Days, there is now a way to
> convey this information. From the report:
>
> multiple licenses: we don't want to make things very complex. It
> doesn't have to be machine-readable (we don't need to support
> machine analysis of the license field), so we don't have to
> formally decide how the license text must be written. It does make
> sense to have some convention, though. Proposal: "GPLv2+ or BSD-2c
> for the library, GPLv2+ for the dtc executable".
Right-o-right, I forgot that. Thanks for reminding me. :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply
* [Buildroot] no crosstool-ng 1.17.0 in 2012.11
From: Carsten Schoenert @ 2012-12-03 18:03 UTC (permalink / raw)
To: buildroot
In-Reply-To: <201212031745.59827.yann.morin.1998@free.fr>
Hello Yann, Thomas,
Am 03.12.2012 17:45, schrieb Yann E. MORIN:
> crosstool-NG 1.17.0 was released too late for inclusion in buildroot 2012.11.
> I did not even try to update it.
o.k. that's the explanation. ;)
> If all goes well, I'll push the next ct-ng version in time for inclusion in
> the next BR release.
>
> Hopefully, all will go well, but there's FOSDEM at just about the time the
> next release of ct-ng is due. So, we'll see... :-/
Yes, FOSDEM in the cold city of Brussels. I'll be there.
> Alternatively, interested users ( eg. you! ;-) ) can post a patch! ;-)
I will do, right now a arm gcc 4.7.2 is builded. I will before checking
some things inside my branch. Until now everything work well, even the
compiler warnings are gone while cross compiler is building. ;)
Regards
Carsten
^ permalink raw reply
* [Buildroot] [PATCH 14/14] ltrace: bump to version 0.7.1
From: Gustavo Zacarias @ 2012-12-03 16:48 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121203174545.475969fe@skate>
On 12/03/2012 01:45 PM, Thomas Petazzoni wrote:
> Dear Gustavo Zacarias,
>
> On Mon, 3 Dec 2012 11:46:12 -0300, Gustavo Zacarias wrote:
>
>> config BR2_PACKAGE_LTRACE
>> bool "ltrace"
>> - depends on !(BR2_avr32 || BR2_mips || BR2_mipsel || BR2_sh || BR2_sh64)
>> - depends on !BR2_xtensa
>> + depends on !(BR2_avr32 || BR2_mips || BR2_sh || BR2_sh64 || BR2_xtensa)
>> select BR2_PACKAGE_LIBELF
>
> So now ltrace supports mipsel ?
Oh yes, qemu mipsel tested.
> When there are more changes than just bumping the version name, like
> changes in patches and other things, it'd be nice to have a slightly
> more elaborate commit log.
Yes, i could be more verbose, noted.
> And, unrelated to the commit itself, did you try this ltrace version? I
> have never been able to get ltrace 0.6 to work on ARM/uClibc.
I didn't run test it on ARM, just mipsel to really verify it and ppc to
see that it wasn't broken (and it was, hence the new ppc patch).
I'll fire up a arm qemu build to test it.
Regards.
^ permalink raw reply
* [Buildroot] no crosstool-ng 1.17.0 in 2012.11
From: Yann E. MORIN @ 2012-12-03 16:45 UTC (permalink / raw)
To: buildroot
In-Reply-To: <50BCD509.4050508@googlemail.com>
Carsten, All,
On Monday 03 December 2012 17:36:25 Carsten Schoenert wrote:
> I was hoping that the current crosstool-ng version 1.17.0 would be
> placed into buildroot 1012.11.
> Any special reason why crosstool-ng is still 1.16.0 or was it just
> forgotten to update? :)
crosstool-NG 1.17.0 was released too late for inclusion in buildroot 2012.11.
I did not even try to update it.
If all goes well, I'll push the next ct-ng version in time for inclusion in
the next BR release.
Hopefully, all will go well, but there's FOSDEM at just about the time the
next release of ct-ng is due. So, we'll see... :-/
Alternatively, interested users ( eg. you! ;-) ) can post a patch! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
^ permalink raw reply
* [Buildroot] [PATCH 14/14] ltrace: bump to version 0.7.1
From: Thomas Petazzoni @ 2012-12-03 16:45 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354545972-26783-14-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 3 Dec 2012 11:46:12 -0300, Gustavo Zacarias wrote:
> config BR2_PACKAGE_LTRACE
> bool "ltrace"
> - depends on !(BR2_avr32 || BR2_mips || BR2_mipsel || BR2_sh || BR2_sh64)
> - depends on !BR2_xtensa
> + depends on !(BR2_avr32 || BR2_mips || BR2_sh || BR2_sh64 || BR2_xtensa)
> select BR2_PACKAGE_LIBELF
So now ltrace supports mipsel ?
When there are more changes than just bumping the version name, like
changes in patches and other things, it'd be nice to have a slightly
more elaborate commit log.
And, unrelated to the commit itself, did you try this ltrace version? I
have never been able to get ltrace 0.6 to work on ARM/uClibc.
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] no crosstool-ng 1.17.0 in 2012.11
From: Thomas Petazzoni @ 2012-12-03 16:43 UTC (permalink / raw)
To: buildroot
In-Reply-To: <50BCD509.4050508@googlemail.com>
Dear Carsten Schoenert,
On Mon, 03 Dec 2012 17:36:25 +0100, Carsten Schoenert wrote:
> as I can see the new stable release 2012.11 of buildroot was releasd.
>
> I was hoping that the current crosstool-ng version 1.17.0 would be
> placed into buildroot 1012.11.
> Any special reason why crosstool-ng is still 1.16.0 or was it just
> forgotten to update? :)
Possibly because we didn't receive your patch to make this change? :-)
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 10/13] Add update-all-config target
From: Thomas Petazzoni @ 2012-12-03 16:41 UTC (permalink / raw)
To: buildroot
In-Reply-To: <50BCB4A3.5080003@relinux.de>
Dear Stephan Hoffmann,
On Mon, 03 Dec 2012 15:18:11 +0100, Stephan Hoffmann wrote:
> I'd like to go one step further and put buildroot's default config files
> in the board/company/product hierarchy, too. Then everything would be in
> one place.
This is what we had a long time ago, but it was changed for the current
approach.
See the discussion at
http://lists.busybox.net/pipermail/buildroot/2009-October/029556.html
(note: the discussion starts on October 2009, but continues on November
2009, and the mailing list archive doesn't show it as one single
thread).
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] no crosstool-ng 1.17.0 in 2012.11
From: Carsten Schoenert @ 2012-12-03 16:36 UTC (permalink / raw)
To: buildroot
Hello,
as I can see the new stable release 2012.11 of buildroot was releasd.
I was hoping that the current crosstool-ng version 1.17.0 would be
placed into buildroot 1012.11.
Any special reason why crosstool-ng is still 1.16.0 or was it just
forgotten to update? :)
Regards
Carsten
^ permalink raw reply
* [Buildroot] [PATCH 4/4] lua: support linenoise
From: Francois Perrad @ 2012-12-03 16:12 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354551135-30056-1-git-send-email-francois.perrad@gadz.org>
Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
---
package/lua/Config.in | 17 +++++++++++++++++
package/lua/lua-11-linenoise.patch | 24 ++++++++++++++++++++++++
package/lua/lua.mk | 8 +++++++-
3 files changed, 48 insertions(+), 1 deletion(-)
create mode 100644 package/lua/lua-11-linenoise.patch
diff --git a/package/lua/Config.in b/package/lua/Config.in
index 8233e2a..4166730 100644
--- a/package/lua/Config.in
+++ b/package/lua/Config.in
@@ -7,6 +7,15 @@ config BR2_PACKAGE_LUA
if BR2_PACKAGE_LUA
+choice
+ prompt "Lua Interpreter command-line editing"
+ default BR2_PACKAGE_LUA_INTERPRETER_EDITING_NONE
+
+config BR2_PACKAGE_LUA_INTERPRETER_EDITING_NONE
+ bool "none"
+ help
+ None.
+
config BR2_PACKAGE_LUA_INTERPRETER_READLINE
bool "readline support"
select BR2_PACKAGE_READLINE
@@ -14,4 +23,12 @@ config BR2_PACKAGE_LUA_INTERPRETER_READLINE
help
Enables command-line editing in the lua interpreter.
+config BR2_PACKAGE_LUA_INTERPRETER_LINENOISE
+ bool "linenoise support"
+ select BR2_PACKAGE_LINENOISE
+ help
+ Enables command-line editing in the lua interpreter.
+
+endchoice
+
endif
diff --git a/package/lua/lua-11-linenoise.patch b/package/lua/lua-11-linenoise.patch
new file mode 100644
index 0000000..488c080
--- /dev/null
+++ b/package/lua/lua-11-linenoise.patch
@@ -0,0 +1,24 @@
+Add support of linenoise (replace readline)
+
+see discussion, http://lua-users.org/lists/lua-l/2010-03/msg00879.html
+
+Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
+
+Index: b/src/luaconf.h
+===================================================================
+--- a/src/luaconf.h
++++ b/src/luaconf.h
+@@ -279,6 +279,13 @@
+ if (lua_strlen(L,idx) > 0) /* non-empty line? */ \
+ add_history(lua_tostring(L, idx)); /* add it to history */
+ #define lua_freeline(L,b) ((void)L, free(b))
++#elif defined(LUA_USE_LINENOISE)
++#include <linenoise.h>
++#define lua_readline(L,b,p) ((void)L, ((b)=linenoise(p)) != NULL)
++#define lua_saveline(L,idx) \
++ if (lua_strlen(L,idx) > 0) /* non-empty line? */ \
++ linenoiseHistoryAdd(lua_tostring(L, idx)); /* add it to history */
++#define lua_freeline(L,b) ((void)L, free(b))
+ #else
+ #define lua_readline(L,b,p) \
+ ((void)L, fputs(p, stdout), fflush(stdout), /* show prompt */ \
diff --git a/package/lua/lua.mk b/package/lua/lua.mk
index 9e0d387..32acc99 100644
--- a/package/lua/lua.mk
+++ b/package/lua/lua.mk
@@ -16,10 +16,16 @@ LUA_MYLIBS += -ldl
ifeq ($(BR2_PACKAGE_LUA_INTERPRETER_READLINE),y)
LUA_DEPENDENCIES = readline ncurses
LUA_MYLIBS += -lreadline -lhistory -lncurses
- LUA_CFLAGS += -DLUA_USE_LINUX
+ LUA_CFLAGS += -DLUA_USE_POSIX -DLUA_USE_DLOPEN -DLUA_USE_READLINE
+else
+ifeq ($(BR2_PACKAGE_LUA_INTERPRETER_LINENOISE),y)
+ LUA_DEPENDENCIES = linenoise
+ LUA_MYLIBS += -llinenoise
+ LUA_CFLAGS += -DLUA_USE_POSIX -DLUA_USE_DLOPEN -DLUA_USE_LINENOISE
else
LUA_CFLAGS += -DLUA_USE_POSIX -DLUA_USE_DLOPEN
endif
+endif
# We never want to have host-readline and host-ncurses as dependencies
# of host-lua.
--
1.7.9.5
^ permalink raw reply related
* [Buildroot] [PATCH 3/4] linenoise: new package
From: Francois Perrad @ 2012-12-03 16:12 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354551135-30056-1-git-send-email-francois.perrad@gadz.org>
Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
---
package/Config.in | 1 +
package/linenoise/Config.in | 6 ++++
package/linenoise/linenoise-get-columns.patch | 17 ++++++++++
package/linenoise/linenoise.mk | 45 +++++++++++++++++++++++++
4 files changed, 69 insertions(+)
create mode 100644 package/linenoise/Config.in
create mode 100644 package/linenoise/linenoise-get-columns.patch
create mode 100644 package/linenoise/linenoise.mk
diff --git a/package/Config.in b/package/Config.in
index 5ba1f05..6117716 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -523,6 +523,7 @@ menu "Text and terminal handling"
source "package/enchant/Config.in"
source "package/icu/Config.in"
source "package/libiconv/Config.in"
+source "package/linenoise/Config.in"
source "package/ncurses/Config.in"
source "package/newt/Config.in"
source "package/pcre/Config.in"
diff --git a/package/linenoise/Config.in b/package/linenoise/Config.in
new file mode 100644
index 0000000..8e4ab91
--- /dev/null
+++ b/package/linenoise/Config.in
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_LINENOISE
+ bool "linenoise"
+ help
+ A small self-contained alternative to readline and libedit
+
+ https://github.com/antirez/linenoise
diff --git a/package/linenoise/linenoise-get-columns.patch b/package/linenoise/linenoise-get-columns.patch
new file mode 100644
index 0000000..180d1c3
--- /dev/null
+++ b/package/linenoise/linenoise-get-columns.patch
@@ -0,0 +1,17 @@
+see http://github.com/antirez/linenoise/pull/31
+
+Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
+
+Index: b/linenoise.c
+===================================================================
+--- a/linenoise.c
++++ b/linenoise.c
+@@ -182,7 +182,7 @@
+ static int getColumns(void) {
+ struct winsize ws;
+
+- if (ioctl(1, TIOCGWINSZ, &ws) == -1) return 80;
++ if (ioctl(1, TIOCGWINSZ, &ws) == -1 || ws.ws_col == 0) return 80;
+ return ws.ws_col;
+ }
+
diff --git a/package/linenoise/linenoise.mk b/package/linenoise/linenoise.mk
new file mode 100644
index 0000000..e7b6124
--- /dev/null
+++ b/package/linenoise/linenoise.mk
@@ -0,0 +1,45 @@
+#############################################################
+#
+# linenoise
+#
+#############################################################
+LINENOISE_VERSION = g8c9b481
+LINENOISE_SITE = http://github.com/antirez/linenoise/tarball/master
+LINENOISE_LICENSE = BSD-2c
+LINENOISE_INSTALL_STAGING = YES
+
+define LINENOISE_BUILD_CMDS
+ cd $(@D); $(TARGET_CC) $(TARGET_CFLAGS) -c linenoise.c
+ cd $(@D); $(TARGET_AR) rcu liblinenoise.a linenoise.o
+ cd $(@D); $(TARGET_CC) $(TARGET_CFLAGS) -o linenoise_example example.c -L. -llinenoise
+endef
+
+define LINENOISE_INSTALL_STAGING_CMDS
+ $(INSTALL) -m 644 -D $(@D)/linenoise.h $(STAGING_DIR)/usr/include/linenoise.h
+ $(INSTALL) -m 644 -D $(@D)/liblinenoise.a $(STAGING_DIR)/usr/lib/liblinenoise.a
+ $(INSTALL) -m 755 -D $(@D)/linenoise_example $(STAGING_DIR)/usr/bin/linenoise_example
+endef
+
+define LINENOISE_UNINSTALL_STAGING_CMDS
+ rm -f $(STAGING_DIR)/usr/include/linenoise.h
+ rm -f $(STAGING_DIR)/usr/lib/liblinenoise.a
+ rm -f $(STAGING_DIR)/usr/bin/linenoise_example
+endef
+
+define LINENOISE_INSTALL_TARGET_CMDS
+ $(INSTALL) -m 644 -D $(@D)/linenoise.h $(TARGET_DIR)/usr/include/linenoise.h
+ $(INSTALL) -m 644 -D $(@D)/liblinenoise.a $(TARGET_DIR)/usr/lib/liblinenoise.a
+ $(INSTALL) -m 755 -D $(@D)/linenoise_example $(TARGET_DIR)/usr/bin/linenoise_example
+endef
+
+define LINENOISE_UNINSTALL_TARGET_CMDS
+ rm -f $(TARGET_DIR)/usr/include/linenoise.h
+ rm -f $(TARGET_DIR)/usr/lib/liblinenoise.a
+ rm -f $(TARGET_DIR)/usr/bin/linenoise_example
+endef
+
+define LINENOISE_CLEAN_CMDS
+ rm -f $(@D)/*.o $(@D)/*.a $(@D)/linenoise_example
+endef
+
+$(eval $(generic-package))
--
1.7.9.5
^ permalink raw reply related
* [Buildroot] [PATCH 2/4] luajit: bump to version 2.0.0
From: Francois Perrad @ 2012-12-03 16:12 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354551135-30056-1-git-send-email-francois.perrad@gadz.org>
Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
---
package/luajit/luajit-01-root-path.patch | 2 +-
package/luajit/luajit-04-no-bin-symlink.patch | 18 ++----------------
package/luajit/luajit.mk | 2 +-
3 files changed, 4 insertions(+), 18 deletions(-)
diff --git a/package/luajit/luajit-01-root-path.patch b/package/luajit/luajit-01-root-path.patch
index 80ad1e9..cc2f04f 100644
--- a/package/luajit/luajit-01-root-path.patch
+++ b/package/luajit/luajit-01-root-path.patch
@@ -18,5 +18,5 @@ Index: b/src/luaconf.h
+#define LUA_LDIR LUA_ROOT "share/lua/"
+#define LUA_CDIR LUA_ROOT "lib/lua/"
#ifdef LUA_XROOT
- #define LUA_JDIR LUA_XROOT "share/luajit-2.0.0-beta11/"
+ #define LUA_JDIR LUA_XROOT "share/luajit-2.0.0/"
#define LUA_XPATH \
diff --git a/package/luajit/luajit-04-no-bin-symlink.patch b/package/luajit/luajit-04-no-bin-symlink.patch
index 91a470a..0de3162 100644
--- a/package/luajit/luajit-04-no-bin-symlink.patch
+++ b/package/luajit/luajit-04-no-bin-symlink.patch
@@ -6,7 +6,7 @@ Index: b/Makefile
===================================================================
--- a/Makefile
+++ b/Makefile
-@@ -43,8 +43,7 @@
+@@ -42,8 +42,7 @@
INSTALL_MAN= $(INSTALL_SHARE)/man/man1
INSTALL_PKGCONFIG= $(INSTALL_LIB)/pkgconfig
@@ -16,7 +16,7 @@ Index: b/Makefile
INSTALL_ANAME= libluajit-$(ABIVER).a
INSTALL_SONAME= libluajit-$(ABIVER).so.$(MAJVER).$(MINVER).$(RELVER)
INSTALL_SOSHORT= libluajit-$(ABIVER).so
-@@ -58,7 +57,6 @@
+@@ -57,7 +56,6 @@
INSTALL_SHORT1= $(INSTALL_LIB)/$(INSTALL_SOSHORT)
INSTALL_SHORT2= $(INSTALL_LIB)/$(INSTALL_SOSHORT)
INSTALL_T= $(INSTALL_BIN)/$(INSTALL_TNAME)
@@ -24,17 +24,3 @@ Index: b/Makefile
INSTALL_PC= $(INSTALL_PKGCONFIG)/$(INSTALL_PCNAME)
INSTALL_DIRS= $(INSTALL_BIN) $(INSTALL_LIB) $(INSTALL_INC) $(INSTALL_MAN) \
-@@ -120,13 +118,6 @@
- $(RM) $(FILE_PC).tmp
- cd src && $(INSTALL_F) $(FILES_INC) $(INSTALL_INC)
- cd src/jit && $(INSTALL_F) $(FILES_JITLIB) $(INSTALL_JITLIB)
-- @echo "==== Successfully installed LuaJIT $(VERSION) to $(PREFIX) ===="
-- @echo ""
-- @echo "Note: the beta releases deliberately do NOT install a symlink for luajit"
-- @echo "You can do this now by running this command (with sudo):"
-- @echo ""
-- @echo " $(SYMLINK) $(INSTALL_TNAME) $(INSTALL_TSYM)"
-- @echo ""
-
- uninstall:
- @echo "==== Uninstalling LuaJIT $(VERSION) from $(PREFIX) ===="
diff --git a/package/luajit/luajit.mk b/package/luajit/luajit.mk
index 2583f92..844122e 100644
--- a/package/luajit/luajit.mk
+++ b/package/luajit/luajit.mk
@@ -4,7 +4,7 @@
#
#############################################################
-LUAJIT_VERSION = 2.0.0-beta11
+LUAJIT_VERSION = 2.0.0
LUAJIT_SOURCE = LuaJIT-$(LUAJIT_VERSION).tar.gz
LUAJIT_SITE = http://luajit.org/download
LUAJIT_LICENSE = MIT
--
1.7.9.5
^ permalink raw reply related
* [Buildroot] [PATCH 1/4] perl: bump to version 5.16.2
From: Francois Perrad @ 2012-12-03 16:12 UTC (permalink / raw)
To: buildroot
Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
---
package/perl/perl.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/perl/perl.mk b/package/perl/perl.mk
index 391047d..a86ee2a 100644
--- a/package/perl/perl.mk
+++ b/package/perl/perl.mk
@@ -5,7 +5,7 @@
#############################################################
PERL_VERSION_MAJOR = 16
-PERL_VERSION = 5.$(PERL_VERSION_MAJOR).1
+PERL_VERSION = 5.$(PERL_VERSION_MAJOR).2
PERL_SITE = http://www.cpan.org/src/5.0
PERL_SOURCE = perl-$(PERL_VERSION).tar.bz2
PERL_LICENSE = Artistic
--
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