Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [PATCH] add new package fxload
From: Jérémy Rosen @ 2012-11-06 10:50 UTC (permalink / raw)
  To: buildroot

Signed-off-by: J?r?my Rosen <jeremy.rosen@openwide.fr>
---
v2: Incorporated comments from Arnout,

I am not sure about the make install target line,

I would have expected prefix= to be set by the environement, but maybe it is not a standard var name for make...
---
 package/Config.in        |    1 +
 package/fxload/Config.in |    9 +++++++++
 package/fxload/fxload.mk |   19 +++++++++++++++++++
 3 files changed, 29 insertions(+)
 create mode 100644 package/fxload/Config.in
 create mode 100644 package/fxload/fxload.mk

diff --git a/package/Config.in b/package/Config.in
index e531c41..bcd1b47 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -211,6 +211,7 @@ source "package/flashrom/Config.in"
 source "package/fconfig/Config.in"
 source "package/fis/Config.in"
 source "package/fmtools/Config.in"
+source "package/fxload/Config.in"
 source "package/gadgetfs-test/Config.in"
 source "package/gdisk/Config.in"
 source "package/gpsd/Config.in"
diff --git a/package/fxload/Config.in b/package/fxload/Config.in
new file mode 100644
index 0000000..ac190f0
--- /dev/null
+++ b/package/fxload/Config.in
@@ -0,0 +1,9 @@
+config BR2_PACKAGE_FXLOAD
+	bool "fxload"
+	help
+	  This program is conveniently able to download firmware into FX, FX2,
+	  and FX2LP EZ-USB devices, as well as the original AnchorChips EZ-USB.
+	  It is intended to be invoked by hotplug scripts when the unprogrammed
+	  device appears on the bus.
+
+	  http://sourceforge.net/projects/linux-hotplug/
diff --git a/package/fxload/fxload.mk b/package/fxload/fxload.mk
new file mode 100644
index 0000000..1b5e8c7
--- /dev/null
+++ b/package/fxload/fxload.mk
@@ -0,0 +1,19 @@
+#############################################################
+#
+# fxload
+#
+#############################################################
+FXLOAD_VERSION = 2008_10_13
+FXLOAD_SITE = http://downloads.sourceforge.net/project/linux-hotplug/fxload/$(FXLOAD_VERSION)
+FXLOAD_LICENSE = GPLv2+
+FXLOAD_LICENSE_FILE = COPYING
+
+define FXLOAD_BUILD_CMDS
+    $(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) all
+endef
+
+define FXLOAD_INSTALL_TARGET_CMDS
+    $(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) prefix=$(TARGET_DIR) -C $(@D) install
+endef
+
+$(eval $(generic-package))
-- 
1.7.10.4

^ permalink raw reply related
* [Buildroot] [git commit] kernel-headers: bump 3.{0, 4, 6}.x stable versions
From: Peter Korsgaard @ 2012-11-06 11:11 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=d80d382620ac57926b13cbfce49ebda197c9be0a
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>
---
 toolchain/kernel-headers/Config.in                 |    6 +++---
 ...all-fix-__packed-in-exported-kernel-head.patch} |    0
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/toolchain/kernel-headers/Config.in b/toolchain/kernel-headers/Config.in
index d596870..e195def 100644
--- a/toolchain/kernel-headers/Config.in
+++ b/toolchain/kernel-headers/Config.in
@@ -67,12 +67,12 @@ config BR2_DEFAULT_KERNEL_HEADERS
 	default "2.6.37.6"	if BR2_KERNEL_HEADERS_2_6_37
 	default "2.6.38.8"	if BR2_KERNEL_HEADERS_2_6_38
 	default "2.6.39.4"	if BR2_KERNEL_HEADERS_2_6_39
-	default "3.0.50"	if BR2_KERNEL_HEADERS_3_0
+	default "3.0.51"	if BR2_KERNEL_HEADERS_3_0
 	default "3.1.10"	if BR2_KERNEL_HEADERS_3_1
 	default "3.2.33"	if BR2_KERNEL_HEADERS_3_2
 	default "3.3.8"		if BR2_KERNEL_HEADERS_3_3
-	default "3.4.17"	if BR2_KERNEL_HEADERS_3_4
+	default "3.4.18"	if BR2_KERNEL_HEADERS_3_4
 	default "3.5.7"		if BR2_KERNEL_HEADERS_3_5
-	default "3.6.5"		if BR2_KERNEL_HEADERS_3_6
+	default "3.6.6"		if BR2_KERNEL_HEADERS_3_6
 	default "2.6"		if BR2_KERNEL_HEADERS_SNAP
 	default $BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
diff --git a/toolchain/kernel-headers/linux-3.0.50-headers_install-fix-__packed-in-exported-kernel-head.patch b/toolchain/kernel-headers/linux-3.0.51-headers_install-fix-__packed-in-exported-kernel-head.patch
similarity index 100%
rename from toolchain/kernel-headers/linux-3.0.50-headers_install-fix-__packed-in-exported-kernel-head.patch
rename to toolchain/kernel-headers/linux-3.0.51-headers_install-fix-__packed-in-exported-kernel-head.patch

^ permalink raw reply related
* [Buildroot] [git commit] linux: bump 3.6.x stable version
From: Peter Korsgaard @ 2012-11-06 11:11 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=5a6392228a4f9383c40005bbd0b41ebda977d3cd
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>
---
 linux/Config.in |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/linux/Config.in b/linux/Config.in
index 60d7794..277ef0e 100644
--- a/linux/Config.in
+++ b/linux/Config.in
@@ -21,7 +21,7 @@ choice
 	prompt "Kernel version"
 
 config BR2_LINUX_KERNEL_3_6
