* [Buildroot] [PATCH 1/2] hiawatha: needs mmu
From: Gustavo Zacarias @ 2012-11-28 13:24 UTC (permalink / raw)
To: buildroot
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
---
package/hiawatha/Config.in | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/package/hiawatha/Config.in b/package/hiawatha/Config.in
index 431a9fa..ac0aa10 100644
--- a/package/hiawatha/Config.in
+++ b/package/hiawatha/Config.in
@@ -1,5 +1,7 @@
config BR2_PACKAGE_HIAWATHA
bool "hiawatha"
+ # needs fork()
+ depends on BR2_USE_MMU
help
Hiawatha is a webserver for Unix and has been built with
security in mind. This resulted in a highly secure
--
1.7.8.6
^ permalink raw reply related
* [Buildroot] [git commit branch/next] package: add gd package
From: Thomas Petazzoni @ 2012-11-28 13:06 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121128052616.GA29377@sapphire.tkos.co.il>
Dear Baruch Siach,
On Wed, 28 Nov 2012 07:26:17 +0200, Baruch Siach wrote:
> On Tue, Nov 27, 2012 at 11:21:06AM -0800, Peter Korsgaard wrote:
>
> [...]
>
> > +GD_TOOLS_ += gdlib-config
>
> Shouldn't this be 'GD_TOOLS_y'?
No, the idea is to have all tools to be kept in GD_TOOLS_y and all
tools to be removed in GD_TOOLS_. Since we always want to remove
gdlib-config from the target, we unconditionally add it to GD_TOOLS_.
> > +define GD_REMOVE_TOOLS
> > + rm -f $(addprefix $(TARGET_DIR)/usr/bin/,$(GD_TOOLS_))
>
> And here.
No, that's correct. GD_TOOLS_ is the list of things to be removed.
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 > To integrate pycrypto into Buildroot
From: Thomas Petazzoni @ 2012-11-28 13:02 UTC (permalink / raw)
To: buildroot
In-Reply-To: <07407110F438184D9D87521726FF42D41F64FE15@M357PRD1.ad.bcc.qld.gov.au>
Dear Noel Roberts,
On Wed, 28 Nov 2012 05:05:29 +0000, Noel Roberts wrote:
> This patch allows Buildroot to cross compile the crypto libraries
> needed for python integration, enabling good cryptographic support
> within Python.
Good. The part adding the package in package/Config.in is missing.
> This is my first patch submission - please advise me, if I need to
> rework anything.
Could you use git send-email to send your patch?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply
* [Buildroot] Qt mouse, keyboard, touchscreen
From: Thomas Petazzoni @ 2012-11-28 13:00 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354102604.50307.YahooMailNeo@web164602.mail.gq1.yahoo.com>
Dear Zoran Djordjevic,
On Wed, 28 Nov 2012 03:36:44 -0800 (PST), Zoran Djordjevic wrote:
> I've tried patch, you submitted, and then make qt-reconfigure and
qt-reconfigure will not re-extract the source code and apply the
patches, so it is not appropriate. If you want to rebuild a package
from scratch, including extracting the package and applying the
patches, do:
make qt-dirclean
> receive strange error about include folders. Same error I had
> earlier when trying with deleting stamp files (when added some
> options regarding Qt in Buildroot's menuconfig), and in that case
> I had to do make clean all. But if I do so, now, I think I will loose my
> patched files (am I right ?)
If you made changes to output/build/<something>/, yes, you will loose
your changes. But you shouldn't be making any change in
output/build/<something>/
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] Qt mouse, keyboard, touchscreen
From: Zoran Djordjevic @ 2012-11-28 11:36 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121127163037.3f619184@skate>
I've tried patch, you submitted, and then make qt-reconfigure and
receive strange error about include folders. Same error I had
earlier when trying with deleting stamp files (when added some
options regarding Qt in Buildroot's menuconfig), and in that case
I had to do make clean all. But if I do so, now, I think I will loose my
patched files (am I right ?)
What to do then ?
?
________________________________
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Zoran Djordjevic <djdjdjole@yahoo.com>
Cc: Stephan Hoffmann <sho@relinux.de>; "buildroot at busybox.net" <buildroot@busybox.net>
Sent: Tuesday, November 27, 2012 4:30 PM
Subject: Re: [Buildroot] Qt mouse, keyboard, touchscreen
Dear Zoran Djordjevic,
On Mon, 26 Nov 2012 23:46:15 -0800 (PST), Zoran Djordjevic wrote:
> My /dev/input node has event0, event1, mouse0 and mice.
> When I give: export QWS_MOUSE_PROTO=tslib:/dev/input/event0,
> touch screen works fine. However, tried different options for
> USB?mouse, and neither one works (cat /dev/input/mouse0 or mice gives
> terminal "garbage"). Regarding keyboard, I gave: export
> QWS_KEYBOARD=linuxinput:/dev/input/event1 Keyboard (USB)?does work,
> but from that moment my terminal connected keyboard (via COM port) -
> doesn't work (Ctrl-C). When exiting application, I can't give
> commands via terminal. Any help ?
Apply the attached patch to Qt.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121128/99be9bad/attachment.html>
^ permalink raw reply
* [Buildroot] [autobuild.buildroot.net] Build results for 2012-11-27
From: Thomas Petazzoni @ 2012-11-28 7:34 UTC (permalink / raw)
To: buildroot
Hello,
On 2012-11-27, 141 random build tests have been done and
submitted on autobuild.buildroot.net.
99 builds have been successful
42 builds have failed
Below the results of the failed builds. Successful builds are omitted.
Build 692ba721f42f7d1dbef7b93fbb5adea61ae77d11
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 00:02:26
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/692ba721f42f7d1dbef7b93fbb5adea61ae77d11/build-end.log
Complete log : http://autobuild.buildroot.net/results/692ba721f42f7d1dbef7b93fbb5adea61ae77d11/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/692ba721f42f7d1dbef7b93fbb5adea61ae77d11/config
Defconfig : http://autobuild.buildroot.net/results/692ba721f42f7d1dbef7b93fbb5adea61ae77d11/defconfig
Build 0bf06ee7c4364bd127816e3f6fa8231bb76d5e6d
==============================================
Status : NOK
Failure reason : gpsd-3.7
Architecture : x86_64
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 01:10:16
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/0bf06ee7c4364bd127816e3f6fa8231bb76d5e6d/build-end.log
Complete log : http://autobuild.buildroot.net/results/0bf06ee7c4364bd127816e3f6fa8231bb76d5e6d/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/0bf06ee7c4364bd127816e3f6fa8231bb76d5e6d/config
Defconfig : http://autobuild.buildroot.net/results/0bf06ee7c4364bd127816e3f6fa8231bb76d5e6d/defconfig
Build 7a309c9cc8e0598c7f3bd217f335155f1adcb79c
==============================================
Status : NOK
Failure reason : dropbear-2012.55
Architecture : sh2a
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 01:27:05
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/7a309c9cc8e0598c7f3bd217f335155f1adcb79c/build-end.log
Complete log : http://autobuild.buildroot.net/results/7a309c9cc8e0598c7f3bd217f335155f1adcb79c/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/7a309c9cc8e0598c7f3bd217f335155f1adcb79c/config
Defconfig : http://autobuild.buildroot.net/results/7a309c9cc8e0598c7f3bd217f335155f1adcb79c/defconfig
Build 10a1d2750dcd1a26d4bd50e1abbf80f8dbb0150e
==============================================
Status : NOK
Failure reason : ortp-0.20.0
Architecture : avr32
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 01:56:30
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/10a1d2750dcd1a26d4bd50e1abbf80f8dbb0150e/build-end.log
Complete log : http://autobuild.buildroot.net/results/10a1d2750dcd1a26d4bd50e1abbf80f8dbb0150e/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/10a1d2750dcd1a26d4bd50e1abbf80f8dbb0150e/config
Defconfig : http://autobuild.buildroot.net/results/10a1d2750dcd1a26d4bd50e1abbf80f8dbb0150e/defconfig
Build 0c84977b966661621195df6ff89989cc7c46eacf
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 02:02:42
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/0c84977b966661621195df6ff89989cc7c46eacf/build-end.log
Complete log : http://autobuild.buildroot.net/results/0c84977b966661621195df6ff89989cc7c46eacf/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/0c84977b966661621195df6ff89989cc7c46eacf/config
Defconfig : http://autobuild.buildroot.net/results/0c84977b966661621195df6ff89989cc7c46eacf/defconfig
Build 3e712b81947be06812e48bf310e121e634027009
==============================================
Status : NOK
Failure reason : icu-4.8.1.1
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 02:55:23
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/3e712b81947be06812e48bf310e121e634027009/build-end.log
Complete log : http://autobuild.buildroot.net/results/3e712b81947be06812e48bf310e121e634027009/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/3e712b81947be06812e48bf310e121e634027009/config
Defconfig : http://autobuild.buildroot.net/results/3e712b81947be06812e48bf310e121e634027009/defconfig
Build 31d1c341668eeb00fecb60f9cd521a4d2123d873
==============================================
Status : NOK
Failure reason : icu-4.8.1.1
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 02:59:33
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/31d1c341668eeb00fecb60f9cd521a4d2123d873/build-end.log
Complete log : http://autobuild.buildroot.net/results/31d1c341668eeb00fecb60f9cd521a4d2123d873/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/31d1c341668eeb00fecb60f9cd521a4d2123d873/config
Defconfig : http://autobuild.buildroot.net/results/31d1c341668eeb00fecb60f9cd521a4d2123d873/defconfig
Build 0946f1a89ec65fe750b391f370aa2795c2bef3ac
==============================================
Status : NOK
Failure reason : can-utils-836d3cc0122ce31a1b732d369cbd27b690c3110f
Architecture : sh2a
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 03:13:46
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/0946f1a89ec65fe750b391f370aa2795c2bef3ac/build-end.log
Complete log : http://autobuild.buildroot.net/results/0946f1a89ec65fe750b391f370aa2795c2bef3ac/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/0946f1a89ec65fe750b391f370aa2795c2bef3ac/config
Defconfig : http://autobuild.buildroot.net/results/0946f1a89ec65fe750b391f370aa2795c2bef3ac/defconfig
Build 840ec0682f889bf474671e352caf5e6381d820b3
==============================================
Status : NOK
Failure reason : squid-3.2.3
Architecture : mips
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 04:34:39
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/840ec0682f889bf474671e352caf5e6381d820b3/build-end.log
Complete log : http://autobuild.buildroot.net/results/840ec0682f889bf474671e352caf5e6381d820b3/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/840ec0682f889bf474671e352caf5e6381d820b3/config
Defconfig : http://autobuild.buildroot.net/results/840ec0682f889bf474671e352caf5e6381d820b3/defconfig
Build 53f20fb91023c5c3f2ad505eaea2c94b9bcd16dd
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 04:42:05
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/53f20fb91023c5c3f2ad505eaea2c94b9bcd16dd/build-end.log
Complete log : http://autobuild.buildroot.net/results/53f20fb91023c5c3f2ad505eaea2c94b9bcd16dd/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/53f20fb91023c5c3f2ad505eaea2c94b9bcd16dd/config
Defconfig : http://autobuild.buildroot.net/results/53f20fb91023c5c3f2ad505eaea2c94b9bcd16dd/defconfig
Build 8c84849b360d0f983a37b7cce6716050a6515d44
==============================================
Status : NOK
Failure reason : matchbox-lib-1.9
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 04:43:52
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/8c84849b360d0f983a37b7cce6716050a6515d44/build-end.log
Complete log : http://autobuild.buildroot.net/results/8c84849b360d0f983a37b7cce6716050a6515d44/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/8c84849b360d0f983a37b7cce6716050a6515d44/config
Defconfig : http://autobuild.buildroot.net/results/8c84849b360d0f983a37b7cce6716050a6515d44/defconfig
Build 0d345e497778de4aadce5c86875a9fb4d5d131c8
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 05:15:44
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/0d345e497778de4aadce5c86875a9fb4d5d131c8/build-end.log
Complete log : http://autobuild.buildroot.net/results/0d345e497778de4aadce5c86875a9fb4d5d131c8/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/0d345e497778de4aadce5c86875a9fb4d5d131c8/config
Defconfig : http://autobuild.buildroot.net/results/0d345e497778de4aadce5c86875a9fb4d5d131c8/defconfig
Build f346afde303aee7be301603c87dfd60bc4065435
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 05:29:27
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/f346afde303aee7be301603c87dfd60bc4065435/build-end.log
Complete log : http://autobuild.buildroot.net/results/f346afde303aee7be301603c87dfd60bc4065435/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/f346afde303aee7be301603c87dfd60bc4065435/config
Defconfig : http://autobuild.buildroot.net/results/f346afde303aee7be301603c87dfd60bc4065435/defconfig
Build ba86da09e9650186509e506bca36e4273022f3b4
==============================================
Status : NOK
Failure reason : mtd-1.5.0
Architecture : mips
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 06:25:09
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/ba86da09e9650186509e506bca36e4273022f3b4/build-end.log
Complete log : http://autobuild.buildroot.net/results/ba86da09e9650186509e506bca36e4273022f3b4/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/ba86da09e9650186509e506bca36e4273022f3b4/config
Defconfig : http://autobuild.buildroot.net/results/ba86da09e9650186509e506bca36e4273022f3b4/defconfig
Build de14eba75a9a49abc8449a14fa2f78baab85e452
==============================================
Status : NOK
Failure reason : libnss-3.12.9
Architecture : powerpc
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 06:51:28
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/de14eba75a9a49abc8449a14fa2f78baab85e452/build-end.log
Complete log : http://autobuild.buildroot.net/results/de14eba75a9a49abc8449a14fa2f78baab85e452/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/de14eba75a9a49abc8449a14fa2f78baab85e452/config
Defconfig : http://autobuild.buildroot.net/results/de14eba75a9a49abc8449a14fa2f78baab85e452/defconfig
Build 5d1dd1fb873c2894d6423a3196fcd3801b81d637
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 08:41:29
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/5d1dd1fb873c2894d6423a3196fcd3801b81d637/build-end.log
Complete log : http://autobuild.buildroot.net/results/5d1dd1fb873c2894d6423a3196fcd3801b81d637/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/5d1dd1fb873c2894d6423a3196fcd3801b81d637/config
Defconfig : http://autobuild.buildroot.net/results/5d1dd1fb873c2894d6423a3196fcd3801b81d637/defconfig
Build c9e9f3f3e6c4d4c2e2093d7991bbff4cd2897da4
==============================================
Status : NOK
Failure reason : squid-3.2.3
Architecture : mips
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 09:27:42
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/c9e9f3f3e6c4d4c2e2093d7991bbff4cd2897da4/build-end.log
Complete log : http://autobuild.buildroot.net/results/c9e9f3f3e6c4d4c2e2093d7991bbff4cd2897da4/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/c9e9f3f3e6c4d4c2e2093d7991bbff4cd2897da4/config
Defconfig : http://autobuild.buildroot.net/results/c9e9f3f3e6c4d4c2e2093d7991bbff4cd2897da4/defconfig
Build d63fdc05b95acd99161babc5a160ede3e52ec34f
==============================================
Status : NOK
Failure reason : netatalk-3.0
Architecture : x86_64
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 10:12:25
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/d63fdc05b95acd99161babc5a160ede3e52ec34f/build-end.log
Complete log : http://autobuild.buildroot.net/results/d63fdc05b95acd99161babc5a160ede3e52ec34f/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/d63fdc05b95acd99161babc5a160ede3e52ec34f/config
Defconfig : http://autobuild.buildroot.net/results/d63fdc05b95acd99161babc5a160ede3e52ec34f/defconfig
Build ce13c1e1eed8518299696a2b9cb474b7c375c35d
==============================================
Status : NOK
Failure reason : mplayer-1.1
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 11:19:55
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/ce13c1e1eed8518299696a2b9cb474b7c375c35d/build-end.log
Complete log : http://autobuild.buildroot.net/results/ce13c1e1eed8518299696a2b9cb474b7c375c35d/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/ce13c1e1eed8518299696a2b9cb474b7c375c35d/config
Defconfig : http://autobuild.buildroot.net/results/ce13c1e1eed8518299696a2b9cb474b7c375c35d/defconfig
Build 473a8f5773c8cdd95cd14db1d0631c3f09dbe1e7
==============================================
Status : NOK
Failure reason : directfb-1.4.17
Architecture : mips64el
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 11:38:36
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/473a8f5773c8cdd95cd14db1d0631c3f09dbe1e7/build-end.log
Complete log : http://autobuild.buildroot.net/results/473a8f5773c8cdd95cd14db1d0631c3f09dbe1e7/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/473a8f5773c8cdd95cd14db1d0631c3f09dbe1e7/config
Defconfig : http://autobuild.buildroot.net/results/473a8f5773c8cdd95cd14db1d0631c3f09dbe1e7/defconfig
Build 6cceb457c76eb7b0fa65931b7ba5d9073c9a029a
==============================================
Status : NOK
Failure reason : sconeserver-180
Architecture : mipsel
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 12:24:15
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/6cceb457c76eb7b0fa65931b7ba5d9073c9a029a/build-end.log
Complete log : http://autobuild.buildroot.net/results/6cceb457c76eb7b0fa65931b7ba5d9073c9a029a/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/6cceb457c76eb7b0fa65931b7ba5d9073c9a029a/config
Defconfig : http://autobuild.buildroot.net/results/6cceb457c76eb7b0fa65931b7ba5d9073c9a029a/defconfig
Build f6413c5addbf5049c0a25c3cc58f934f207f6f6b
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 13:36:27
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/f6413c5addbf5049c0a25c3cc58f934f207f6f6b/build-end.log
Complete log : http://autobuild.buildroot.net/results/f6413c5addbf5049c0a25c3cc58f934f207f6f6b/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/f6413c5addbf5049c0a25c3cc58f934f207f6f6b/config
Defconfig : http://autobuild.buildroot.net/results/f6413c5addbf5049c0a25c3cc58f934f207f6f6b/defconfig
Build 28ecc5d062dbf51c04e298e20f6ecdd1666a8064
==============================================
Status : NOK
Failure reason : ffmpeg-0.8.12
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 13:53:10
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/28ecc5d062dbf51c04e298e20f6ecdd1666a8064/build-end.log
Complete log : http://autobuild.buildroot.net/results/28ecc5d062dbf51c04e298e20f6ecdd1666a8064/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/28ecc5d062dbf51c04e298e20f6ecdd1666a8064/config
Defconfig : http://autobuild.buildroot.net/results/28ecc5d062dbf51c04e298e20f6ecdd1666a8064/defconfig
Build 758d699d7cfd53b67df76d8567f00318bde11f68
==============================================
Status : NOK
Failure reason : alsa-lib-1.0.26
Architecture : bfin
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 13:53:35
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/758d699d7cfd53b67df76d8567f00318bde11f68/build-end.log
Complete log : http://autobuild.buildroot.net/results/758d699d7cfd53b67df76d8567f00318bde11f68/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/758d699d7cfd53b67df76d8567f00318bde11f68/config
Defconfig : http://autobuild.buildroot.net/results/758d699d7cfd53b67df76d8567f00318bde11f68/defconfig
Build e5e80020d82ddcff80fbaf6ee2be9225717cdcb3
==============================================
Status : NOK
Failure reason : ltrace-0.6.0
Architecture : aarch64
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 13:55:12
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/e5e80020d82ddcff80fbaf6ee2be9225717cdcb3/build-end.log
Complete log : http://autobuild.buildroot.net/results/e5e80020d82ddcff80fbaf6ee2be9225717cdcb3/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/e5e80020d82ddcff80fbaf6ee2be9225717cdcb3/config
Defconfig : http://autobuild.buildroot.net/results/e5e80020d82ddcff80fbaf6ee2be9225717cdcb3/defconfig
Build 3e8e57e1a119cc04c7e658a860f56b2df7bd434e
==============================================
Status : NOK
Failure reason : boost-1.49.0
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 14:00:29
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/3e8e57e1a119cc04c7e658a860f56b2df7bd434e/build-end.log
Complete log : http://autobuild.buildroot.net/results/3e8e57e1a119cc04c7e658a860f56b2df7bd434e/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/3e8e57e1a119cc04c7e658a860f56b2df7bd434e/config
Defconfig : http://autobuild.buildroot.net/results/3e8e57e1a119cc04c7e658a860f56b2df7bd434e/defconfig
Build 37fbd467803fbd166764b72d15569e82eea0f813
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 14:30:20
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/37fbd467803fbd166764b72d15569e82eea0f813/build-end.log
Complete log : http://autobuild.buildroot.net/results/37fbd467803fbd166764b72d15569e82eea0f813/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/37fbd467803fbd166764b72d15569e82eea0f813/config
Defconfig : http://autobuild.buildroot.net/results/37fbd467803fbd166764b72d15569e82eea0f813/defconfig
Build 3d79e0977cb1dfa04f155ab897f0675888082d58
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 14:44:17
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/3d79e0977cb1dfa04f155ab897f0675888082d58/build-end.log
Complete log : http://autobuild.buildroot.net/results/3d79e0977cb1dfa04f155ab897f0675888082d58/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/3d79e0977cb1dfa04f155ab897f0675888082d58/config
Defconfig : http://autobuild.buildroot.net/results/3d79e0977cb1dfa04f155ab897f0675888082d58/defconfig
Build dcd80336364417009eb8576f478408d89b2bd366
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 14:57:28
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/dcd80336364417009eb8576f478408d89b2bd366/build-end.log
Complete log : http://autobuild.buildroot.net/results/dcd80336364417009eb8576f478408d89b2bd366/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/dcd80336364417009eb8576f478408d89b2bd366/config
Defconfig : http://autobuild.buildroot.net/results/dcd80336364417009eb8576f478408d89b2bd366/defconfig
Build 08aea0d2f39d714f351041333bad284b9ef59b51
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 15:11:31
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/08aea0d2f39d714f351041333bad284b9ef59b51/build-end.log
Complete log : http://autobuild.buildroot.net/results/08aea0d2f39d714f351041333bad284b9ef59b51/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/08aea0d2f39d714f351041333bad284b9ef59b51/config
Defconfig : http://autobuild.buildroot.net/results/08aea0d2f39d714f351041333bad284b9ef59b51/defconfig
Build 2cc04b0a77226e79ba65eb0fe21ebb286bc7878e
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 15:42:41
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/2cc04b0a77226e79ba65eb0fe21ebb286bc7878e/build-end.log
Complete log : http://autobuild.buildroot.net/results/2cc04b0a77226e79ba65eb0fe21ebb286bc7878e/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/2cc04b0a77226e79ba65eb0fe21ebb286bc7878e/config
Defconfig : http://autobuild.buildroot.net/results/2cc04b0a77226e79ba65eb0fe21ebb286bc7878e/defconfig
Build d4fd6021219963dd357a5c027d39f4144078b0cd
==============================================
Status : NOK
Failure reason : libffi-3.0.11
Architecture : xtensa
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 15:45:18
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/d4fd6021219963dd357a5c027d39f4144078b0cd/build-end.log
Complete log : http://autobuild.buildroot.net/results/d4fd6021219963dd357a5c027d39f4144078b0cd/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/d4fd6021219963dd357a5c027d39f4144078b0cd/config
Defconfig : http://autobuild.buildroot.net/results/d4fd6021219963dd357a5c027d39f4144078b0cd/defconfig
Build 56d53a4d7a708fd51673c94a2d32ddc99614b7f5
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 17:17:00
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/56d53a4d7a708fd51673c94a2d32ddc99614b7f5/build-end.log
Complete log : http://autobuild.buildroot.net/results/56d53a4d7a708fd51673c94a2d32ddc99614b7f5/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/56d53a4d7a708fd51673c94a2d32ddc99614b7f5/config
Defconfig : http://autobuild.buildroot.net/results/56d53a4d7a708fd51673c94a2d32ddc99614b7f5/defconfig
Build cd71721b9c70d20d874a67a1d99b4e08b5eeb427
==============================================
Status : NOK
Failure reason : qt-4.8.3
Architecture : aarch64
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 17:51:36
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/cd71721b9c70d20d874a67a1d99b4e08b5eeb427/build-end.log
Complete log : http://autobuild.buildroot.net/results/cd71721b9c70d20d874a67a1d99b4e08b5eeb427/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/cd71721b9c70d20d874a67a1d99b4e08b5eeb427/config
Defconfig : http://autobuild.buildroot.net/results/cd71721b9c70d20d874a67a1d99b4e08b5eeb427/defconfig
Build b1e9c3777ce274e9893f623f523ef699fc1d25e4
==============================================
Status : NOK
Failure reason : libffi-3.0.11
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 19:01:38
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/b1e9c3777ce274e9893f623f523ef699fc1d25e4/build-end.log
Complete log : http://autobuild.buildroot.net/results/b1e9c3777ce274e9893f623f523ef699fc1d25e4/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/b1e9c3777ce274e9893f623f523ef699fc1d25e4/config
Defconfig : http://autobuild.buildroot.net/results/b1e9c3777ce274e9893f623f523ef699fc1d25e4/defconfig
Build 69bf6ab75bdef0c54d0cb0567d6e6b82183d2e3b
==============================================
Status : NOK
Failure reason : icu-4.8.1.1
Architecture : arm
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 19:07:36
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/69bf6ab75bdef0c54d0cb0567d6e6b82183d2e3b/build-end.log
Complete log : http://autobuild.buildroot.net/results/69bf6ab75bdef0c54d0cb0567d6e6b82183d2e3b/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/69bf6ab75bdef0c54d0cb0567d6e6b82183d2e3b/config
Defconfig : http://autobuild.buildroot.net/results/69bf6ab75bdef0c54d0cb0567d6e6b82183d2e3b/defconfig
Build 16d79facc4905989e77e726bdeed2c4a463272fd
==============================================
Status : NOK
Failure reason : connman-1.8
Architecture : avr32
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 19:21:11
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/16d79facc4905989e77e726bdeed2c4a463272fd/build-end.log
Complete log : http://autobuild.buildroot.net/results/16d79facc4905989e77e726bdeed2c4a463272fd/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/16d79facc4905989e77e726bdeed2c4a463272fd/config
Defconfig : http://autobuild.buildroot.net/results/16d79facc4905989e77e726bdeed2c4a463272fd/defconfig
Build 342cd2bedd1d66ee1b581ede40f3e7d421b55e59
==============================================
Status : NOK
Failure reason : host-python-2.7.2
Architecture : powerpc
Submitted by : Peter Korsgaard (gcc14)
Submitted at : 2012-11-27 19:27:05
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/342cd2bedd1d66ee1b581ede40f3e7d421b55e59/build-end.log
Complete log : http://autobuild.buildroot.net/results/342cd2bedd1d66ee1b581ede40f3e7d421b55e59/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/342cd2bedd1d66ee1b581ede40f3e7d421b55e59/config
Defconfig : http://autobuild.buildroot.net/results/342cd2bedd1d66ee1b581ede40f3e7d421b55e59/defconfig
Build b9ee0cf67d6871b784f39e8576138e9341498673
==============================================
Status : NOK
Failure reason : alsa-lib-1.0.26
Architecture : bfin
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 20:17:53
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/b9ee0cf67d6871b784f39e8576138e9341498673/build-end.log
Complete log : http://autobuild.buildroot.net/results/b9ee0cf67d6871b784f39e8576138e9341498673/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/b9ee0cf67d6871b784f39e8576138e9341498673/config
Defconfig : http://autobuild.buildroot.net/results/b9ee0cf67d6871b784f39e8576138e9341498673/defconfig
Build 3edd4d522aadd7710934c2b115a2d52d7c27a0de
==============================================
Status : NOK
Failure reason : libfuse-2.9.2
Architecture : aarch64
Submitted by : Thomas Petazzoni (Free Electrons build server)
Submitted at : 2012-11-27 20:29:03
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/3edd4d522aadd7710934c2b115a2d52d7c27a0de/build-end.log
Complete log : http://autobuild.buildroot.net/results/3edd4d522aadd7710934c2b115a2d52d7c27a0de/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/3edd4d522aadd7710934c2b115a2d52d7c27a0de/config
Defconfig : http://autobuild.buildroot.net/results/3edd4d522aadd7710934c2b115a2d52d7c27a0de/defconfig
Build f38e6dbaadf65f8e99165dea0378cb59bd71ddf3
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 20:57:55
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/f38e6dbaadf65f8e99165dea0378cb59bd71ddf3/build-end.log
Complete log : http://autobuild.buildroot.net/results/f38e6dbaadf65f8e99165dea0378cb59bd71ddf3/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/f38e6dbaadf65f8e99165dea0378cb59bd71ddf3/config
Defconfig : http://autobuild.buildroot.net/results/f38e6dbaadf65f8e99165dea0378cb59bd71ddf3/defconfig
Build 22734272fc6182a206c3d53765991134c697fd4a
==============================================
Status : NOK
Failure reason : host-libglib2-2.30.3
Architecture : i686
Submitted by : Peter Korsgaard (gcc110)
Submitted at : 2012-11-27 21:18:22
Git commit ID : http://git.buildroot.net/buildroot/commit/?id=3bdbe9abb90de0262832d5d545f239fa41fb0e91
End of log : http://autobuild.buildroot.net/results/22734272fc6182a206c3d53765991134c697fd4a/build-end.log
Complete log : http://autobuild.buildroot.net/results/22734272fc6182a206c3d53765991134c697fd4a/build.log.bz2
Configuration : http://autobuild.buildroot.net/results/22734272fc6182a206c3d53765991134c697fd4a/config
Defconfig : http://autobuild.buildroot.net/results/22734272fc6182a206c3d53765991134c697fd4a/defconfig
--
http://autobuild.buildroot.net
^ permalink raw reply
* [Buildroot] [git commit branch/next] package: add gd package
From: Baruch Siach @ 2012-11-28 5:26 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20121128011244.B677B8F461@busybox.osuosl.org>
Hi Peter,
On Tue, Nov 27, 2012 at 11:21:06AM -0800, Peter Korsgaard wrote:
[...]
> +GD_TOOLS_ += gdlib-config
Shouldn't this be 'GD_TOOLS_y'?
> +GD_TOOLS_$(BR2_PACKAGE_GD_ANNOTATE) += annotate
> +GD_TOOLS_$(BR2_PACKAGE_GD_BDFTOGD) += bdftogd
> +GD_TOOLS_$(BR2_PACKAGE_GD_GD2COPYPAL) += gd2copypal
> +GD_TOOLS_$(BR2_PACKAGE_GD_GD2TOGIF) += gd2togif
> +GD_TOOLS_$(BR2_PACKAGE_GD_GD2TOPNG) += gd2topng
> +GD_TOOLS_$(BR2_PACKAGE_GD_GDCMPGIF) += gdcmpgif
> +GD_TOOLS_$(BR2_PACKAGE_GD_GDPARTTOPNG) += gdparttopng
> +GD_TOOLS_$(BR2_PACKAGE_GD_GDTOPNG) += gdtopng
> +GD_TOOLS_$(BR2_PACKAGE_GD_GIFTOGD2) += giftogd2
> +GD_TOOLS_$(BR2_PACKAGE_GD_PNGTOGD) += pngtogd
> +GD_TOOLS_$(BR2_PACKAGE_GD_PNGTOGD2) += pngtogd2
> +GD_TOOLS_$(BR2_PACKAGE_GD_WEBPNG) += webpng
> +
> +define GD_REMOVE_TOOLS
> + rm -f $(addprefix $(TARGET_DIR)/usr/bin/,$(GD_TOOLS_))
And here.
> +endef
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
^ permalink raw reply
* [Buildroot] PATCH > To integrate pycrypto into Buildroot
From: Noel Roberts @ 2012-11-28 5:05 UTC (permalink / raw)
To: buildroot
This patch allows Buildroot to cross compile the crypto libraries needed for python integration, enabling good cryptographic support within Python.
This is my first patch submission - please advise me, if I need to rework anything.
[Below is the original developer?s permission for inclusion]
Regards
Noel
From: Dwayne Litzenberger [mailto:dlitz at dlitz.net]
Sent: Wednesday, 28 November 2012 9:01 AM
To: Noel Roberts
Subject: Re: Including pycrypto in Buildroot
You don't need my permission. Go nuts!
Out of curiosity, what uses PyCryptoin buildroot?
Noel Roberts <Noel.Roberts at brisbane.qld.gov.au<mailto:Noel.Roberts@brisbane.qld.gov.au>> wrote:
Good day
Would you object to me submitting a patch to buildroot, to allow the inclusion of pycrypto within the buildroot environment?
Regards
Noel
**************************************************** This message has passed through an insecure network. Please direct all enquiries to the message author. ****************************************************
**************************************************** This message has passed through an insecure network. Please direct all enquiries to the message author. ****************************************************
****************************************************
This message has passed through an insecure network.
Please direct all enquiries to the message author.
****************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121128/5d0f509c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Adding-pyCrypto-functionality-in-Buildroot.patch
Type: application/octet-stream
Size: 1759 bytes
Desc: 0001-Adding-pyCrypto-functionality-in-Buildroot.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121128/5d0f509c/attachment.obj>
^ permalink raw reply
* [Buildroot] Problem building libglib2
From: Charles Manning @ 2012-11-28 1:37 UTC (permalink / raw)
To: buildroot
Hello
I'm a buildroot newbie and am trying to figure out what went wrong here.
make[5]: Entering directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
CCLD libgobject-2.0.la
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
skipping incompatible /lib/libpthread.so.0 when searching for
/lib/libpthread.so.0
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /lib/libpthread.so.0
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
skipping incompatible /usr/lib/libpthread_nonshared.a when searching
for /usr/lib/libpthread_nonshared.a
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /usr/lib/libpthread_nonshared.a
collect2: ld returned 1 exit status
make[5]: *** [libgobject-2.0.la] Error 1
make[5]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3'
make: *** [/opt/buildroot/buildroot/output/build/libglib2-2.30.3/.stamp_built]
Error 2
As far as I can tell, this failed building libglib because various
files were missing. For example /lib/libpthread.so.0.
However if I look in staging, that file exists:
charles at charles-laptop:/opt/buildroot/buildroot$ ls -al
output/staging/lib/libp*
-rwxr-xr-x 1 charles charles 19467 2012-05-29 00:41
output/staging/lib/libpcprofile.so
-rwxr-xr-x 1 charles charles 144489 2012-05-29 00:41
output/staging/lib/libpthread-2.15.so
lrwxrwxrwx 1 charles charles 18 2012-11-28 12:03
output/staging/lib/libpthread.so.0 -> libpthread-2.15.so
charles at charles-laptop:/opt/buildroot/buildroot$
So... please help the newbie....
Thanks
Charles
^ permalink raw reply
* [Buildroot] [PATCH for-next 1/3] toolchain-external: add Linaro 2012.11
From: Peter Korsgaard @ 2012-11-28 1:12 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354025223-14474-1-git-send-email-thomas.petazzoni@free-electrons.com>
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Committed series to next, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] toolchain-external: on ARM, show comment about the availability of Linaro toolchains
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=90f763c77d2316c2fdefa1301e96d5b31376e2cf
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
On ARM, Linaro external toolchains are only visible if the user
selects Cortex-A8 or Cortex-A9. Therefore, we add a comment that tells
the user that the Linaro toolchains are only available under those
conditions.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 469c283..4fe605d 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -54,6 +54,10 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
To use this toolchain, you must disable soft float usage.
+comment "Linaro toolchains available for Cortex-A{8,9}"
+ depends on BR2_arm
+ depends on !BR2_cortex_a8 && !BR2_cortex_a9
+
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
bool "Sourcery CodeBench ARM 2012.03"
depends on BR2_arm
^ permalink raw reply related
* [Buildroot] [git commit branch/next] toolchain-external: on ARM, show comment about the availability of Linaro toolchains
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=90f763c77d2316c2fdefa1301e96d5b31376e2cf
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/next
On ARM, Linaro external toolchains are only visible if the user
selects Cortex-A8 or Cortex-A9. Therefore, we add a comment that tells
the user that the Linaro toolchains are only available under those
conditions.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 469c283..4fe605d 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -54,6 +54,10 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
To use this toolchain, you must disable soft float usage.
+comment "Linaro toolchains available for Cortex-A{8,9}"
+ depends on BR2_arm
+ depends on !BR2_cortex_a8 && !BR2_cortex_a9
+
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
bool "Sourcery CodeBench ARM 2012.03"
depends on BR2_arm
^ permalink raw reply related
* [Buildroot] [git commit] toolchain-external: remove Linaro 2012.08
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=ba60360e412663f581848c9f61d1b4dd6c4edce2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 18 ------------------
toolchain/toolchain-external/ext-tool.mk | 3 ---
2 files changed, 0 insertions(+), 21 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 56630fa..469c283 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -54,23 +54,6 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
To use this toolchain, you must disable soft float usage.
-config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
- bool "Linaro 2012.08"
- depends on BR2_arm
- depends on BR2_cortex_a8 || BR2_cortex_a9
- select BR2_TOOLCHAIN_EXTERNAL_GLIBC
- select BR2_TOOLCHAIN_HAS_NATIVE_RPC
- select BR2_INSTALL_LIBSTDCPP
- help
- Linaro toolchain for the ARM architecture. It uses Linaro
- GCC 2012.08 (based on gcc 4.7), Linaro GDB 2012.06 (based on
- GDB 7.4), eglibc 2.15. It generates code that runs on all
- Cortex-A profile devices, but tuned for the Cortex-A9. The
- code generated is Thumb 2, with the hard floating point
- calling convention, and uses the VFPv3-D16 FPU instructions.
-
- To use this toolchain, you must disable soft float usage.
-
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
bool "Sourcery CodeBench ARM 2012.03"
depends on BR2_arm
@@ -641,7 +624,6 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX
config BR2_TOOLCHAIN_EXTERNAL_PREFIX
string
- default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index d98fcc6..4429480 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -184,9 +184,6 @@ TOOLCHAIN_EXTERNAL_SOURCE=arm-2011.09-70-arm-none-linux-gnueabi-i686-pc-linux-gn
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y)
TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/
TOOLCHAIN_EXTERNAL_SOURCE=arm-2012.03-57-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
-else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08),y)
-TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.08/+download/
-TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.tar.bz2
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09),y)
TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.09/+download/
TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.tar.bz2
^ permalink raw reply related
* [Buildroot] [git commit branch/next] toolchain-external: remove Linaro 2012.08
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=ba60360e412663f581848c9f61d1b4dd6c4edce2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/next
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 18 ------------------
toolchain/toolchain-external/ext-tool.mk | 3 ---
2 files changed, 0 insertions(+), 21 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 56630fa..469c283 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -54,23 +54,6 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
To use this toolchain, you must disable soft float usage.
-config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
- bool "Linaro 2012.08"
- depends on BR2_arm
- depends on BR2_cortex_a8 || BR2_cortex_a9
- select BR2_TOOLCHAIN_EXTERNAL_GLIBC
- select BR2_TOOLCHAIN_HAS_NATIVE_RPC
- select BR2_INSTALL_LIBSTDCPP
- help
- Linaro toolchain for the ARM architecture. It uses Linaro
- GCC 2012.08 (based on gcc 4.7), Linaro GDB 2012.06 (based on
- GDB 7.4), eglibc 2.15. It generates code that runs on all
- Cortex-A profile devices, but tuned for the Cortex-A9. The
- code generated is Thumb 2, with the hard floating point
- calling convention, and uses the VFPv3-D16 FPU instructions.
-
- To use this toolchain, you must disable soft float usage.
-
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
bool "Sourcery CodeBench ARM 2012.03"
depends on BR2_arm
@@ -641,7 +624,6 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX
config BR2_TOOLCHAIN_EXTERNAL_PREFIX
string
- default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index d98fcc6..4429480 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -184,9 +184,6 @@ TOOLCHAIN_EXTERNAL_SOURCE=arm-2011.09-70-arm-none-linux-gnueabi-i686-pc-linux-gn
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y)
TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/
TOOLCHAIN_EXTERNAL_SOURCE=arm-2012.03-57-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
-else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08),y)
-TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.08/+download/
-TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.tar.bz2
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09),y)
TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.09/+download/
TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.tar.bz2
^ permalink raw reply related
* [Buildroot] [git commit] toolchain-external: add Linaro 2012.11
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=008f635d29310b55e0bb3e9a1a6009f12f7f7400
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 18 ++++++++++++++++++
toolchain/toolchain-external/ext-tool.mk | 3 +++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index f04ced6..56630fa 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -3,6 +3,23 @@ if BR2_TOOLCHAIN_EXTERNAL
choice
prompt "Toolchain"
+config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
+ bool "Linaro 2012.11"
+ depends on BR2_arm
+ depends on BR2_cortex_a8 || BR2_cortex_a9
+ select BR2_TOOLCHAIN_EXTERNAL_GLIBC
+ select BR2_TOOLCHAIN_HAS_NATIVE_RPC
+ select BR2_INSTALL_LIBSTDCPP
+ help
+ Linaro toolchain for the ARM architecture. It uses Linaro
+ GCC 2012.11 (based on gcc 4.7), Linaro GDB 2012.10 (based on
+ GDB 7.5), eglibc 2.15. It generates code that runs on all
+ Cortex-A profile devices, but tuned for the Cortex-A9. The
+ code generated is Thumb 2, with the hard floating point
+ calling convention, and uses the VFPv3-D16 FPU instructions.
+
+ To use this toolchain, you must disable soft float usage.
+
config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
bool "Linaro 2012.10"
depends on BR2_arm
@@ -627,6 +644,7 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
+ default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201103
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index a6025db..d98fcc6 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -193,6 +193,9 @@ TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10),y)
TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.10/+download/
TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2
+else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11),y)
+TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.11/+download/
+TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux.tar.bz2
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS44),y)
TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/sgpp/lite/mips/portal/package7401/public/mips-linux-gnu/
TOOLCHAIN_EXTERNAL_SOURCE=mips-4.4-303-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2
^ permalink raw reply related
* [Buildroot] [git commit branch/next] toolchain-external: add Linaro 2012.11
From: Peter Korsgaard @ 2012-11-28 1:11 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=008f635d29310b55e0bb3e9a1a6009f12f7f7400
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/next
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
toolchain/toolchain-external/Config.in | 18 ++++++++++++++++++
toolchain/toolchain-external/ext-tool.mk | 3 +++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index f04ced6..56630fa 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -3,6 +3,23 @@ if BR2_TOOLCHAIN_EXTERNAL
choice
prompt "Toolchain"
+config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
+ bool "Linaro 2012.11"
+ depends on BR2_arm
+ depends on BR2_cortex_a8 || BR2_cortex_a9
+ select BR2_TOOLCHAIN_EXTERNAL_GLIBC
+ select BR2_TOOLCHAIN_HAS_NATIVE_RPC
+ select BR2_INSTALL_LIBSTDCPP
+ help
+ Linaro toolchain for the ARM architecture. It uses Linaro
+ GCC 2012.11 (based on gcc 4.7), Linaro GDB 2012.10 (based on
+ GDB 7.5), eglibc 2.15. It generates code that runs on all
+ Cortex-A profile devices, but tuned for the Cortex-A9. The
+ code generated is Thumb 2, with the hard floating point
+ calling convention, and uses the VFPv3-D16 FPU instructions.
+
+ To use this toolchain, you must disable soft float usage.
+
config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
bool "Linaro 2012.10"
depends on BR2_arm
@@ -627,6 +644,7 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
+ default "arm-linux-gnueabihf" if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201103
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201109
default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index a6025db..d98fcc6 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -193,6 +193,9 @@ TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10),y)
TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.10/+download/
TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2
+else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_11),y)
+TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.11/+download/
+TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux.tar.bz2
else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS44),y)
TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/sgpp/lite/mips/portal/package7401/public/mips-linux-gnu/
TOOLCHAIN_EXTERNAL_SOURCE=mips-4.4-303-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2
^ permalink raw reply related
* [Buildroot] [PATCHv3 for-2012.11 1/5] manual: trivial fixes
From: Peter Korsgaard @ 2012-11-28 1:10 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354053560-30352-1-git-send-email-arnout@mind.be>
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
Arnout> From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Arnout> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Arnout> ---
Arnout> As promised, here is the series with the trivial fixes split off.
Arnout> This patch doesn't require review IMHO.
Committed series, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] manual: restructure 'Adding packages' chapter
From: Peter Korsgaard @ 2012-11-28 1:08 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=722b82f05bd7e2b46661c721daad99125e655b76
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
The depends-on-vs-select part of the manual really deserves its own
section title (especially because it is referred to and the xref gets
a 'sinpara' in PDF if the section doesn't have a title). So restructure
the surrounding sections to reduce the section nesting depth.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
docs/manual/adding-packages-directory.txt | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
index 5903ed1..5d17aac 100644
--- a/docs/manual/adding-packages-directory.txt
+++ b/docs/manual/adding-packages-directory.txt
@@ -13,7 +13,7 @@ New subdirectories are discouraged, however.
+Config.in+ file
-^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~
Then, create a file named +Config.in+. This file will contain the
option descriptions related to our +libfoo+ software that will be used
@@ -51,6 +51,9 @@ source "package/libfoo/Config.in"
--------------------------
[[depends-on-vs-select]]
+Choosing +depends on+ or +select+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
The +Config.in+ file of your package must also ensure that
dependencies are enabled. Typically, Buildroot uses the following
rules:
@@ -164,7 +167,7 @@ Further formatting details: see xref:writing-rules-config-in[the
coding style].
The +.mk+ file
-^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~
Finally, here's the hardest part. Create a file named +libfoo.mk+. It
describes how the package should be downloaded, configured, built,
^ permalink raw reply related
* [Buildroot] [git commit] manual: give example where _INSTALL_TARGET = NO
From: Peter Korsgaard @ 2012-11-28 1:07 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=50b32848c2e8065a4b3646a5e0c17a0adb54781e
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
The tutorial for autotools-package and cmake-package currently gives
the bad example of setting _INSTALL_TARGET to YES, which is the default.
So change this into an example with _INSTALL_TARGET = NO, and explain in
which case this is relevant.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
docs/manual/adding-packages-autotools.txt | 16 ++++++++--------
docs/manual/adding-packages-cmake.txt | 14 +++++++-------
2 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/docs/manual/adding-packages-autotools.txt b/docs/manual/adding-packages-autotools.txt
index 4127df4..84d76f9 100644
--- a/docs/manual/adding-packages-autotools.txt
+++ b/docs/manual/adding-packages-autotools.txt
@@ -21,8 +21,8 @@ package, with an example :
07: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
08: LIBFOO_SITE = http://www.foosoftware.org/download
09: LIBFOO_INSTALL_STAGING = YES
-10: LIBFOO_INSTALL_TARGET = YES
-11: LIBFOO_CONF_OPT = --enable-shared
+10: LIBFOO_INSTALL_TARGET = NO
+11: LIBFOO_CONF_OPT = --disable-shared
12: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
13:
14: $(eval $(autotools-package))
@@ -44,13 +44,13 @@ other libraries or applications depending on them. Also by default, when
staging installation is enabled, packages are installed in this location
using the +make install+ command.
-On line 10, we tell Buildroot to also install the package to the
+On line 10, we tell Buildroot to not install the package to the
target directory. This directory contains what will become the root
-filesystem running on the target. Usually, we try not to install header
-files and to install stripped versions of the binary. By default, target
-installation is enabled, so in fact, this line is not strictly
-necessary. Also by default, packages are installed in this location
-using the +make install+ command.
+filesystem running on the target. For purely static libraries, it is
+not necessary to install them in the target directory because they will
+not be used at runtime. By default, target installation is enabled; setting
+this variable to NO is almost never needed. Also by default, packages are
+installed in this location using the +make install+ command.
On line 11, we tell Buildroot to pass a custom configure option, that
will be passed to the +./configure+ script before configuring
diff --git a/docs/manual/adding-packages-cmake.txt b/docs/manual/adding-packages-cmake.txt
index 4a9e893..bb1705b 100644
--- a/docs/manual/adding-packages-cmake.txt
+++ b/docs/manual/adding-packages-cmake.txt
@@ -21,7 +21,7 @@ with an example :
07: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
08: LIBFOO_SITE = http://www.foosoftware.org/download
09: LIBFOO_INSTALL_STAGING = YES
-10: LIBFOO_INSTALL_TARGET = YES
+10: LIBFOO_INSTALL_TARGET = NO
11: LIBFOO_CONF_OPT = -DBUILD_DEMOS=ON
12: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
13:
@@ -44,13 +44,13 @@ other libraries or applications depending on them. Also by default, when
staging installation is enabled, packages are installed in this location
using the +make install+ command.
-On line 10, we tell Buildroot to also install the package to the
+On line 10, we tell Buildroot to not install the package to the
target directory. This directory contains what will become the root
-filesystem running on the target. Usually, we try not to install header
-files and to install stripped versions of the binary. By default, target
-installation is enabled, so in fact, this line is not strictly
-necessary. Also by default, packages are installed in this location
-using the +make install+ command.
+filesystem running on the target. For purely static libraries, it is
+not necessary to install them in the target directory because they will
+not be used at runtime. By default, target installation is enabled; setting
+this variable to NO is almost never needed. Also by default, packages are
+installed in this location using the +make install+ command.
On line 11, we tell Buildroot to pass custom options to CMake when it is
configuring the package.
^ permalink raw reply related
* [Buildroot] [git commit] manual: more warnings to not use output/target
From: Peter Korsgaard @ 2012-11-28 1:07 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=13562ddd2ac2f15e14d5f244675bc3ab2bc63fb2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
docs/manual/using.txt | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index 6e144d0..857aa33 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -86,7 +86,8 @@ This directory contains several subdirectories:
* +target/+ which contains 'almost' the complete root filesystem for
the target: everything needed is present except the device files in
+/dev/+ (Buildroot can't create them because Buildroot doesn't run
- as root and doesn't want to run as root). Therefore, this directory
+ as root and doesn't want to run as root). Also, it doesn't have the correct
+ permissions (e.g. setuid for the busybox binary). Therefore, this directory
*should not be used on your target*. Instead, you should use one of
the images built in the +images/+ directory. If you need an
extracted image of the root filesystem for booting over NFS, then
^ permalink raw reply related
* [Buildroot] [git commit] manual: various fixes
From: Peter Korsgaard @ 2012-11-28 1:07 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=65f66c170e6703cf1b75574e7aabea1302f51c50
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Various consistency and correctness improvements.
Also removing some sentences that are not or no longer relevant.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
docs/manual/adding-packages-conclusion.txt | 3 +-
docs/manual/adding-packages-directory.txt | 13 ++++---
docs/manual/adding-packages-generic.txt | 25 +++++++------
docs/manual/adding-packages-gettext.txt | 20 ++++++----
docs/manual/adding-packages-tips.txt | 30 +++++++++++-----
docs/manual/beyond-buildroot.txt | 2 +
docs/manual/board-support.txt | 4 +-
docs/manual/customize-toolchain.txt | 3 +-
docs/manual/download-location.txt | 14 +++++---
docs/manual/embedded-basics.txt | 4 ++-
docs/manual/faq-troubleshooting.txt | 8 +++-
docs/manual/how-buildroot-works.txt | 33 +++++++++++------
docs/manual/legal-notice.txt | 33 +++++++++---------
docs/manual/makedev-syntax.txt | 3 +-
docs/manual/package-make-target.txt | 51 +++++++++++----------------
docs/manual/patch-policy.txt | 27 ++++++++-------
docs/manual/prerequisite.txt | 4 +--
docs/manual/rebuilding-packages.txt | 40 ++++++++--------------
docs/manual/using.txt | 4 +-
docs/manual/writing-rules.txt | 37 +++++++++++++------
20 files changed, 193 insertions(+), 165 deletions(-)
diff --git a/docs/manual/adding-packages-conclusion.txt b/docs/manual/adding-packages-conclusion.txt
index 137b7c3..0f6f0ca 100644
--- a/docs/manual/adding-packages-conclusion.txt
+++ b/docs/manual/adding-packages-conclusion.txt
@@ -8,5 +8,6 @@ matter of writing a Makefile using an existing example and modifying it
according to the compilation process required by the package.
If you package software that might be useful for other people, don't
-forget to send a patch to the Buildroot mailing list!
+forget to send a patch to the Buildroot mailing list (see
+xref:submitting-patches[])!
diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
index 88a4645..5903ed1 100644
--- a/docs/manual/adding-packages-directory.txt
+++ b/docs/manual/adding-packages-directory.txt
@@ -9,6 +9,7 @@ your software, for example +libfoo+.
Some packages have been grouped by topic in a sub-directory:
+multimedia+, +x11r7+, +efl+ and +matchbox+. If your package fits in
one of these categories, then create your package directory in these.
+New subdirectories are discouraged, however.
+Config.in+ file
@@ -32,12 +33,12 @@ configuration option must be indented with one tab. The help text
itself should be indented with one tab and two spaces, and it must
mention the upstream URL of the project.
-Of course, you can add other sub-options into a +if
+You can add other sub-options into a +if
BR2_PACKAGE_LIBFOO...endif+ statement to configure particular things
in your software. You can look at examples in other packages. The
syntax of the +Config.in+ file is the same as the one for the kernel
Kconfig file. The documentation for this syntax is available at
-http://lxr.free-electrons.com/source/Documentation/kbuild/kconfig-language.txt[]
+http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[]
Finally you have to add your new +libfoo/Config.in+ to
+package/Config.in+ (or in a category subdirectory if you decided to
@@ -68,9 +69,9 @@ rules:
dependency for dependencies on toolchain options (target
architecture, MMU support, C library, C++ support, large file
support, thread support, RPC support, IPV6 support, WCHAR support),
- or for dependencies on "big" things, such as the X.org system. In
- some cases, especially dependency on toolchain options, it is
- recommended to add a +comment+ displayed when the option is not
+ or for dependencies on "big" things, such as the X.org system. For
+ dependencies on toolchain options, there should be a +comment+ that
+ is displayed when the option is not
enabled, so that the user knows why the package is not available.
The +depends on+ keyword express the dependency with a forward
semantic.
@@ -160,7 +161,7 @@ so, the dependency also needs to be expressed in the +.mk+ file of the
package.
Further formatting details: see xref:writing-rules-config-in[the
-writing rules].
+coding style].
The +.mk+ file
^^^^^^^^^^^^^^
diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
index ee96bc1..3f21f86 100644
--- a/docs/manual/adding-packages-generic.txt
+++ b/docs/manual/adding-packages-generic.txt
@@ -151,11 +151,11 @@ information is (assuming the package name is +libfoo+) :
* +LIBFOO_PATCH+ may contain the name of a patch, that will be
downloaded from the same location as the tarball indicated in
+LIBFOO_SOURCE+. If +HOST_LIBFOO_PATCH+ is not specified, it
- defaults to +LIBFOO_PATCH+. Also note that another mechanism is
- available to patch a package: all files of the form
- +packagename-packageversion-description.patch+ present in the
- package directory inside Buildroot will be applied to the package
- after extraction.
+ defaults to +LIBFOO_PATCH+. Note that patches that are included
+ in Buildroot itself use a different mechanism: all files of the
+ form +<packagename>-*.patch+ present in the package directory inside
+ Buildroot will be applied to the package after extraction (see
+ xref:patch-policy[patching a package]).
* +LIBFOO_SITE+ provides the location of the package, which can be a
URL or a local filesystem path. HTTP, FTP and SCP are supported URL
@@ -251,9 +251,6 @@ information is (assuming the package name is +libfoo+) :
use the same string to make the manifest file uniform.
Otherwise, describe the license in a precise and concise way, avoiding
ambiguous names such as +BSD+ which actually name a family of licenses.
- If the root filesystem you generate contains non-opensource packages, you
- can define their license as +PROPRIETARY+: Buildroot will not save any
- licensing info or source code for this package.
This variable is optional. If it is not defined, +unknown+ will appear in
the +license+ field of the manifest file for this package.
@@ -265,6 +262,11 @@ information is (assuming the package name is +libfoo+) :
to let you know, and +not saved+ will appear in the +license files+ field
of the manifest file for this package.
+* +LIBFOO_REDISTRIBUTE+ can be set to +YES+ (default) or +NO+ to indicate if
+ the package source code is allowed to be redistributed. Set it to +NO+ for
+ non-opensource packages: Buildroot will not save the source code for this
+ package when collecting the +legal-info+.
+
The recommended way to define these variables is to use the following
syntax:
@@ -292,10 +294,9 @@ different steps of the build process.
performed to install the package to the target directory, when the
package is a target package. The package must install its files to
the directory given by +$(TARGET_DIR)+. Only the files required for
- 'documentation' and 'execution' of the package should be
- installed. Header files should not be installed, they will be copied
- to the target, if the +development files in target filesystem+
- option is selected.
+ 'execution' of the package have to be
+ installed. Header files, static libraries and documentation will be
+ removed again when the target filesystem is finalized.
* +LIBFOO_INSTALL_STAGING_CMDS+ lists the actions to be
performed to install the package to the staging directory, when the
diff --git a/docs/manual/adding-packages-gettext.txt b/docs/manual/adding-packages-gettext.txt
index e9446d2..58fd98d 100644
--- a/docs/manual/adding-packages-gettext.txt
+++ b/docs/manual/adding-packages-gettext.txt
@@ -27,16 +27,20 @@ Therefore, Buildroot defines two configuration options:
doesn't provide its own gettext implementation and if locale support
is enabled
-Therefore, packages that unconditionally need gettext should:
+Packages that need gettext only when locale support is enabled should:
-* Use +select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT+
+* use +select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE+ in the
+ +Config.in+ file;
-* Use +$(if $(BR2_NEEDS_GETTEXT),gettext)+ in the package
- +DEPENDENCIES+ variable
+* use +$(if $(BR2_NEEDS_GETTEXT_IF_LOCALE),gettext)+ in the package
+ +DEPENDENCIES+ variable in the +.mk+ file.
-Packages that need gettext only when locale support is enabled should:
+Packages that unconditionally need gettext (which should be very rare)
+should:
+
+* use +select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT+ in the +Config.in+
+ file;
-* Use +select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE+
+* use +$(if $(BR2_NEEDS_GETTEXT),gettext)+ in the package
+ +DEPENDENCIES+ variable in the +.mk+ file.
-* Use +$(if $(BR2_NEEDS_GETTEXT_IF_LOCALE),gettext)+ in the package
- +DEPENDENCIES+ variable
diff --git a/docs/manual/adding-packages-tips.txt b/docs/manual/adding-packages-tips.txt
index 5e327d2..acdee40 100644
--- a/docs/manual/adding-packages-tips.txt
+++ b/docs/manual/adding-packages-tips.txt
@@ -19,7 +19,10 @@ In Buildroot, there is some relationship between:
It is mandatory to maintain consistency between these elements,
using the following rules:
-* the _make_ target name will be the _package name_ itself (e.g.:
+* the package directory and the +*.mk+ name are the _package name_
+ itself (e.g.: +package/foo-bar_boo/foo-bar_boo.mk+);
+
+* the _make_ target name is the _package name_ itself (e.g.:
+foo-bar_boo+);
* the config entry is the upper case _package name_ with `.` and `-`
@@ -35,15 +38,9 @@ using the following rules:
How to add a package from github
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-If the package has no release version, or its version cannot be
-identified using tag, then the sha1 of the particular commit should be
-used to identify the version (the first 7 characters of the sha1 are
-enough):
-
-------------------------
-FOO_VERSION = 1234567
-FOO_SITE = http://github.com/<user>/<package>/tarball/<branch>
-------------------------
+Packages on github often don't have a download area with release tarballs.
+However, it is possible to download tarballs directly from the repository
+on github.
If the package version matches a tag, then this tag should be used to
identify the version:
@@ -52,3 +49,16 @@ identify the version:
FOO_VERSION = v1.0
FOO_SITE = http://github.com/<user>/<package>/tarball/$(FOO_VERSION)
------------------------
+
+If the package has no release version, or its version cannot be
+identified using tag, then the SHA1 of the particular commit should be
+used to identify the version (the first 7 characters of the SHA1 are
+enough):
+
+------------------------
+FOO_VERSION = 1234567
+FOO_SITE = http://github.com/<user>/<package>/tarball/<branch>
+------------------------
+
+Note that the name of the tarball is the default +foo-1234567.tar.gz+
+so it is not necessary to specify it in the +.mk+ file.
diff --git a/docs/manual/beyond-buildroot.txt b/docs/manual/beyond-buildroot.txt
index e7b902d..a87b584 100644
--- a/docs/manual/beyond-buildroot.txt
+++ b/docs/manual/beyond-buildroot.txt
@@ -19,6 +19,8 @@ NFS-root directory:
sudo tar -xavf /path/to/output_dir/rootfs.tar -C /path/to/nfs_root_dir
-------------------
+Remember to add this path to +/etc/exports+.
+
Then, you can execute a NFS-boot from your target.
Chroot
diff --git a/docs/manual/board-support.txt b/docs/manual/board-support.txt
index 5a4da2c..44ab6eb 100644
--- a/docs/manual/board-support.txt
+++ b/docs/manual/board-support.txt
@@ -26,8 +26,8 @@ directory, and rename it +BOARDNAME_defconfig+.
It is recommended to use upstream versions of the Linux kernel and
bootloaders where possible, and also to use default kernel and bootloader
configurations if possible. If the defaults are incorrect for
-your platform, we encourage you to send fixes to the corresponding upstream
-projects.
+your board, or no default exists, we encourage you to send fixes to the
+corresponding upstream projects.
However, in the mean time, you may want to store kernel or bootloader
configuration or patches specific to your target platform. To do so,
diff --git a/docs/manual/customize-toolchain.txt b/docs/manual/customize-toolchain.txt
index 11f6f28..2b24412 100644
--- a/docs/manual/customize-toolchain.txt
+++ b/docs/manual/customize-toolchain.txt
@@ -37,8 +37,7 @@ Using the Crosstool-NG backend
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The http://crosstool-ng.org[crosstool-NG] toolchain backend enables a rather
-limited set of settings under the Buildroot +Toolchain+ menu (ie. when invoking
-+make menuconfig+); mostly:
+limited set of settings under the Buildroot +Toolchain+ menu:
* The http://crosstool-ng.org[crosstool-NG] configuration file
diff --git a/docs/manual/download-location.txt b/docs/manual/download-location.txt
index 13e675c..4befe0a 100644
--- a/docs/manual/download-location.txt
+++ b/docs/manual/download-location.txt
@@ -3,12 +3,12 @@
Location of downloaded packages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-It might be useful to know that the various tarballs that are
-downloaded by the Makefiles are all stored in +DL_DIR+ which by
-default is the +dl+ directory. This is useful, for example, if you want
+The various tarballs that are downloaded by Buildroot are all stored in
++DL_DIR+, which by default is the +dl+ directory. If you want
to keep a complete version of Buildroot which is known to be working
-with the associated tarballs. This will allow you to regenerate the
-toolchain and the target filesystem with exactly the same versions.
+with the associated tarballs, you can make a copy of this directory.
+This will allow you to regenerate the toolchain and the target filesystem
+with exactly the same versions.
If you maintain several Buildroot trees, it might be better to have a
shared download location. This can be accessed by creating a symbolic
@@ -26,3 +26,7 @@ should be added to +<~/.bashrc>+.
-----------------
$ export BUILDROOT_DL_DIR <shared download location>
-----------------
+
+The download location can also be set in the +.config+ file, with the
++BR2_DL_DIR+ option. This value is overridden by the +BUILDROOT_DL_DIR+
+environment variable.
diff --git a/docs/manual/embedded-basics.txt b/docs/manual/embedded-basics.txt
index a33338c..fdadf62 100644
--- a/docs/manual/embedded-basics.txt
+++ b/docs/manual/embedded-basics.txt
@@ -49,7 +49,9 @@ processor. Under most Linux systems, the compilation toolchain uses
the GNU libc (glibc) as the C standard library. This compilation
toolchain is called the "host compilation toolchain". The machine on
which it is running, and on which you're working, is called the "host
-system".
+system" footnote:[This terminology differs from what is used by GNU
+configure, where the host is the machine on which the application will
+run (which is usually the same as target)].
The compilation toolchain is provided by your distribution, and
Buildroot has nothing to do with it (other than using it to build a
diff --git a/docs/manual/faq-troubleshooting.txt b/docs/manual/faq-troubleshooting.txt
index fc75d66..5a22702 100644
--- a/docs/manual/faq-troubleshooting.txt
+++ b/docs/manual/faq-troubleshooting.txt
@@ -98,7 +98,7 @@ deal with expressing the dependencies of this package.
In the +Config.in+ file, dependencies may be expressed following two
semantics.
-See xref:depends-on-vs-select[].
+See xref:depends-on-vs-select[choosing between _depends_ and _select_].
[[faq-why-not-visible-package]]
Why are some packages not visible in the Buildroot config menu?
@@ -131,4 +131,8 @@ one, among these:
* device nodes are not created in the target directory.
For these reasons, commands run through chroot, using the target
-directory as the new root, would fail.
+directory as the new root, will most likely fail.
+
+If you want to run the target filesystem inside a chroot, or as an NFS
+root, then use the tarball image generated in +images/+ and extract it
+as root.
diff --git a/docs/manual/how-buildroot-works.txt b/docs/manual/how-buildroot-works.txt
index 7e33d8e..ec08f95 100644
--- a/docs/manual/how-buildroot-works.txt
+++ b/docs/manual/how-buildroot-works.txt
@@ -10,25 +10,34 @@ involved in the cross-compilation toolchain (+gcc+, +binutils+ and
+uClibc+).
There is basically one Makefile per software package, and they are
-named with the +.mk+ extension. Makefiles are split into three main
-sections:
+named with the +.mk+ extension. Makefiles are split into many different
+parts.
-* *toolchain* (in the +toolchain/+ directory) contains the Makefiles
+* The +toolchain/+ directory contains the Makefiles
and associated files for all software related to the
cross-compilation toolchain: +binutils+, +gcc+, +gdb+,
+kernel-headers+ and +uClibc+.
-* *package* (in the +package/+ directory) contains the Makefiles and
- associated files for all user-space tools that Buildroot can compile
- and add to the target root filesystem. There is one sub-directory
- per tool.
+* The +arch/+ directory contains the definitions for all the processor
+ architectures that are supported by Buildroot.
-* *target* (in the +target+ directory) contains the Makefiles and
+* The +package/+ directory contains the Makefiles and
+ associated files for all user-space tools and libraries that Buildroot
+ can compile and add to the target root filesystem. There is one
+ sub-directory per package.
+
+* The +linux/+ directory contains the Makefiles and associated files for
+ the Linux kernel.
+
+* The +boot/+ directory contains the Makefiles and associated files for
+ the bootloaders supported by Buildroot.
+
+* The +system/+ directory contains support for system integration, e.g.
+ the target filesystem skeleton and the selection of an init system.
+
+* The +fs/+ directory contains the Makefiles and
associated files for software related to the generation of the
- target root filesystem image. Four types of filesystems are
- supported: ext2, jffs2, cramfs and squashfs. For each of them there
- is a sub-directory with the required files. There is also a
- +default/+ directory that contains the target filesystem skeleton.
+ target root filesystem image.
Each directory contains at least 2 files:
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index 989b285..0f30234 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -73,52 +73,51 @@ License abbreviations
Here is a list of the licenses that are most widely used by packages in
Buildroot, with the name used in the manifest file:
-* +GPLv2+:
+* `GPLv2`:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
GNU General Public License, version 2];
-* +GPLv2++:
+* `GPLv2+`:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
GNU General Public License, version 2]
or (at your option) any later version;
-* +GPLv3+:
+* `GPLv3`:
http://www.gnu.org/licenses/gpl.html[
GNU General Public License, version 3];
-* +GPLv3++:
+* `GPLv3+`:
http://www.gnu.org/licenses/gpl.html[
GNU General Public License, version 3]
or (at your option) any later version;
-* +GPL+:
+* `GPL`:
http://www.gnu.org/licenses/gpl.html[
GNU General Public License] (any version);
-* +LGPLv2+:
+* `LGPLv2`:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
GNU Library General Public License, version 2];
-* +LGPLv2++:
+* `LGPLv2+`:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
GNU Library General Public License, version 2.1]
or (at your option) any later version;
-* +LGPLv2.1+:
+* `LGPLv2.1`:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
GNU Lesser General Public License, version 2.1];
-* +LGPLv2.1++:
+* `LGPLv2.1+`:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
GNU Lesser General Public License, version 2.1]
or (at your option) any later version;
-* +LGPLv3+:
+* `LGPLv3`:
http://www.gnu.org/licenses/lgpl.html[
GNU Lesser General Public License, version 3];
-* +LGPLv3++:
+* `LGPLv3+`:
http://www.gnu.org/licenses/lgpl.html[
GNU Lesser General Public License, version 3]
or (at your option) any later version;
-* +LGPL+:
+* `LGPL`:
http://www.gnu.org/licenses/lgpl.html[
GNU Lesser General Public License] (any version);
-* +BSD-4c+: Original BSD 4-clause license;
-* +BSD-3c+: BSD 3-clause license;
-* +BSD-2c+: BSD 2-clause license;
-* +PROPRIETARY+: marks a non-opensource package;
- Buildroot does not save any licensing info or source code for these packages.
+* `BSD-4c`: Original BSD 4-clause license;
+* `BSD-3c`: BSD 3-clause license;
+* `BSD-2c`: BSD 2-clause license;
+* `MIT`: MIT-style license.
Complying with the Buildroot license
------------------------------------
diff --git a/docs/manual/makedev-syntax.txt b/docs/manual/makedev-syntax.txt
index fc57105..27517b3 100644
--- a/docs/manual/makedev-syntax.txt
+++ b/docs/manual/makedev-syntax.txt
@@ -27,7 +27,8 @@ There are a few non-trivial blocks here:
* b: a block device file
* p: a named pipe
- +mode+, +uid+ and +gid+ are the usual permissions settings
-- +major+ and +minor+ are here for device files
+- +major+ and +minor+ are here for device files - set to - for other
+ files
- +start+, +inc+ and +count+ are for when you want to create a batch
of files, and can be reduced to a loop, beginning at +start+,
incrementing its counter by +inc+ until it reaches +count+
diff --git a/docs/manual/package-make-target.txt b/docs/manual/package-make-target.txt
index e8d5f53..7374957 100644
--- a/docs/manual/package-make-target.txt
+++ b/docs/manual/package-make-target.txt
@@ -2,20 +2,13 @@
[[pkg-build-steps]]
-Package make targets
-~~~~~~~~~~~~~~~~~~~~
+Package-specific _make_ targets
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-A +make <package>+ call achieves several _make targets_ with, as a
-result, this particular package and its dependencies built, installed
-in their destination directory (target, staging or host directory).
+Running +make <package>+ builds and installs that particular package
+and its dependencies.
-For packages based on the Buildroot infrastructures (+generic-package+,
-+autotools-package+ or +cmake-package+), each of those
-actions/steps/commands. For packages relying on other build system,
-then there is no other choice than looking at the +.mk+ file (see also
-the xref:rebuild-pkg[]).
-
-For packages relying on the Buildroot infrastructures, there are
+For packages relying on the Buildroot infrastructure, there are
numerous special make targets that can be called independently like
this:
@@ -23,7 +16,7 @@ this:
make <package>-<target>
------------
-In order, the package build commands are:
+The package build targets are (in the order they are executed):
[width="90%",cols="^1,4",options="header"]
|===================================================
@@ -38,27 +31,22 @@ build the package
| +extract+ | Put the source in the package build directory
(extract the tarball, copy the source, etc)
-| +patch+ | Apply the patches if any
+| +patch+ | Apply the patches, if any
-| +configure+ | Run the configure command
+| +configure+ | Run the configure commands, if any
-| +build+ | Compile the source
+| +build+ | Run the compilation commands
| +install-staging+ |
*target package:* Run the installation of the package in the
-staging directory
-
-*host package:* Does nothing
+staging directory, if necessary
| +install-target+ |
*target package:* Run the installation of the package in the
-staging directory
-
-*host package:* Does nothing
+target directory, if necessary
| +install+ |
-*target package:* Run the 2 previous installation commands for the
-target packages
+*target package:* Run the 2 previous installation commands
*host package:* Run the installation of the package in the host
directory
@@ -74,15 +62,18 @@ Additionally, there are some other useful make targets:
| +show-depends+ | Displays the dependencies required to build the
package
-| +clean+ | Clean the package build directory, also
-uninstall the package from both the target and the staging directory
+| +clean+ | Run the clean command of the package, also
+uninstall the package from both the target and the staging directory; _note
+that this is not implemented for all packages_
| +dirclean+ | Remove the whole package build directory
-| +rebuild+ | Rebuild only necessary binaries and install them
-again
+| +rebuild+ | Re-run the compilation commands - this only makes
+sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a file
+directly in the build directory
-| +reconfigure+ | Re-run the configure command, then rebuild
-only necessary binaries, and lastly install them again
+| +reconfigure+ | Re-run the configure commands, then rebuild - this only
+makes sense when using the +OVERRIDE_SRCDIR+ feature or when you modified a
+file directly in the build directory
|===================================================
diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt
index b65855e..9bc6537 100644
--- a/docs/manual/patch-policy.txt
+++ b/docs/manual/patch-policy.txt
@@ -2,8 +2,8 @@
[[patch-policy]]
-Patch Policy
-------------
+Patching a package
+------------------
While integrating a new package or updating an existing one, it may be
necessary to patch the source of the software to get it cross-built within
@@ -16,15 +16,15 @@ and patches supplied within buildroot.
Providing patches
~~~~~~~~~~~~~~~~~
-Additional tarball
-^^^^^^^^^^^^^^^^^^
+Downloaded
+^^^^^^^^^^
-If it is necessary to apply a patch set available as a downloadable
-tarball, then add the patch tarball to the +<packagename>_PATCH+
-variable.
+If it is necessary to apply a patch that is available for download, then it
+to the +<packagename>_PATCH+ variable. It is downloaded from the same site
+as the package itself. It can be a single patch, or a tarball containing a
+patch series.
-Note that the patch tarballs are downloaded from the same site as the
-sources.
+This method is typically used for packages from Debian.
Within Buildroot
^^^^^^^^^^^^^^^^
@@ -72,14 +72,15 @@ modified.
A message explaining what the patch does, and why it is needed, should
be added in the header commentary of the patch.
-You should add a +signed-off-by+ statement in the header of the each
-patch to help with keeping track of the changes.
+You should add a +Signed-off-by+ statement in the header of the each
+patch to help with keeping track of the changes and to certify that the
+patch is released under the same license as the software that is modified.
If the software is under version control, it is recommended to use the
-SCM software to generate the patch set.
+upstream SCM software to generate the patch set.
Otherwise, concatenate the header with the output of the
-+diff -purN source.c.orig source.c+ command.
++diff -purN package-version.orig/ package-version/+ command.
At the end, the patch should look like:
diff --git a/docs/manual/prerequisite.txt b/docs/manual/prerequisite.txt
index 38f9a94..17660b7 100644
--- a/docs/manual/prerequisite.txt
+++ b/docs/manual/prerequisite.txt
@@ -47,9 +47,6 @@ Mandatory packages
* Source fetching tools:
** +wget+
-* Configuration interface dependencies (requires development libraries):
-** +ncurses5+
-
[[requirement-optional]]
Optional packages
@@ -73,6 +70,7 @@ development context (further details: refer to xref:download-infra[]).
** +subversion+
* Configuration interface dependencies (requires development libraries):
+** +ncurses5+ to use the 'menuconfig' interface
** +qt4+ to use the 'xconfig' interface
** +glib2+, +gtk2+ and +glade2+ to use the 'gconfig' interface
diff --git a/docs/manual/rebuilding-packages.txt b/docs/manual/rebuilding-packages.txt
index e677590..d6a77a7 100644
--- a/docs/manual/rebuilding-packages.txt
+++ b/docs/manual/rebuilding-packages.txt
@@ -41,49 +41,37 @@ One of the most common questions asked by Buildroot users is how to
rebuild a given package or how to remove a package without rebuilding
everything from scratch.
-Removing a package is currently unsupported by Buildroot without
+Removing a package is unsupported by Buildroot without
rebuilding from scratch. This is because Buildroot doesn't keep track
of which package installs what files in the +output/staging+ and
-+output/target+ directories. However, implementing clean package
-removal is on the TODO-list of Buildroot developers.
++output/target+ directories, or which package would be compiled differently
+depending on the availability of another package.
The easiest way to rebuild a single package from scratch is to remove
its build directory in +output/build+. Buildroot will then re-extract,
-re-configure, re-compile and re-install this package from scratch.
+re-configure, re-compile and re-install this package from scratch. You
+can ask buildroot to do this with the +make <package>-dirclean+ command.
-For convenience, most packages support the special make targets
-<package>-reconfigure and <package>-rebuild to repeat the configure
-and build steps.
+For convenience, the special make targets
+<package>-reconfigure and <package>-rebuild repeat the configure
+resp. build steps.
However, if you don't want to rebuild the package completely from
scratch, a better understanding of the Buildroot internals is
needed. Internally, to keep track of which steps have been done and
which steps remain to be done, Buildroot maintains stamp files (empty
-files that just tell whether this or that action has been done). The
-problem is that these stamp files are not uniformly named and handled
-by the different packages, so some understanding of the particular
-package is needed.
+files that just tell whether this or that action has been done):
-For packages relying on Buildroot packages infrastructures (see
-xref:adding-packages[this section] for details), the following stamp
-files are relevant:
-
-* +output/build/packagename-version/.stamp_configured+. If removed,
+* +output/build/<package>-<version>/.stamp_configured+. If removed,
Buildroot will trigger the recompilation of the package from the
configuration step (execution of +./configure+).
-* +output/build/packagename-version/.stamp_built+. If removed,
+* +output/build/<package>-<version>/.stamp_built+. If removed,
Buildroot will trigger the recompilation of the package from the
compilation step (execution of +make+).
-.Notes
-- Since the _Buildroot-2012.11_ release, all packages rely on the
-Buildroot infrastructures.
-- Only toolchain packages remain using custom makefiles (i.e. do not
-use any Buildroot infrastructure).
-- Most, if not all, packages and toolchain packages will progressively
-be ported over to the generic, autotools or CMake infrastructure,
-making it much easier to rebuild individual packages.
+Note: toolchain packages use custom makefiles. Their stamp files are named
+differently.
-Further details about package special make target at the
+Further details about package special make targets are explained in
xref:pkg-build-steps[].
diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index 9436981..6e144d0 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -93,8 +93,8 @@ This directory contains several subdirectories:
use the tarball image generated in +images/+ and extract it as
root. Compared to +staging/+, +target/+ contains only the files and
libraries needed to run the selected target applications: the
- development files (headers, etc.) are not present, unless the
- +development files in target filesystem+ option is selected.
+ development files (headers, etc.) are not present, the binaries are
+ stripped.
* +host/+ contains the installation of tools compiled for the host
that are needed for the proper execution of Buildroot, including the
diff --git a/docs/manual/writing-rules.txt b/docs/manual/writing-rules.txt
index 2a61639..f6382b5 100644
--- a/docs/manual/writing-rules.txt
+++ b/docs/manual/writing-rules.txt
@@ -1,16 +1,18 @@
// -*- mode:doc; -*-
-Writing rules
--------------
+Coding style
+------------
-Overall, these writing rules are here to help you add new files in
+Overall, these coding style rules are here to help you to add new files in
Buildroot or refactor existing ones.
If you slightly modify some existing file, the important thing is
-keeping the consistency of the whole file, so you can:
-* either follow the potentially deprecated rules used all over this
-file
-* or entirely rework it in order to make it comply with those rules.
+to keep the consistency of the whole file, so you can:
+
+* either follow the potentially deprecated coding style used in this
+file,
+
+* or entirely rework it in order to make it comply with these rules.
[[writing-rules-config-in]]
@@ -39,9 +41,9 @@ config BR2_PACKAGE_LIBFOO
* The help text itself should be indented with one tab and two
spaces.
-The configuration system used in Buildroot, so the content of the
-+Config.in+ files, is regular _Kconfig_. Further details about
-_Kconfig_: refer to
+The +Config.in+ files are the input for the configuration tool
+used in Buildroot, which is the regular _Kconfig_. For further
+details about the _Kconfig_ language, refer to
http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[].
[[writing-rules-mk]]
@@ -55,15 +57,26 @@ The +.mk+ file
LIBFOO_VERSION = 1.0
LIBFOO_CONF_OPT += --without-python-support
---------------------
++
+It is also possible to align the +=+ signs:
++
+---------------------
+LIBFOO_VERSION = 1.0
+LIBFOO_SOURCE = foo-$(LIBFOO_VERSION).tar.gz
+LIBFOO_CONF_OPT += --without-python-support
+---------------------
* Indentation: use tab only:
+
---------------------
define LIBFOO_REMOVE_DOC
-$(RM) -fr $(TARGET_DIR)/usr/share/libfoo/doc \
- $(TARGET_DIR)/usr/share/man/man3/libfoo*
+ $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/doc \
+ $(TARGET_DIR)/usr/share/man/man3/libfoo*
endef
---------------------
++
+Note that commands inside a +define+ block should always start with a tab,
+so _make_ recognizes them as commands.
* Optional dependency:
^ permalink raw reply related
* [Buildroot] [git commit] manual: trivial fixes
From: Peter Korsgaard @ 2012-11-28 1:07 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=1d989fafba761d29b3b2960bf388821d3ac0f6e7
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
docs/manual/adding-packages-autotools.txt | 4 +-
docs/manual/adding-packages-cmake.txt | 4 +-
docs/manual/adding-packages-conclusion.txt | 2 +-
docs/manual/adding-packages-directory.txt | 2 +-
docs/manual/adding-packages-generic.txt | 34 +++++++++---------
docs/manual/adding-packages-tips.txt | 4 +-
docs/manual/board-support.txt | 2 +-
docs/manual/common-usage.txt | 8 ++--
docs/manual/customize-rootfs.txt | 8 ++--
docs/manual/customize-toolchain.txt | 10 +++---
docs/manual/customize-uclibc-config.txt | 11 +++---
docs/manual/embedded-basics.txt | 2 +-
docs/manual/external-toolchain.txt | 9 +++--
docs/manual/how-buildroot-works.txt | 2 +-
docs/manual/introduction.txt | 4 +-
docs/manual/legal-notice.txt | 27 ++++++++++----
docs/manual/make-tips.txt | 50 +++++++++++++++------------
docs/manual/makedev-syntax.txt | 2 +-
docs/manual/patch-policy.txt | 9 +++--
docs/manual/prerequisite.txt | 2 +-
docs/manual/rebuilding-packages.txt | 4 +-
docs/manual/using.txt | 22 ++++++------
docs/manual/writing-rules.txt | 4 +-
23 files changed, 122 insertions(+), 104 deletions(-)
diff --git a/docs/manual/adding-packages-autotools.txt b/docs/manual/adding-packages-autotools.txt
index 1184b69..4127df4 100644
--- a/docs/manual/adding-packages-autotools.txt
+++ b/docs/manual/adding-packages-autotools.txt
@@ -133,13 +133,13 @@ cases, typical packages will therefore only use a few of them.
* +LIBFOO_INSTALL_STAGING_OPT+ contains the make options
used to install the package to the staging directory. By default, the
- value is +DESTDIR=$$(STAGING_DIR) install+, which is
+ value is +DESTDIR=$(STAGING_DIR) install+, which is
correct for most autotools packages. It is still possible to override
it.
* +LIBFOO_INSTALL_TARGET_OPT+ contains the make options
used to install the package to the target directory. By default, the
- value is +DESTDIR=$$(TARGET_DIR) install+. The default
+ value is +DESTDIR=$(TARGET_DIR) install+. The default
value is correct for most autotools packages, but it is still possible
to override it if needed.
diff --git a/docs/manual/adding-packages-cmake.txt b/docs/manual/adding-packages-cmake.txt
index 81ac0a7..4a9e893 100644
--- a/docs/manual/adding-packages-cmake.txt
+++ b/docs/manual/adding-packages-cmake.txt
@@ -115,12 +115,12 @@ typical packages will therefore only use a few of them.
* +LIBFOO_INSTALL_STAGING_OPT+ contains the make options used to
install the package to the staging directory. By default, the value
- is +DESTDIR=$$(STAGING_DIR) install+, which is correct for most
+ is +DESTDIR=$(STAGING_DIR) install+, which is correct for most
CMake packages. It is still possible to override it.
* +LIBFOO_INSTALL_TARGET_OPT+ contains the make options used to
install the package to the target directory. By default, the value
- is +DESTDIR=$$(TARGET_DIR) install+. The default value is correct
+ is +DESTDIR=$(TARGET_DIR) install+. The default value is correct
for most CMake packages, but it is still possible to override it if
needed.
diff --git a/docs/manual/adding-packages-conclusion.txt b/docs/manual/adding-packages-conclusion.txt
index 42f1c8f..137b7c3 100644
--- a/docs/manual/adding-packages-conclusion.txt
+++ b/docs/manual/adding-packages-conclusion.txt
@@ -8,5 +8,5 @@ matter of writing a Makefile using an existing example and modifying it
according to the compilation process required by the package.
If you package software that might be useful for other people, don't
-forget to send a patch to Buildroot developers!
+forget to send a patch to the Buildroot mailing list!
diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
index c8f41ff..88a4645 100644
--- a/docs/manual/adding-packages-directory.txt
+++ b/docs/manual/adding-packages-directory.txt
@@ -7,7 +7,7 @@ First of all, create a directory under the +package+ directory for
your software, for example +libfoo+.
Some packages have been grouped by topic in a sub-directory:
-+multimedia+, +java+, +x11r7+, and +games+. If your package fits in
++multimedia+, +x11r7+, +efl+ and +matchbox+. If your package fits in
one of these categories, then create your package directory in these.
diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
index b05043a..ee96bc1 100644
--- a/docs/manual/adding-packages-generic.txt
+++ b/docs/manual/adding-packages-generic.txt
@@ -175,8 +175,8 @@ information is (assuming the package name is +libfoo+) :
Examples: +
+LIBFOO_SITE=http://www.libfoosoftware.org/libfoo+ +
+LIBFOO_SITE=http://svn.xiph.org/trunk/Tremor/+ +
- +LIBFOO_SITE=git://github.com/kergoth/tslib.git+
- +LIBFOO_SITE=/opt/software/libfoo.tar.gz+
+ +LIBFOO_SITE=git://github.com/kergoth/tslib.git+ +
+ +LIBFOO_SITE=/opt/software/libfoo.tar.gz+ +
+LIBFOO_SITE=$(TOPDIR)/../src/libfoo/+
* +LIBFOO_SITE_METHOD+ determines the method used to fetch or copy the
@@ -221,7 +221,7 @@ information is (assuming the package name is +libfoo+) :
name) that are required for the current target package to
compile. These dependencies are guaranteed to be compiled and
installed before the configuration of the current package starts. In
- a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependency for
+ a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for
the current host package.
* +LIBFOO_INSTALL_STAGING+ can be set to +YES+ or +NO+ (default). If
@@ -275,20 +275,20 @@ LIBFOO_VERSION = 2.32
Now, the variables that define what should be performed at the
different steps of the build process.
-* +LIBFOO_CONFIGURE_CMDS+, used to list the actions to be performed to
- configure the package before its compilation
+* +LIBFOO_CONFIGURE_CMDS+ lists the actions to be performed to
+ configure the package before its compilation.
-* +LIBFOO_BUILD_CMDS+, used to list the actions to be performed to
- compile the package
+* +LIBFOO_BUILD_CMDS+ lists the actions to be performed to
+ compile the package.
-* +HOST_LIBFOO_INSTALL_CMDS+, used to list the actions to be performed
+* +HOST_LIBFOO_INSTALL_CMDS+ lists the actions to be performed
to install the package, when the package is a host package. The
package must install its files to the directory given by
+$(HOST_DIR)+. All files, including development files such as
headers should be installed, since other packages might be compiled
on top of this package.
-* +LIBFOO_INSTALL_TARGET_CMDS+, used to list the actions to be
+* +LIBFOO_INSTALL_TARGET_CMDS+ lists the actions to be
performed to install the package to the target directory, when the
package is a target package. The package must install its files to
the directory given by +$(TARGET_DIR)+. Only the files required for
@@ -297,24 +297,24 @@ different steps of the build process.
to the target, if the +development files in target filesystem+
option is selected.
-* +LIBFOO_INSTALL_STAGING_CMDS+, used to list the actions to be
+* +LIBFOO_INSTALL_STAGING_CMDS+ lists the actions to be
performed to install the package to the staging directory, when the
package is a target package. The package must install its files to
the directory given by +$(STAGING_DIR)+. All development files
should be installed, since they might be needed to compile other
packages.
-* +LIBFOO_CLEAN_CMDS+, used to list the actions to perform to clean up
+* +LIBFOO_CLEAN_CMDS+, lists the actions to perform to clean up
the build directory of the package.
-* +LIBFOO_UNINSTALL_TARGET_CMDS+, used to list the actions to
+* +LIBFOO_UNINSTALL_TARGET_CMDS+ lists the actions to
uninstall the package from the target directory +$(TARGET_DIR)+
-* +LIBFOO_UNINSTALL_STAGING_CMDS+, used to list the actions to
+* +LIBFOO_UNINSTALL_STAGING_CMDS+ lists the actions to
uninstall the package from the staging directory +$(STAGING_DIR)+.
-* +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+, used
- to install init scripts either for the systemV-like init systems
+* +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+ list the
+ actions to install init scripts either for the systemV-like init systems
(busybox, sysvinit, etc.) or for the systemd units. These commands
will be run only when the relevant init system is installed (i.e. if
systemd is selected as the init system in the configuration, only
@@ -352,8 +352,8 @@ using the autotools infrastructure described below. However, since
they are provided by the generic infrastructure, they are documented
here. The exception is +LIBFOO_POST_PATCH_HOOKS+. Patching the
package and producing legal info are not user definable, so
-+LIBFOO_POST_PATCH_HOOKS+ and +LIBFOO_POST_LEGAL_INFO_HOOKS+ will be
-userful for generic packages.
++LIBFOO_POST_PATCH_HOOKS+ and +LIBFOO_POST_LEGAL_INFO_HOOKS+ are
+useful for generic packages.
The following hook points are available:
diff --git a/docs/manual/adding-packages-tips.txt b/docs/manual/adding-packages-tips.txt
index 6ec632d..5e327d2 100644
--- a/docs/manual/adding-packages-tips.txt
+++ b/docs/manual/adding-packages-tips.txt
@@ -32,8 +32,8 @@ using the following rules:
[[github-download-url]]
-How to add package from github
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+How to add a package from github
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If the package has no release version, or its version cannot be
identified using tag, then the sha1 of the particular commit should be
diff --git a/docs/manual/board-support.txt b/docs/manual/board-support.txt
index 271f3e0..5a4da2c 100644
--- a/docs/manual/board-support.txt
+++ b/docs/manual/board-support.txt
@@ -21,7 +21,7 @@ selections are highly application-specific.
Once you have a known working configuration, run +make
savedefconfig+. This will generate a minimal +defconfig+ file at the
root of the Buildroot source tree. Move this file into the +configs/+
-directory, and rename it +MYBOARD_defconfig+.
+directory, and rename it +BOARDNAME_defconfig+.
It is recommended to use upstream versions of the Linux kernel and
bootloaders where possible, and also to use default kernel and bootloader
diff --git a/docs/manual/common-usage.txt b/docs/manual/common-usage.txt
index 98503b5..5566a39 100644
--- a/docs/manual/common-usage.txt
+++ b/docs/manual/common-usage.txt
@@ -47,7 +47,7 @@ safely run multiple builds in parallel using the same source tree as
long as they use unique output directories.
For ease of use, Buildroot generates a Makefile wrapper in the output
-directory - So after the first run, you no longer need to pass +O=..+
+directory - so after the first run, you no longer need to pass +O=..+
and +-C ..+, simply run (in the output directory):
--------------------
@@ -69,21 +69,21 @@ to +make+ or set in the environment:
internal toolchain is being built.
+
Note that the uClibc configuration file can also be set from the
- configuration interface, so through the Buildroot .config file; this
+ configuration interface, so through the Buildroot +.config+ file; this
is the recommended way of setting it.
+
* +BUSYBOX_CONFIG_FILE=<path/to/.config>+, path to
the Busybox configuration file.
+
Note that the Busybox configuration file can also be set from the
- configuration interface, so through the Buildroot .config file; this
+ configuration interface, so through the Buildroot +.config+ file; this
is the recommended way of setting it.
+
* +BUILDROOT_DL_DIR+ to override the directory in which
Buildroot stores/retrieves downloaded files
+
Note that the Buildroot download directory can also be set from the
- configuration interface, so through the Buildroot .config file; this
+ configuration interface, so through the Buildroot +.config+ file; this
is the recommended way of setting it.
An example that uses config files located in the toplevel directory and
diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt
index d6224ff..a1a556b 100644
--- a/docs/manual/customize-rootfs.txt
+++ b/docs/manual/customize-rootfs.txt
@@ -5,7 +5,7 @@ Customizing the generated target filesystem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Besides changing one or another configuration through +make *config+,
-there are a few ways to customize the resulting target filesystem:
+there are a few ways to customize the resulting target filesystem.
* Customize the target filesystem directly and rebuild the image. The
target filesystem is available under +output/target/+. You can
@@ -13,7 +13,7 @@ there are a few ways to customize the resulting target filesystem:
rebuild the target filesystem image. This method allows you to do
anything to the target filesystem, but if you decide to completely
rebuild your toolchain and tools, these changes will be lost.
- _Changes are not resistent to the +make clean+ command_.
+ _Changes do not survive the +make clean+ command_.
* Create your own 'target skeleton'. You can start with the default
skeleton available under +system/skeleton+ and then customize it to
@@ -30,13 +30,13 @@ there are a few ways to customize the resulting target filesystem:
assembled. The +BR2_ROOTFS_POST_BUILD_SCRIPT+ will allow you to
specify the location of your post-build script. This option can be
found in the +System configuration+ menu. The destination root
- filesystem folder *is given as the first argument to this script,
+ filesystem folder is given as the first argument to this script,
and this script can then be used to copy programs, static data or
any other needed file to your target filesystem. You should,
however, use this feature with care. Whenever you find that a
certain package generates wrong or unneeded files, you should fix
that package rather than work around it with a post-build cleanup
- script. _Among these first 3 methods, this one should be prefere_d.
+ script. _Among these first 3 methods, this one should be preferred_.
* A special package, 'customize', stored in +package/customize+ can be
used. You can put all the files that you want to see in the final
diff --git a/docs/manual/customize-toolchain.txt b/docs/manual/customize-toolchain.txt
index 91657cf..11f6f28 100644
--- a/docs/manual/customize-toolchain.txt
+++ b/docs/manual/customize-toolchain.txt
@@ -24,13 +24,13 @@ The internal Buildroot toolchain backend *only* allows to generate
However, it allows to tune major settings, such as:
-* Linux header version
+* Linux headers version;
-* http://www.uclibc.org/[uClibc] configuration (see xref:uclibc-custom[uClibc])
+* http://www.uclibc.org/[uClibc] configuration (see xref:uclibc-custom[uClibc]);
-* Binutils, GCC, Gdb and toolchain options
+* Binutils, GCC, Gdb and toolchain options.
-This is directly available after selecting the +Buildroot toolchain+ type in
+These settings are available after selecting the +Buildroot toolchain+ type in
the menu +Toolchain+.
Using the Crosstool-NG backend
@@ -44,4 +44,4 @@ limited set of settings under the Buildroot +Toolchain+ menu (ie. when invoking
* Gdb and some toolchain options
-Then, the toolchain can be finely tuned invoking +make ctng-menuconfig+.
+Then, the toolchain can be fine-tuned by invoking +make ctng-menuconfig+.
diff --git a/docs/manual/customize-uclibc-config.txt b/docs/manual/customize-uclibc-config.txt
index d340c9a..38a1575 100644
--- a/docs/manual/customize-uclibc-config.txt
+++ b/docs/manual/customize-uclibc-config.txt
@@ -18,17 +18,16 @@ follow these steps:
similar to the one used in the Linux kernel or Buildroot,
appears. Make your configuration changes as appropriate.
-* Copy the +$(O)/toolchain/uclibc-VERSION/.config+ file to a different
- place (like +toolchain/uClibc/uClibc-myconfig.config+, or
- +board/mymanufacturer/myboard/uClibc.config+) and adjust the uClibc
- configuration (configuration option +BR2_UCLIBC_CONFIG+) to use this
+* Copy the +$(O)/toolchain/uClibc-VERSION/.config+ file to a different
+ place (e.g. +board/MANUFACTURER/BOARDNAME/uClibc.config+) and adjust
+ the uClibc configuration file option +BR2_UCLIBC_CONFIG+ to refer to this
configuration instead of the default one.
* Run the compilation of Buildroot again.
-Otherwise, you can simply change +toolchain/uClibc/uClibc.config+,
+Otherwise, you can simply change +toolchain/uClibc/uClibc-VERSION.config+,
without running the configuration assistant.
-If you want to use an existing config file for uclibc, then see
+If you want to use an existing config file for uClibc, then see
xref:env-vars[].
diff --git a/docs/manual/embedded-basics.txt b/docs/manual/embedded-basics.txt
index d1ee88c..a33338c 100644
--- a/docs/manual/embedded-basics.txt
+++ b/docs/manual/embedded-basics.txt
@@ -82,7 +82,7 @@ interested in Buildroot for two reasons:
You might wonder why such a tool is needed when you can compile +gcc+,
+binutils+, +uClibc+ and all the other tools by hand. Of course doing
-so is possible but, dealing with all of the configure options and
+so is possible, but dealing with all of the configure options and
problems of every +gcc+ or +binutils+ version is very time-consuming
and uninteresting. Buildroot automates this process through the use
of Makefiles and has a collection of patches for each +gcc+ and
diff --git a/docs/manual/external-toolchain.txt b/docs/manual/external-toolchain.txt
index b337376..6124fe4 100644
--- a/docs/manual/external-toolchain.txt
+++ b/docs/manual/external-toolchain.txt
@@ -26,8 +26,8 @@ Then, you have three solutions to use an external toolchain:
* Use a predefined external toolchain profile, and let Buildroot
download, extract and install the toolchain. Buildroot already knows
- about a few CodeSourcery toolchains for ARM, PowerPC, MIPS and
- SuperH. Just select the toolchain profile in +Toolchain+ through the
+ about a few CodeSourcery, Linaro, Blackfin and Xilinx toolchains.
+ Just select the toolchain profile in +Toolchain+ from the
available ones. This is definitely the easiest solution.
* Use a predefined external toolchain profile, but instead of having
@@ -45,7 +45,8 @@ Then, you have three solutions to use an external toolchain:
toolchain C library+ options. Then, you have to tell Buildroot what
your external toolchain supports. If your external toolchain uses
the 'glibc' library, you only have to tell whether your toolchain
- supports C++ or not. If your external toolchain uses the 'uclibc'
+ supports C\+\+ or not and whether it has built-in RPC support. If
+ your external toolchain uses the 'uClibc'
library, then you have to tell Buildroot if it supports largefile,
IPv6, RPC, wide-char, locale, program invocation, threads and
C++. At the beginning of the execution, Buildroot will tell you if
@@ -53,7 +54,7 @@ Then, you have three solutions to use an external toolchain:
Our external toolchain support has been tested with toolchains from
-CodeSourcery, toolchains generated by
+CodeSourcery and Linaro, toolchains generated by
http://crosstool-ng.org[crosstool-NG], and toolchains generated by
Buildroot itself. In general, all toolchains that support the
'sysroot' feature should work. If not, do not hesitate to contact the
diff --git a/docs/manual/how-buildroot-works.txt b/docs/manual/how-buildroot-works.txt
index 879cff3..7e33d8e 100644
--- a/docs/manual/how-buildroot-works.txt
+++ b/docs/manual/how-buildroot-works.txt
@@ -6,7 +6,7 @@ How Buildroot works
As mentioned above, Buildroot is basically a set of Makefiles that
download, configure, and compile software with the correct options. It
also includes patches for various software packages - mainly the ones
-involved in the cross-compilation tool chain (+gcc+, +binutils+ and
+involved in the cross-compilation toolchain (+gcc+, +binutils+ and
+uClibc+).
There is basically one Makefile per software package, and they are
diff --git a/docs/manual/introduction.txt b/docs/manual/introduction.txt
index bcca544..9353f8c 100644
--- a/docs/manual/introduction.txt
+++ b/docs/manual/introduction.txt
@@ -17,5 +17,5 @@ processors, MIPS processors, ARM processors, etc.
Buildroot supports numerous processors and their variants; it also
comes with default configurations for several boards available
off-the-shelf. Besides this, a number of third-party projects are based on,
-or develop their BSP footnote:[BSP: Board Software Package] or
-SDK footnote:[SDK: Standard Development Kit] on top of Buildroot.
+or develop their BSP footnote:[BSP: Board Support Package] or
+SDK footnote:[SDK: Software Development Kit] on top of Buildroot.
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index a7af5a8..989b285 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -5,13 +5,13 @@
Legal notice and licensing
==========================
-Complying with opensource licenses
-----------------------------------
+Complying with open source licenses
+-----------------------------------
All of the end products of Buildroot (toolchain, root filesystem, kernel,
-bootloaders) contain opensource software, released under various licenses.
+bootloaders) contain open source software, released under various licenses.
-Using opensource software gives you the freedom to build rich embedded
+Using open source software gives you the freedom to build rich embedded
systems, choosing from a wide range of packages, but also imposes some
obligations that you must know and honour.
Some licenses require you to publish the license text in the documentation of
@@ -46,7 +46,7 @@ There you will find:
* A manifest file listing the configured packages, their version, license and
related information.
Some of this information might not be defined in Buildroot; such items are
- clearly marked as "unknown" or similar.
+ marked as "unknown".
* A +licenses/+ subdirectory, which contains the license text of packages.
If the license file(s) are not defined in Buildroot, the file is not produced
and a warning in the +README+ indicates this.
@@ -56,16 +56,20 @@ produce all the material that is somehow relevant for legal compliance with the
package licenses. Buildroot does not try to produce the exact material that
you must somehow make public. Certainly, more material is produced than is
needed for a strict legal compliance. For example, it produces the source code
-for packages released under BSD-like licenses, that you might not want to
+for packages released under BSD-like licenses, that you are not required to
redistribute in source form.
Moreover, due to technical limitations, Buildroot does not produce some
material that you will or may need, such as the toolchain source code and the
-Buildroot source code itself.
+Buildroot source code itself (including patches to packages for which source
+distribution is required).
When you run +make legal-info+, Buildroot produces warnings in the +README+
file to inform you of relevant material that could not be saved.
[[legal-info-list-licenses]]
+License abbreviations
+---------------------
+
Here is a list of the licenses that are most widely used by packages in
Buildroot, with the name used in the manifest file:
@@ -86,6 +90,13 @@ Buildroot, with the name used in the manifest file:
* +GPL+:
http://www.gnu.org/licenses/gpl.html[
GNU General Public License] (any version);
+* +LGPLv2+:
+ http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
+ GNU Library General Public License, version 2];
+* +LGPLv2++:
+ http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
+ GNU Library General Public License, version 2.1]
+ or (at your option) any later version;
* +LGPLv2.1+:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
GNU Lesser General Public License, version 2.1];
@@ -112,7 +123,7 @@ Buildroot, with the name used in the manifest file:
Complying with the Buildroot license
------------------------------------
-Buildroot itself is an opensource software, released under the
+Buildroot itself is an open source software, released under the
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public
License, version 2] or (at your option) any later version.
However, being a build system, it is not normally part of the end product:
diff --git a/docs/manual/make-tips.txt b/docs/manual/make-tips.txt
index 25c4e35..8cd77c0 100644
--- a/docs/manual/make-tips.txt
+++ b/docs/manual/make-tips.txt
@@ -4,55 +4,61 @@
'make' tips
-----------
-Because Buildroot is a set of Makefiles and patches, there are a few
-things that are useful to know, such as:
+This is a collection of tips that help you make the most of Buildroot.
-+make *config+ commands offer a search tool. Read the help message in
+.Configuration searches:
+
+The +make *config+ commands offer a search tool. Read the help message in
the different frontend menus to know how to use it:
-* in _menuconfig_, search tool is called by pressing +/+;
-* in _xconfig_, search tool is called by pressing +ctrl+ + +f+.
+* in _menuconfig_, the search tool is called by pressing +/+;
+* in _xconfig_, the search tool is called by pressing +Ctrl+ + +f+.
The result of the search shows the help message of the matching items.
-Display all commands executed by make:
+.Display all commands executed by make:
--------------------
- $ make V=0|1 <target>
+ $ make V=1 <target>
--------------------
-Display all available targets:
+.Display all available targets:
--------------------
$ make help
--------------------
-Note that some settings in the +.config+ file may hide some targets:
+.Not all targets are always available,
+
+some settings in the +.config+ file may hide some targets:
+
+* +linux-menuconfig+ and +linux-savedefconfig+ only work when
+ +linux+ is enabled;
+* +uclibc-menuconfig+ is only available when the
+ Buildroot internal toolchain backend is used;
+* +ctng-menuconfig+ is only available when the
+ crosstool-NG backend is used;
+* +barebox-menuconfig+ and +barebox-savedefconfig+ only work when the
+ +barebox+ bootloader is enabled.
+
+.Cleaning:
-* +busybox-menuconfig+ depends on whether +busybox+ is enabled or not
- in the +Package selection+ menu
-* +linux-menuconfig+ and +linux-savedefconfig+ depend on whether
- +linux+ is enabled or not
-* +uclibc-menuconfig+ depends on whether the toolchain uses the
- Buildroot internal toolchain backend or not
-* +ctng-menuconfig+ depends on whether the toolchain uses the
- crosstool-NG backend or not
-* +barebox-menuconfig+ and +barebox-savedefconfig+ depend on whether
- +barebox+ bootloader is enabled or not
+Explicit cleaning is required when any of the architecture or toolchain
+configuration options are changed.
-Delete all build products (including build directories, host, staging
+To delete all build products (including build directories, host, staging
and target trees, the images and the toolchain):
--------------------
$ make clean
--------------------
-Delete all build products as well as the configuration:
+To delete all build products as well as the configuration:
--------------------
$ make distclean
--------------------
-Note that if +ccache+ is enabled, running +make clean|distclean+ does
+Note that if +ccache+ is enabled, running +make clean+ or +distclean+ does
not empty the compiler cache used by Buildroot. To delete it, refer
to xref:ccache[].
diff --git a/docs/manual/makedev-syntax.txt b/docs/manual/makedev-syntax.txt
index 99ecdea..fc57105 100644
--- a/docs/manual/makedev-syntax.txt
+++ b/docs/manual/makedev-syntax.txt
@@ -20,7 +20,7 @@ It takes the form of a line for each file, with the following layout:
There are a few non-trivial blocks here:
- +name+ is the path to the file you want to create/modify
-- +type+ is the type of the file, being one of :
+- +type+ is the type of the file, being one of:
* f: a regular file
* d: a directory
* c: a character device file
diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt
index 1fdb04e..b65855e 100644
--- a/docs/manual/patch-policy.txt
+++ b/docs/manual/patch-policy.txt
@@ -6,11 +6,12 @@ Patch Policy
------------
While integrating a new package or updating an existing one, it may be
-necessary to patch the source of the software to get it built within
+necessary to patch the source of the software to get it cross-built within
Buildroot.
Buildroot offers an infrastructure to automatically handle this during
-the builds. It supports several ways of applying patch sets:
+the builds. It supports two ways of applying patch sets: downloaded patches
+and patches supplied within buildroot.
Providing patches
~~~~~~~~~~~~~~~~~
@@ -29,10 +30,10 @@ Within Buildroot
^^^^^^^^^^^^^^^^
Most patches are provided within Buildroot, in the package
-directory; these typically aim to fix cross-compilation, +libc+ support,
+directory; these typically aim to fix cross-compilation, libc support,
or other such issues.
-These patch files should have the extension +*.patch+.
+These patch files should be named +<packagename>-*.patch+.
A +series+ file, as used by +quilt+, may also be added in the
package directory. In that case, the +series+ file defines the patch
diff --git a/docs/manual/prerequisite.txt b/docs/manual/prerequisite.txt
index 36d8da7..38f9a94 100644
--- a/docs/manual/prerequisite.txt
+++ b/docs/manual/prerequisite.txt
@@ -23,7 +23,7 @@ Mandatory packages
** +which+
** +sed+
-** +make+ (version 3.82 or any later)
+** +make+ (version 3.81 or any later)
** +binutils+
** +build-essential+ (only for Debian based systems)
** +gcc+ (version 2.95 or any later)
diff --git a/docs/manual/rebuilding-packages.txt b/docs/manual/rebuilding-packages.txt
index 83f6a36..e677590 100644
--- a/docs/manual/rebuilding-packages.txt
+++ b/docs/manual/rebuilding-packages.txt
@@ -14,7 +14,7 @@ In some cases, a full rebuild is mandatory:
* each time the toolchain properties are changed, this includes:
-** after changing some toolchain option under the _Toolchain_ menu (if
+** after changing any toolchain option under the _Toolchain_ menu (if
the internal Buildroot backend is used);
** after running +make ctng-menuconfig+ (if the crosstool-NG backend
is used);
@@ -25,7 +25,7 @@ In some cases, a full rebuild is mandatory:
In some cases, a full rebuild is recommended:
* after adding some libraries to the package selection (otherwise,
- some packages that can be optionally linked against those libraries
+ packages that can be optionally linked against those libraries
won't be rebuilt, so they won't support those new available
features).
diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index 892caf5..9436981 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -31,9 +31,9 @@ to run the Qt or GTK-based configurators.
All of these "make" commands will need to build a configuration
utility (including the interface), so you may need to install
"development" packages for relevant libraries used by the
-configuration utilities. Check the xref:requirement[] to know what
-Buildroot needs, and specifically the xref:requirement-optional[system requirements]
-to get the dependencies of favorite interface.
+configuration utilities. Check xref:requirement[] to know what
+Buildroot needs, and specifically the xref:requirement-optional[optional requirements]
+to get the dependencies of your favorite interface.
For each menu entry in the configuration tool, you can find associated
help that describes the purpose of the entry.
@@ -52,15 +52,15 @@ You *should never* use +make -jN+ with Buildroot: it does not support
'top-level parallel make'. Instead, use the +BR2_JLEVEL+ option to
tell Buildroot to run each package compilation with +make -jN+.
-This command will generally perform the following steps:
+The `make` command will generally perform the following steps:
-* Download source files (as required)
-* Configure, build and install the cross-compiling toolchain using the
- appropriate toolchain backend, or simply import an external toolchain
-* Build/install selected target packages
-* Build a kernel image, if selected
-* Build a bootloader image, if selected
-* Create a root filesystem in selected formats
+* download source files (as required);
+* configure, build and install the cross-compiling toolchain using the
+ appropriate toolchain backend, or simply import an external toolchain;
+* build/install selected target packages;
+* build a kernel image, if selected;
+* build a bootloader image, if selected;
+* create a root filesystem in selected formats.
Buildroot output is stored in a single directory, +output/+.
This directory contains several subdirectories:
diff --git a/docs/manual/writing-rules.txt b/docs/manual/writing-rules.txt
index c32f855..2a61639 100644
--- a/docs/manual/writing-rules.txt
+++ b/docs/manual/writing-rules.txt
@@ -121,5 +121,5 @@ The documentation
The documentation uses the
http://www.methods.co.nz/asciidoc/[asciidoc] format.
-Further details about the http://www.methods.co.nz/asciidoc/[asciidoc]
-syntax: refer to http://www.methods.co.nz/asciidoc/userguide.html[].
+For further details about the http://www.methods.co.nz/asciidoc/[asciidoc]
+syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[].
^ permalink raw reply related
* [Buildroot] [PATCH] ocf-linux: tweak kernel patch for newer kernels
From: Peter Korsgaard @ 2012-11-28 1:06 UTC (permalink / raw)
To: buildroot
In-Reply-To: <1354044188-23646-1-git-send-email-gustavo@zacarias.com.ar>
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Newer kernels had a slight change in the random number API so the OCF
Gustavo> patchset requires a slight tweak to build and run properly.
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] ocf-linux: tweak kernel patch for newer kernels
From: Peter Korsgaard @ 2012-11-28 1:05 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=670d60dc919fe6d99224ad1056c426812b38d108
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Newer kernels had a slight change in the random number API so the OCF
patchset requires a slight tweak to build and run properly.
Affected kernels are, per series:
>=3.0.41, >=3.2.29, >=3.4.9, >=3.5.2 and any newer version.
The fix is applied by detecting the API change rather than guessing the
kernel version.
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
linux/linux-ext-ocf-linux.mk | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/linux/linux-ext-ocf-linux.mk b/linux/linux-ext-ocf-linux.mk
index faf7360..1a601d5 100644
--- a/linux/linux-ext-ocf-linux.mk
+++ b/linux/linux-ext-ocf-linux.mk
@@ -15,6 +15,8 @@ LINUX_DEPENDENCIES += ocf-linux
define OCF_LINUX_PREPARE_KERNEL
support/scripts/apply-patches.sh $(LINUX_DIR) \
$(OCF_LINUX_DIR)/patches/ linux-3.2.1-ocf.patch ; \
+ grep -q __mix_pool_bytes $(LINUX_DIR)/drivers/char/random.c && \
+ $(SED) 's:wordcount\*4:&, NULL:' $(LINUX_DIR)/drivers/char/random.c ; \
cp -rf $(OCF_LINUX_DIR)/ocf $(LINUX_DIR)/crypto/ocf ;
endef
^ permalink raw reply related
* [Buildroot] [git commit] package: add libmatroska package
From: Peter Korsgaard @ 2012-11-28 0:43 UTC (permalink / raw)
To: buildroot
commit: http://git.buildroot.net/buildroot/commit/?id=d69172d7d807769f5091a612f7145bd464c7bc82
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
package/Config.in | 1 +
package/libmatroska/Config.in | 12 ++++++++++++
package/libmatroska/libmatroska.mk | 27 +++++++++++++++++++++++++++
3 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/package/Config.in b/package/Config.in
index fa04fd7..f3ca496 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -436,6 +436,7 @@ menu "Multimedia"
source "package/libdvdread/Config.in"
source "package/libdvdnav/Config.in"
source "package/libebml/Config.in"
+source "package/libmatroska/Config.in"
source "package/libmms/Config.in"
source "package/libmpeg2/Config.in"
source "package/libogg/Config.in"
diff --git a/package/libmatroska/Config.in b/package/libmatroska/Config.in
new file mode 100644
index 0000000..b1c53ee
--- /dev/null
+++ b/package/libmatroska/Config.in
@@ -0,0 +1,12 @@
+config BR2_PACKAGE_LIBMATROSKA
+ bool "libmatroska"
+ select BR2_PACKAGE_LIBEBML
+ depends on BR2_INSTALL_LIBSTDCPP
+ help
+ Extensible open standard audio/video container format access
+ library.
+
+ http://matroska.org
+
+comment "libmatroska requires a toolchain with C++ support"
+ depends on !BR2_INSTALL_LIBSTDCPP
diff --git a/package/libmatroska/libmatroska.mk b/package/libmatroska/libmatroska.mk
new file mode 100644
index 0000000..605a2fb
--- /dev/null
+++ b/package/libmatroska/libmatroska.mk
@@ -0,0 +1,27 @@
+#############################################################
+#
+# libmatroska
+#
+#############################################################
+
+LIBMATROSKA_VERSION = 1.3.0
+LIBMATROSKA_SOURCE = libmatroska-$(LIBMATROSKA_VERSION).tar.bz2
+LIBMATROSKA_SITE = http://dl.matroska.org/downloads/libmatroska/
+LIBMATROSKA_INSTALL_STAGING = YES
+LIBMATROSKA_LICENSE = LGPLv2.1+
+LIBMATROSKA_LICENSE_FILES = LICENSE.LGPL
+LIBMATROSKA_DEPENDENCIES = libebml
+
+define LIBMATROSKA_BUILD_CMDS
+ $(MAKE) -C $(@D)/make/linux CROSS="$(CCACHE) $(TARGET_CROSS)"
+endef
+
+define LIBMATROSKA_INSTALL_STAGING_CMDS
+ $(MAKE) -C $(@D)/make/linux prefix=$(STAGING_DIR)/usr install
+endef
+
+define LIBMATROSKA_INSTALL_TARGET_CMDS
+ $(MAKE) -C $(@D)/make/linux prefix=$(TARGET_DIR)/usr install
+endef
+
+$(eval $(generic-package))
^ 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