-	bool "3.6.5"
+	bool "3.6.6"
 
 config BR2_LINUX_KERNEL_SAME_AS_HEADERS
 	bool "Same as toolchain kernel headers"
@@ -76,7 +76,7 @@ config BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION
 
 config BR2_LINUX_KERNEL_VERSION
 	string
-	default "3.6.5" if BR2_LINUX_KERNEL_3_6
+	default "3.6.6" if BR2_LINUX_KERNEL_3_6
 	default BR2_DEFAULT_KERNEL_HEADERS if BR2_LINUX_KERNEL_SAME_AS_HEADERS
 	default BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE if BR2_LINUX_KERNEL_CUSTOM_VERSION
 	default "custom" if BR2_LINUX_KERNEL_CUSTOM_TARBALL

^ permalink raw reply related
* [Buildroot] [PATCH 1/2] kernel-headers: bump 3.{0, 4, 6}.x stable versions
From: Peter Korsgaard @ 2012-11-06 11:11 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1352123620-16466-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] [PATCH] lcdproc: bump version to 0.5.6
From: spdawson at gmail.com @ 2012-11-06 13:14 UTC (permalink / raw)
  To: buildroot

From: Simon Dawson <spdawson@gmail.com>

Signed-off-by: Simon Dawson <spdawson@gmail.com>
---
 .../lcdproc/lcdproc-0.5.5-fix-menu-segfault.patch   |   19 -------------------
 package/lcdproc/lcdproc.mk                          |    2 +-
 2 files changed, 1 insertion(+), 20 deletions(-)
 delete mode 100644 package/lcdproc/lcdproc-0.5.5-fix-menu-segfault.patch

diff --git a/package/lcdproc/lcdproc-0.5.5-fix-menu-segfault.patch b/package/lcdproc/lcdproc-0.5.5-fix-menu-segfault.patch
deleted file mode 100644
index f0ebe2d..0000000
--- a/package/lcdproc/lcdproc-0.5.5-fix-menu-segfault.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-Trying to add a menu item using menu_add_item causes a segmentation fault
-in the LCDd server. This is caused by a read beyond the end of an array.
-
-This patch adds a safety check on the size of the argument array.
-
-Signed-off-by: Simon Dawson <spdawson@gmail.com>
-
-diff -Nurp a/server/commands/menu_commands.c b/server/commands/menu_commands.c
---- a/server/commands/menu_commands.c	2011-08-14 13:29:16.000000000 +0100
-+++ b/server/commands/menu_commands.c	2012-10-04 22:19:07.997409193 +0100
-@@ -198,7 +198,7 @@ menu_add_item_func(Client *c, int argc,
- 
- 	/* call menu_set_item() with a temporarily allocated argv
- 	 * to process the remaining options */
--	if ((argc > 5) || (argv[4][0] == '-')) {
-+	if ((argc > 5) || ((argc == 5) && argv[4][0] == '-')) {
- 		// menu_add_item <menuid> <newitemid> <type> [<text>]
- 		// menu_set_item <menuid> <itemid> {<option>}+
- 		int i, j;
diff --git a/package/lcdproc/lcdproc.mk b/package/lcdproc/lcdproc.mk
index 7914c85..aa204f1 100644
--- a/package/lcdproc/lcdproc.mk
+++ b/package/lcdproc/lcdproc.mk
@@ -3,7 +3,7 @@
 # lcdproc
 #
 #############################################################
-LCDPROC_VERSION = 0.5.5
+LCDPROC_VERSION = 0.5.6
 LCDPROC_SOURCE = lcdproc-$(LCDPROC_VERSION).tar.gz
 LCDPROC_SITE = http://downloads.sourceforge.net/project/lcdproc/lcdproc/$(LCDPROC_VERSION)
 LCDPROC_LICENSE = GPLv2+
-- 
1.7.10.4

^ permalink raw reply related
* [Buildroot] Udev on a live CD system does not appear to populate /dev
From: Antony Vennard @ 2012-11-06 14:02 UTC (permalink / raw)
  To: buildroot

Hi All,

I'm currently looking at using udev for a live cd environment built with
buildroot, and I'm having trouble getting udev to pick up the machine's
devices.

I have some questions and some details that will (hopefully) help
identify my problem

Firstly, my kernel is configured to use devtmpfs:

681:CONFIG_DEVTMPFS=y
682:CONFIG_DEVTMPFS_MOUNT=y

so as I understand it, /dev should be mounted as a tmpfs by the kernel
and populated with /dev/null, /dev/console etc. Yet, my
buildroot/output/target contains a dev folder with subdirectories
created by buildroot.

So, I tried both creating the entries with target/generic_device_table
for tty0, tty1, console, null. This works, and udev reports it is
scanning for devices and done, yet /dev never picks up e.g. /dev/sda, or
/dev/disk/..., or so on. I have, in this configuration, copied
/usr/lib/udev/rules.d/* to buildroot/output/target/etc/udev/rules.d to
no avail; as far as I can see whatever rules I supply, even from my
Fedora or Ubuntu distributions, do not seem to affect udev.

Wondering if this creation method was wrong, I have then removed all of
the entries in /dev so that the kernel can mount its own devtmpfs. When
booting, /dev/null and /dev/tty1 are reported as missing. I imagine
there is nothing in /dev at this stage

Various possibly related points:
 * I thought udev required udevd, yet I can't see that either running or
available on the ISO, nor can I find a configuration option to create it.
 * I have D-Bus built for the system, as I read udev required it.
 * I can see sda1 in /sys/block/sda/sda1; likewise for other attached
storage devices.

Am I doing anything very wrong? I get the feeling I must be missing
something for this to not work, yet I'm not sure what.

Can anyone offer any advice? Happy to provide config snippets etc.

Using buildroot 2012.08.

Thanks,

Antony


-- 
________________

Macrium? Software is a trading name of Paramount Software UK Ltd, 
Registered in England and Wales Number 02973414
Registered Office: Kilburn House, Manchester Science Park, Lloyd St. North, 
Manchester M15 6SE United Kingdom

The information contained in this e-mail is confidential, privileged, or 
otherwise protected from disclosure. It is intended only for the use of the 
authorized individual as indicated in the e-mail. Any unauthorized 
disclosure, copying, distribution or taking of any action based on the 
contents of this material is strictly prohibited.

If you have received this e-mail in error, please delete it immediately.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 895 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121106/29afbc10/attachment.asc>

^ permalink raw reply
* [Buildroot] [PATCH] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static
From: ANDY KENNEDY @ 2012-11-06 15:06 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <50984D57.3080402@mind.be>

> 
>   Although I'm OK with this patch, I have been unable to reproduce the problem
> and I'd like to know why it is going wrong with -static.  Can you post a
> defconfig that I can rebuild and that exposes the problem?
> 
>   Note: a few autobuilders with BR2_PREFER_STATIC_LIB enabled could be nice -
> or maybe not, because many packages _will_break.
> 
>   Regards,
>   Arnout

First off, I built again with a clean copy of BuildRoot (2012.08) and
produced this output this time:

root at akennedy_lin:~/deleteme/buildroot-2012.08# find output/target/ \
-exec file {} \; 2>&1 | grep dynamic | awk -F: '{print $1}'
output/target/usr/bin/ldd
output/target/usr/bin/htop
output/target/usr/bin/getconf
output/target/usr/sbin/kdump
output/target/usr/sbin/proftpd
output/target/sbin/ldconfig

Note that htop and proftpd got linked dynamically.  The odd part is
that kexec built static this time.  What's up with that?  I repeated
this twice and kexec builds static every time. . . though I really
thought I did this last week and it was dynamically linked.  Perhaps
I'm smokin' something. . .  BTW, I have _NEVER_ been able to build
kdump static through their build.  I can reproduce it manually, but
there seems to be no way to do it with their current Makefile.

Attached is the config file.  You may want to change the primary
download site as I have it set to ftp://localhost/pub/dl.

Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot-2012_08.config
Type: application/octet-stream
Size: 25887 bytes
Desc: buildroot-2012_08.config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121106/a48d4e15/attachment-0001.obj>

^ permalink raw reply
* [Buildroot] [PATCH] add new package fxload
From: Alex Bradbury @ 2012-11-06 15:33 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <27204261.196.1352192268013.JavaMail.rosen@pcrosen>

On 6 November 2012 08:58, Jeremy Rosen <jeremy.rosen@openwide.fr> wrote:
>>   Also I'll warn you: it may take a while (months) before your patch
>>   is
>> accepted even if you make all necessary correction, and we may even
>> forget
>> to include it in the end.  That's not because we're evil :-) but
>> because
>> our contribution process is still sub-optimal.  Buildroot has grown
>> significantly in number of contributions over the last two years, and
>> our maintainer (Peter Korsgaard) is just saturated.  We're still
>> experimenting
>> with ways to improve the process.
>>
>
> Fair enough, i'm a maintainer for other FOSS projects, so I know how that sort of problem go...
>
> is Peter the only one comitting ? couldn't someone help with simple patches (like updating version of existing packages)

Note it was decided at the recent Developer Days meeting that patches
would be accepted more aggressively. Presumably this means the chances
of patches that have been appropriately cleaned up to meet the
buildroot guidelines are less likely to be accidentally dropped.

Alex

^ permalink raw reply
* [Buildroot] [PATCH v11 2/9] perl: new package
From: François Perrad @ 2012-11-06 16:23 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <CAB0FRsv058=3G7qbFPS6xrSr_TG5=QDhRKcOU8O6mCot_dCuMQ@mail.gmail.com>

2012/11/6 Fran?ois Perrad <francois.perrad@gadz.org>:
> 2012/11/5 Fran?ois Perrad <francois.perrad@gadz.org>:
>> 2012/10/30 Bernd Kuhls <berndkuhls@hotmail.com>:
>>> Hi,
>>>
>>> Francois Perrad <fperrad@gmail.com> wrote in
>>> news:1350652434-32020-2-git-send-email-francois.perrad at gadz.org:
>>>
>>> currently I am testing your patchset, but I found problems during
>>> compiling, some I could solve myself:
>>>
>>>> +PERL_CONF_OPT = -des \
>>>
>>> [...]
>>>
>>>> +          -Dlibc=$(STAGING_DIR)/lib/libc.so \
>>>
>>> I had to change this line to
>>>
>>>              -Dlibc=$(STAGING_DIR)/usr/lib/libc.so.0 \
>>>
>>> for usage with uClibc 0.9.33.2
>>>
>>> [...]
>>>
>>>> +          -Uoptimize
>>>
>>> Here I had to add "-Ud_eaccess" to avoid a compilation bug.
>>>
>>> Perl will still not finish to compile, stopping with this error message:
>>>
>>>> LD_LIBRARY_PATH=/home/bernd/.fbr/build/output/build/perl-5.16.1
>>> /home/bernd/.fbr/build/output/build/perl-5.16.1/Cross/run-qemu-i386
>>> ./miniperl -Ilib make_ext.pl cpan/Archive-Extract/pm_to_blib
>>> MAKE=/home/bernd/.fbr/build/output/host/usr/bin/make LIBPERL_A=libperl.so
>>>>         Making Archive::Extract (all)
>>>>
>>>> Creating Makefile.PL in cpan/Archive-Extract for Archive::Extract
>>>>
>>>> Running Makefile.PL in cpan/Archive-Extract
>>>> /home/bernd/.fbr/build/output/build/perl-5.16.1/Cross/run-qemu-i386
>>> ../../miniperl -I../../lib Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none
>>> INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=libperl.so
>>>> -1 from cpan/Archive-Extract's Makefile.PL at make_ext.pl line 409.
>>>> Warning: No Makefile!
>>>> /home/bernd/.fbr/build/output/host/usr/bin/make config PERL_CORE=1
>>> LIBPERL_A=libperl.so failed, continuing anyway...
>>>> Making all in cpan/Archive-Extract
>>>> /home/bernd/.fbr/build/output/build/perl-5.16.1/Cross/run-qemu-i386
>>> /home/bernd/.fbr/build/output/host/usr/bin/make all PERL_CORE=1
>>> LIBPERL_A=libperl.so
>>>> Unsuccessful make(cpan/Archive-Extract): code=-1 at make_ext.pl line 468.
>>>> make[1]: *** [cpan/Archive-Extract/pm_to_blib] Fehler 22
>>>> make[1]: Leaving directory `/home/bernd/.fbr/build/output/build/perl-
>>> 5.16.1'
>>>> make: *** [/home/bernd/.fbr/build/output/build/perl-5.16.1/.stamp_built]
>>> Fehler 2
>>>
>>> Executing the last command alone provides this error hinting at a problem
>>> with host-qemu, which I was able to solve yet.
>>>
>>> $ /home/bernd/.fbr/build/output/build/perl-5.16.1/Cross/run-qemu-i386
>>> /home/bernd/.fbr/build/output/host/usr/bin/make all PERL_CORE=1
>>> LIBPERL_A=libperl.so
>>> qemu: Unsupported syscall: 240
>>> qemu: Unsupported syscall: 240
>>>
>>> First I got this error message with Debian Squeeze i386 (virtualbox guest,
>>> Win XP host), but also on Debian wheezy amd64 running non-virtualized.
>>>
>>> My .config can be found here: http://pastebin.com/yz1SzeB2
>>> I am using buildroot as part of the FLI4L source package[1].
>>>
>>> Kind regards, Bernd
>>>
>>
>> I could reproduce the lastest problem on the HEAD of Buildroot with
>> qemu_x86_defconfig (which is a smaller config than your FLI4L config).
>>
>
> first, before manually running a command in the build tree, you must
> set PERL_MM_OPT
>    $ export PERL_MM_OPT="PERL=`pwd`/Cross/miniperl"
>
> the error
>     -1 from cpan/Archive-Extract's Makefile.PL at make_ext.pl line 409.
> comes from miniperl which fails with a 'system' call.
>
> this problem could be reproduced with a simple one-liner :
>
> $ perl -e "my \$code = system( q(echo), q(hello) ); print(\$code);"
> hello
> 0
>
> $ Cross/miniperl -e "my \$code = system( q(echo), q(hello) ); print(\$code);"
> -1
>
> Fran?ois
>

after an installation on the target, this 'miniperl' works fine.
so, the problem comes from Qemu.

I write a small C example :

$ cat sys.c
#include <stdio.h>
#include <stdlib.h>

int main()
{
 	int ret = system("echo hello");
	printf("%d\n", ret);
}

$ ../../host/usr/bin/i686-buildroot-linux-uclibc-gcc -o sys sys.c
$ file sys
sys: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), not stripped
$ ../../host/usr/bin/qemu-i386 ./sys
-1

I also try on various architecture.
I build Perl successfully with qemu-arm and qemu-mips,
the problem occurs with qemu-i386 and qemu-x86_64,
with a qemu-i386 version 1.2.0 built with Buildroot and with a
qemu-i386 version 1.0.50 which comes my distro Ubuntu 12.04 LTS.

Other bad new, these days, the homepage of Qemu (http://wiki.qemu.org) is down.

Fran?ois

>> Fran?ois
>>
>>> [1] http://www.fli4l.de/download/tarball-version/aktuell.html
>>>
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot

^ permalink raw reply
* [Buildroot] [PATCH] boost: bump to version 1.52.0
From: Victor Hiairrassary @ 2012-11-06 17:53 UTC (permalink / raw)
  To: buildroot

From: mecanix <victor.hiairrassary.ml@gmail.com>

---
 package/boost/Config.in | 4 ++++
 package/boost/boost.mk  | 4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/package/boost/Config.in b/package/boost/Config.in
index 8798367..58e62a0 100644
--- a/package/boost/Config.in
+++ b/package/boost/Config.in
@@ -1,9 +1,13 @@
 comment "boost requires a toolchain with C++ support enabled"
 	depends on !BR2_INSTALL_LIBSTDCPP
 
+comment "boost requires a toolchain with large file support enabled"
+	depends on !BR2_LARGEFILE
+
 config BR2_PACKAGE_BOOST
 	bool "boost"
 	depends on BR2_INSTALL_LIBSTDCPP
+	depends on BR2_LARGEFILE
 	select BR2_PACKAGE_BZIP2
 	select BR2_PACKAGE_ZLIB
 	help
diff --git a/package/boost/boost.mk b/package/boost/boost.mk
index 64856bc..005c7ca 100644
--- a/package/boost/boost.mk
+++ b/package/boost/boost.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-BOOST_VERSION = 1.49.0
+BOOST_VERSION = 1.52.0
 BOOST_FILE_VERSION = $(subst .,_,$(BOOST_VERSION))
 BOOST_SOURCE = boost_$(BOOST_FILE_VERSION).tar.bz2
 BOOST_SITE = http://downloads.sourceforge.net/project/boost/boost/$(BOOST_VERSION)
@@ -15,7 +15,7 @@ TARGET_CC_VERSION = $(shell $(TARGET_CC) -dumpversion)
 BOOST_DEPENDENCIES = bzip2 zlib
 
 BOOST_FLAGS =
-BOOST_WITHOUT_FLAGS = python
+BOOST_WITHOUT_FLAGS = python context
 
 BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_CHRONO),,chrono)
 BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_DATE_TIME),,date_time)
-- 
1.8.0

^ permalink raw reply related
* [Buildroot] Udev on a live CD system does not appear to populate /dev
From: Stefan Fröberg @ 2012-11-06 18:37 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <5099186E.1030409@macrium.com>

6.11.2012 16:02, Antony Vennard kirjoitti:
> Hi All,
>
> I'm currently looking at using udev for a live cd environment built with
> buildroot, and I'm having trouble getting udev to pick up the machine's
> devices.
>
> I have some questions and some details that will (hopefully) help
> identify my problem
>
> Firstly, my kernel is configured to use devtmpfs:
>
> 681:CONFIG_DEVTMPFS=y
> 682:CONFIG_DEVTMPFS_MOUNT=y
>
> so as I understand it, /dev should be mounted as a tmpfs by the kernel
> and populated with /dev/null, /dev/console etc. Yet, my
> buildroot/output/target contains a dev folder with subdirectories
> created by buildroot.
>
> So, I tried both creating the entries with target/generic_device_table
> for tty0, tty1, console, null. This works, and udev reports it is
> scanning for devices and done, yet /dev never picks up e.g. /dev/sda, or
> /dev/disk/..., or so on. I have, in this configuration, copied
> /usr/lib/udev/rules.d/* to buildroot/output/target/etc/udev/rules.d to
> no avail; as far as I can see whatever rules I supply, even from my
> Fedora or Ubuntu distributions, do not seem to affect udev.
>
> Wondering if this creation method was wrong, I have then removed all of
> the entries in /dev so that the kernel can mount its own devtmpfs. When
> booting, /dev/null and /dev/tty1 are reported as missing. I imagine
> there is nothing in /dev at this stage
Im not sure but I tought that device nodes /dev/null and /dev/console
(and some others)
have to always be created manually
(either with buildroot device tables, by doing the mknod thing or just
by copying those
nodes from host system to output/target/dev or fs/skeleton/dev)
to be of any use.

At least that's what I have done always, created those /dev/null and
/dev/cosole and also
/dev/ram0 etc.. myself into output/target/dev and then make my initramfs
from that directory and
 let the hotplug program (either busybox's own mdev or udev) do the rest.

Here's what I have minimally in my own buildroot's fs/skeleton/dev
folder (which is copied at the end of the buildroot
process into output/target/dev )

crw-------.  1 root root 5, 1 11.1.2012 console
lrwxrwxrwx.  1 root root   10 19.3.2012 log -> ../tmp/log
brw-rw----.  1 root root 7, 0 20.8. 00:58 loop0
crw-------.  1 root root 1, 1 11.1.2012 mem
crw-r--r--.  1 root root 1, 3 12.1.2012 null
drwxr-xr-x.  2 root root 1024 12.1.2012 pts
brw-r-----.  1 root root 5, 0 12.1.2012 ram0
crw-r--r--.  1 root root 5, 0 12.1.2012 tty
crw-------.  1 root root 4, 0 11.1.2012 tty0
crw-------.  1 root root 4, 1 11.1.2012 tty1
crw-------.  1 root root 1, 5 11.1.2012 zero

Now, some of those might not be strictly necessary and should be created
by mdev/udev.
But it's good to have them just in case.

Besides some pre-made device nodes, make sure that you have S10udev in your
output/target/etc/init.d.
That is the one responsible of starting udev.

You can also copy S10udev to fs/skeleton/etc/init.d to make sure that
it's included in
output/target/etc/init.d everytime you make complete new rebuild
(make clean && make)


Im presuming you *are* using initramfs in your early device initialization ?
(if not then you absolutely should. Live CD without initramfs is useless)

Best regards
Stefan
> Various possibly related points:
>  * I thought udev required udevd, yet I can't see that either running or
> available on the ISO, nor can I find a configuration option to create it.
>  * I have D-Bus built for the system, as I read udev required it.
>  * I can see sda1 in /sys/block/sda/sda1; likewise for other attached
> storage devices.
>
> Am I doing anything very wrong? I get the feeling I must be missing
> something for this to not work, yet I'm not sure what.
>
> Can anyone offer any advice? Happy to provide config snippets etc.
>
> Using buildroot 2012.08.
>
> Thanks,
>
> Antony
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121106/3d142432/attachment.html>

^ permalink raw reply
* [Buildroot] [PATCH] [v3] Allow to run severals post build scripts instead of only one
From: Arnout Vandecappelle @ 2012-11-06 19:36 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <21241_1352183937_5098B081_21241_18787_1_OF7B519B75.588186A9-ONC1257AAE.002464C5-C1257AAE.0024853E@sagemcom.com>

On 11/06/12 07:38, Philippe REYNES wrote:
> I've tried to remove this backslashes, and I've got an error when building:
>
>
> /bin/sh: -c: line 0: syntax error near unexpected token `('
> /bin/sh: -c: line 0: `echo ">>>    "Executing post-build script(s)""'
> make: *** [target-finalize] Error 1
>
> So those backslashes are usefull.

  Oh I see - it's because the quotes shouldn't be there...  But since we have
quotes in all MESSAGE calls at the moment, leave it as it is.

  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] how does udhcpc print messages to console
From: Jürgen Benjamin Ronshausen @ 2012-11-06 19:48 UTC (permalink / raw)
  To: buildroot

hi,

i am trying to print message from my program which is called in a shell
script.

problem is the shell script collects all the output from my program and
doesn't print it immediately.

i noticed, that udhcpc print its messages immediately by calling syslog.

from debug.h

# define LOG_EMERG	"EMERGENCY!"
# define LOG_ALERT	"ALERT!"
# define LOG_CRIT	"critical!"
# define LOG_WARNING	"warning"
# define LOG_ERR	"error"
# define LOG_INFO	"info"
# define LOG_DEBUG	"debug"
# define LOG(level, str, args...) do { printf("%s, ", level); \
				printf(str, ## args); \
				printf("\n"); } while(0)
# define OPEN_LOG(name) do {;} while(0)
#define CLOSE_LOG() do {;} while(0)

from dhcpc.c

OPEN_LOG("udhcpc");
LOG(LOG_INFO, "udhcp client (v%s) started", VERSION);

is there more than this to do?

thx J?rgen

^ permalink raw reply
* [Buildroot] new perl build issue
From: Alexander Khryukin @ 2012-11-06 20:51 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <CAB0FRssio4MnFavizgHUnLa-_tJAZAUNcb4hxKb=RjQKoXnfQg@mail.gmail.com>

2012/11/5 Fran?ois Perrad <francois.perrad@gadz.org>

> 2012/11/5 Alexander Khryukin <alexander@mezon.ru>:
> >
> >
> > 2012/11/5 Alexander Khryukin <alexander@mezon.ru>
> >>
> >>
> >>
> >> 2012/11/5 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> >>>
> >>>
> >>> On Sun, 4 Nov 2012 20:41:45 +0100, Fran?ois Perrad wrote:
> >>>
> >>> > this afternoon, Thomas has posted 3 patches for qemu (see
> >>> > http://patchwork.ozlabs.org/patch/197055/).
> >>> > Alexander, try to rebuild host-qemu with them.
> >>>
> >>> Unfortunately, none of those patches have a chance to fix Alexander's
> >>> problem. My patches only fix missing dependencies.
> >>>
> >>> Also, could you have a look at http://autobuild.buildroot.org/ for
> perl
> >>> build failures? It seems like Qemu doesn't start properly on some
> >>> platforms, for some reason.
> >>>
> >>> Thomas
> >>> --
> >>> Thomas Petazzoni, Free Electrons
> >>> Kernel, drivers, real-time and embedded Linux
> >>> development, consulting, training and support.
> >>> http://free-electrons.com
> >>
> >>
> >>
> >> I applied your patch but looks it not helps me.
> >>
> >> http://pastie.org/5188031
> >
> >
> >
> > Also if i compile it by my default system gcc it's ok
> >
> >
> > [fdkit at kvm-host UU]$ gcc try.c
> > [fdkit at kvm-host UU]$ ls ./a.out
> > ./a.out*
> > [fdkit at kvm-host UU]$ ./a.out
> > Ok
> >
>
> Alexander,
>
> the 'qemu-arm' built by Buildroot doesn't work properly.
> could you try this workaround ?
> 1) install a 'qemu-arm' with your distro package manager,
>      $ apt-get install qemu-kvm-extras # or equivalent
> 2) apply this patch :
> --- a/package/perl/perl.mk
> +++ b/package/perl/perl.mk
> @@ -22,7 +22,7 @@ endif
>
>  PERL_CONF_OPT = -des \
>                 -Dusecrosscompile \
> -               -Dtargetrun=$(QEMU_USER) \
> +               -Dtargetrun=qemu-arm \
>                 -Dqemulib=$(STAGING_DIR) \
>                 -Dar="$(TARGET_AR)" \
>                 -Dcc="$(TARGET_CC)" \
>
> Fran?ois
>


I migrated my build system to fresh linux installation with 3.5.1 kernel
 Linux localhost.localdomain 3.5.1-nrj-desktop-1mib #1 SMP PREEMPT Tue Aug
14 11:57:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Applied your patch, and problem still here.

http://pastie.org/5336882
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121106/fa1dd9f9/attachment.html>

^ permalink raw reply
* [Buildroot] [PATCH v11 2/9] perl: new package
From: Bernd Kuhls @ 2012-11-06 21:03 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <50986270.4070804@mind.be>

Arnout Vandecappelle <arnout@mind.be> wrote in 
news:50986270.4070804 at mind.be:

>   Is it possible that this is because the target binary is created with
> kernel headers 3.2, but you're running it on a host which is only 2.6.32
> (squeeze)?  But then it should work on wheezy, because that has 3.2 as
> well (at least since about four months IIRC).  Although...  240 on i386
> is futex, which has existed already since long before 2.6.32.

Hi,

on wheezy I am using kernel 3.5.5.

$ LC_ALL=C apt-cache policy linux-image-3.5-trunk-amd64
linux-image-3.5-trunk-amd64:
  Installed: 3.5.5-1~experimental.1
  Candidate: 3.5.5-1~experimental.1

Kind regards, Bernd

^ permalink raw reply
* [Buildroot] [PATCH v11 2/9] perl: new package
From: Bernd Kuhls @ 2012-11-06 21:09 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <20121106080812.4e7bd01a@skate>

Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8
@public.gmane.org> wrote in news:20121106080812.4e7bd01a at skate:

> I guess this whole qemu thing for Perl is going to be annoying on the
> long term. We might need to start looking for a different option, i.e
> seeing how to get Perl to build without needing qemu.

Hi,

maybe this can be of help: http://perlcross.berlios.de/

Kind regards, Bernd

PS: The reason I am fiddling around with Perl is to compile 
Mail::Spamassassin which needs a lot of other modules.

^ permalink raw reply
* [Buildroot] no jack?
From: Grant @ 2012-11-06 21:39 UTC (permalink / raw)
  To: buildroot

Is there a jack package available for buildroot?

- Grant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121106/cd4c830e/attachment.html>

^ permalink raw reply
* [Buildroot] [PATCH] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static
From: Arnout Vandecappelle @ 2012-11-06 22:32 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C628B69F@ex-mb1.corp.adtran.com>

On 11/06/12 16:06, ANDY KENNEDY wrote:
>> >     Although I'm OK with this patch, I have been unable to reproduce the problem
>> >  and I'd like to know why it is going wrong with -static.  Can you post a
>> >  defconfig that I can rebuild and that exposes the problem?
>> >
>> >     Note: a few autobuilders with BR2_PREFER_STATIC_LIB enabled could be nice -
>> >  or maybe not, because many packages _will_break.
>> >
>> >     Regards,
>> >     Arnout
> First off, I built again with a clean copy of BuildRoot (2012.08) and
> produced this output this time:
>
> root at akennedy_lin:~/deleteme/buildroot-2012.08#  find output/target/ \
> -exec file {} \; 2>&1 | grep dynamic | awk -F: '{print $1}'
> output/target/usr/bin/ldd
> output/target/usr/bin/htop
> output/target/usr/bin/getconf
> output/target/usr/sbin/kdump
> output/target/usr/sbin/proftpd
> output/target/sbin/ldconfig

  I finally understand what's going on - it's exactly what Andy said in his
first mail :-)

  libtool interpret -static as linking statically with libraries that will not
be installed to the libdir; you have to pass it -all-static to force static
linking.  Or, as Andy proposes, pass --static, which libtool passes on blindly
to gcc.  gcc and (GNU) ld both interpret --static the same as -static (although
this isn't documented).

  Therefore, this gets my
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>


  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] [PATCH v11 2/9] perl: new package
From: Arnout Vandecappelle @ 2012-11-06 22:59 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <6aub7k.9fm.ln@bernd-kuhls.de>

On 06/11/12 22:09, Bernd Kuhls wrote:
> Thomas Petazzoni<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8
> @public.gmane.org>  wrote in news:20121106080812.4e7bd01a at skate:
>
>> I guess this whole qemu thing for Perl is going to be annoying on the
>> long term. We might need to start looking for a different option, i.e
>> seeing how to get Perl to build without needing qemu.
>
> Hi,
>
> maybe this can be of help: http://perlcross.berlios.de/

  That sounds like a terrific idea!  Do you feel up to integrating this in
buildroot and sending a patch?

  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] [git commit] rpcbind: correct download URL
From: Peter Korsgaard @ 2012-11-06 23:07 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=456f9de2fd6feffa465aeef44fb3d0082e3b0e0f
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

BR2_SOURCEFORGE_MIRROR is gone.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 package/rpcbind/rpcbind.mk |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/package/rpcbind/rpcbind.mk b/package/rpcbind/rpcbind.mk
index d9a80de..de9a421 100644
--- a/package/rpcbind/rpcbind.mk
+++ b/package/rpcbind/rpcbind.mk
@@ -5,7 +5,7 @@
 #############################################################
 
 RPCBIND_VERSION = 0.2.0
-RPCBIND_SITE    = http://$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/project/rpcbind/rpcbind/$(RPCBIND_VERSION)
+RPCBIND_SITE    = http://downloads.sourceforge.net/project/rpcbind/rpcbind/$(RPCBIND_VERSION)
 RPCBIND_SOURCE  = rpcbind-$(RPCBIND_VERSION).tar.bz2
 RPCBIND_LICENSE = BSD-3c
 RPCBIND_LICENSE_FILES = COPYING

^ permalink raw reply related
* [Buildroot] [git commit] adding-package-generic.txt: BR2_SOURCEFORGE_MIRROR is no more
From: Peter Korsgaard @ 2012-11-06 23:10 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=cf76170cc3418f36dd9e4daa2f3d0618ce3dc389
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 docs/manual/adding-packages-generic.txt |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
index e1b46b0..7ecdb91 100644
--- a/docs/manual/adding-packages-generic.txt
+++ b/docs/manual/adding-packages-generic.txt
@@ -167,9 +167,7 @@ information is (assuming the package name is +libfoo+) :
   slash for absolute paths:
   +scp://[user@]host:/absolutepath+. +
   If +HOST_LIBFOO_SITE+ is not specified, it defaults to
-  +LIBFOO_SITE+. If none are specified, then the location is assumed
-  to be
-  +http://$$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/sourceforge/packagename+. +
+  +LIBFOO_SITE+.
   Examples: +
     +LIBFOO_SITE=http://www.libfoosoftware.org/libfoo+ +
     +LIBFOO_SITE=http://svn.xiph.org/trunk/Tremor/+ +

^ permalink raw reply related
* [Buildroot] no jack?
From: Arnout Vandecappelle @ 2012-11-06 23:12 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <CAN0CFw31RjieVoSKf9QOAud5yHe6w-oy_J77V9iLYxu2-pSz5g@mail.gmail.com>

On 06/11/12 22:39, Grant wrote:
> Is there a jack package available for buildroot?

  No, but it shouldn't be too difficult to integrate.  Look at midori for an
example of a package using waf as the build system.

  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] Udev on a live CD system does not appear to populate /dev
From: Arnout Vandecappelle @ 2012-11-06 23:26 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <5099186E.1030409@macrium.com>

On 06/11/12 15:02, Antony Vennard wrote:
> Hi All,
>
> I'm currently looking at using udev for a live cd environment built with
> buildroot, and I'm having trouble getting udev to pick up the machine's
> devices.
>
> I have some questions and some details that will (hopefully) help
> identify my problem

  It would help if you can do 'make savedefconfig' and post the
resulting defconfig file.

>
> Firstly, my kernel is configured to use devtmpfs:
>
> 681:CONFIG_DEVTMPFS=y
> 682:CONFIG_DEVTMPFS_MOUNT=y
>
> so as I understand it, /dev should be mounted as a tmpfs by the kernel
> and populated with /dev/null, /dev/console etc.

  Since you're making a live CD, you'll probably boot with an
initrd/initramfs.  The kernel then doesn't mount /dev automatically,
it has to be done by init script in /init (which is called instead of
/sbin/init for an initramfs).  Buildroot creates this script for you
when you build a cpio or initramfs filesystem (i.e. the things that are
typically used as initrd image).  If you're trying to use an ext2 as
an initrd (which is a bad idea), you have to copy fs/cpio/init to the
target yourself.

> Yet, my
> buildroot/output/target contains a dev folder with subdirectories
> created by buildroot.

  Yes, that's a bit silly.  It doesn't really matter, because the devtmpfs
gets mounted over it and those files are no longer visible.

  If you have an initrd/initramfs, /dev/console should ideally be there,
otherwise you get the message 'Failed to open an initial console'.  That
message is harmless though because the /init script mounts /dev, which
implicitly creates /dev/console, and when /sbin/init is execed it can use
this /dev/console.

> So, I tried both creating the entries with target/generic_device_table
> for tty0, tty1, console, null. This works,

  Yep, this sounds like you're missing a /init.

> and udev reports it is scanning for devices and done,
> yet /dev never picks up e.g. /dev/sda, or
> /dev/disk/..., or so on. I have, in this configuration, copied
> /usr/lib/udev/rules.d/* to buildroot/output/target/etc/udev/rules.d to
> no avail; as far as I can see whatever rules I supply, even from my
> Fedora or Ubuntu distributions, do not seem to affect udev.

  Note that udev doesn't create anything in /dev - it relies on the kernel
to create the device nodes. udev only does renaming, chmodding, chowning
and making symlinks.

>
> Wondering if this creation method was wrong, I have then removed all of
> the entries in /dev so that the kernel can mount its own devtmpfs. When
> booting, /dev/null and /dev/tty1 are reported as missing. I imagine
> there is nothing in /dev at this stage

  This is weird.  If there's no /dev/console, how can init report that
/dev/tty1 is missing?

[snip]

  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] [PATCH] cpio/initramfs: clarify their use in the help text
From: Arnout Vandecappelle @ 2012-11-06 23:41 UTC (permalink / raw)
  To: buildroot

Recent mails on the list show that it is not very clear how to create
an initial RAM fs with buildroot.  So make this more explicit in the
cpio and initramfs help texts.  Hopefully this will reduce the /init
debugging we have to do.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
Is this a documentation patch that should be picked up by Samuel, or
is it for Peter?

 fs/cpio/Config.in      |   11 ++++++++---
 fs/initramfs/Config.in |    2 +-
 2 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/fs/cpio/Config.in b/fs/cpio/Config.in
index 374cfe0..0669a44 100644
--- a/fs/cpio/Config.in
+++ b/fs/cpio/Config.in
@@ -1,14 +1,19 @@
 config BR2_TARGET_ROOTFS_CPIO
-	bool "cpio the root filesystem"
+	bool "cpio the root filesystem (for use as an initial RAM filesystem)"
 	help
-	  Build a cpio archive of the root filesystem
+	  Build a cpio archive of the root filesystem.  This is typically
+	  used for an initial RAM filesystem that is passed to the kernel
+	  by the bootloader.
 
 choice
         prompt "Compression method"
         default BR2_TARGET_ROOTFS_CPIO_NONE
         depends on BR2_TARGET_ROOTFS_CPIO
         help
-          Select compressor for cpio filesystem of the root filesystem
+          Select compressor for cpio filesystem of the root filesystem.
+          If you use the cpio archive as an initial RAM filesystem, make
+          sure the kernel contains the decompression algorithm selected
+          here.
 
 config BR2_TARGET_ROOTFS_CPIO_NONE
         bool "no compression"
diff --git a/fs/initramfs/Config.in b/fs/initramfs/Config.in
index bbc2ab0..22066ee 100644
--- a/fs/initramfs/Config.in
+++ b/fs/initramfs/Config.in
@@ -1,5 +1,5 @@
 config BR2_TARGET_ROOTFS_INITRAMFS
-	bool "initramfs for initial ramdisk of linux kernel"
+	bool "initial RAM filesystem linked into linux kernel"
 	depends on BR2_LINUX_KERNEL
 	select BR2_TARGET_ROOTFS_CPIO
 	help
-- 
tg: (5a63922..) t/cpio-clarify-help (depends on: master)

^ permalink raw reply related
* [Buildroot] Udev on a live CD system does not appear to populate /dev
From: Arnout Vandecappelle @ 2012-11-06 23:46 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <509958D9.7050108@petroprogram.com>

On 06/11/12 19:37, Stefan Fr?berg wrote:
> Here's what I have minimally in my own buildroot's fs/skeleton/dev folder (which is copied at the end of the buildroot
> process into output/target/dev )

  Err... That can only work if you have sudo in your post-build script - which
we consider bad practice.  We have the device_table to deal with device nodes.
And all of that shouldn't be necessary if you use devtmpfs (or udev or mdev,
which implies devtmpfs).  If you use static device nodes, then the default
device_table_dev creates all of those.

  If that doesn't work for you, then we should try to fix it in buildroot.

  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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox