linux: make it possible to install the kernel in /boot
[Peter: always copy to output/images as requested by Luca] Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Makefile.package.in: Makes it possible to override the default extract commands
When using GENTARGETS (or macroes depending on it), there is no way of
specifying a custom extraction procedure. When using the patch one can
simply define $(PACKAGE_NAME)_EXTRACT_CMDS which will override the
default. If non is defined it will fall back to the default extract
procedure.
An example could look like this:
=== PACKAGE BEGIN ===
FGLRX_VERSION=11-3
FGLRX_SOURCE:=ati-driver-installer-$(FGLRX_VERSION)-x86.x86_64.run
FGLRX_SITE:=http://www2.ati.com/drivers/linux/
define FGLRX_EXTRACT_CMDS
sh $(DL_DIR)/$(FGLRX_SOURCE) --extract $(@D)
endef
$(eval $(call GENTARGETS,package,fglrx))
=== PACKAGE END ===
Peter Korsgaard [Tue, 5 Jul 2011 12:58:20 +0000 (14:58 +0200)]
lame: fix build if host has libgtk12-dev (gtk-config)
Lame contains an optional gtk12 based frame analyzer application, which
will be built if gtk12 is detected (using gtk-config). We no longer
have support for (the obsolete) gtk12 in BR, but the host might have
gtk-config, so forcible disable it.
Maxime Ripard [Wed, 29 Jun 2011 13:46:20 +0000 (15:46 +0200)]
Rework the logging daemons startup
The logging mechanism startup being in inittab, it isn't easy to
overcharge the default policy. With this patch, the startup of the
syslog daemon is moved to an init.d script, that can easily be
overwritten.
Peter Korsgaard [Mon, 27 Jun 2011 09:56:11 +0000 (11:56 +0200)]
qt: fix webkit/sqlite build without largefile support
The embedded sqlite module forces FILE_OFFSET_BITS=64 unless
SQLITE_DISABLE_LFS is defined, breaking the build for !largefile toolchains.
Webkit internally builds sqlite, so that's affected as well.
Fix it by passing -DSQLITE_DISABLE_LFS in C/CXXFLAGS for !largefile
builds, similar to how we do it for the standalone sqlite package.
Mike Williams [Wed, 11 May 2011 20:19:56 +0000 (16:19 -0400)]
package: Added Live555 RTSP Server package
[Peter: misc fixes, use real version, correct compile/link flags] Signed-off-by: Mike Williams <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Luca Ceresoli [Mon, 20 Jun 2011 15:59:55 +0000 (17:59 +0200)]
berkeleydb: fix build of shared libraries
009d8fceab4 and 0a5e5534cbf8 moved the --enable-static configure flag
from package files to the default _CONFIGURE_CMDS in
package/Makefile.autotools.in.
This broke Autotools packages that override _CONFIGURE_CMDS.
Luca Ceresoli [Mon, 20 Jun 2011 15:59:54 +0000 (17:59 +0200)]
ffmpeg: fix build of shared libraries
009d8fceab4 and 0a5e5534cbf8 moved the --enable-static configure flag
from package files to the default _CONFIGURE_CMDS in
package/Makefile.autotools.in.
This broke Autotools packages that override _CONFIGURE_CMDS.
Peter Korsgaard [Fri, 17 Jun 2011 07:10:29 +0000 (09:10 +0200)]
bmon: link dynamically unless explicitly requested otherwise
Commit 009d8fceab4d (add --{enable,disable}-{shared,static} automatically)
caused us to pass --enable-static in the normal (non-static) case as well,
which bmon interpretes as a request to link the bmon program statically,
bloating the image.
Fix it by passing an extra --disable-static to bmon configure to nullify
this.
For target packages, depending on BR2_PREFER_STATIC_LIB, add the
correct combination of --{enable,disable}-{shared,static} flags to
./configure calls.
* When BR2_PREFER_STATIC_LIB is enabled, we pass --enable-static
--disable-shared.
* When BR2_PREFER_STATIC_LIB is disabled, we pass --enable-static
--enable-shared. We enable static libraries since they can still be
useful to statically link applications against some libraries
(sometimes it is useful for size reasons). Static libraries are
anyway only installed in the STAGING_DIR, so it doesn't increase in
any way the size of the TARGET_DIR.
For host packages, always pass --enable-shared and --disable-static.
Unfortunately, the official Blackfin toolchains are built without the
shadow password support, so our default Busybox configuration fails to
build.
Therefore, we introduce a new hidden knob
BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS, which is set to yes for Buildroot
internal toolchain, for toolchains generated by the Crosstool-NG
backend, for Glibc external toolchains and for Uclibc custom external
toolchains. It is left unset by the Blackfin toolchain profile.
Thomas Petazzoni [Sun, 22 May 2011 11:56:08 +0000 (13:56 +0200)]
fakeroot: disallow selection for the target
fakeroot for the target fails to build against glibc, due to largefile
related problems :
libtool: link: /home/test/outputs/test-503/host/usr/bin/powerpc-linux-gnu-gcc -pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -o faked faked.o ./.libs/libcommunicate.a -ldl
{standard input}: Assembler messages:
{standard input}:2592: Error: symbol `__fxstatat64' is already defined
{standard input}:2627: Error: symbol `__fxstat64' is already defined
{standard input}:2663: Error: symbol `__xstat64' is already defined
{standard input}:2698: Error: symbol `__lxstat64' is already defined
make[3]: *** [libfakeroot.lo] Error 1
As fakeroot for the target is not really needed, and was only added
when we packaged fakeroot for the host, just make fakeroot not
selectable for the target.
We have to keep the AUTOTARGETS call for fakeroot on the target,
because the host variant does not work otherwise, due to issues in the
package infrastructure (that will be fixed post-2011.05).
If the scripttools are enabled in the Qt configuration, but not the
gui, then the scripttools library is not built by Qt, and the
Buildroot build process fails with:
cp: cannot stat `/home/test/outputs/test-502/host/usr/sh4-unknown-linux-gnu/sysroot/usr/lib/libQtScriptTools.so.*': No such file or directory
Thomas Petazzoni [Sat, 21 May 2011 15:47:50 +0000 (17:47 +0200)]
psmisc: do not install pstree.x11 symbolic link
The psmisc-no-__progname.patch removes the usage of __progname, which
removes any difference between pstree and pstree.x11. Therefore, we
make sure to not create the pstree.x11 symbolic link in the target.
Yann E. MORIN [Sat, 21 May 2011 22:05:42 +0000 (00:05 +0200)]
toolchain/crosstool-NG: fix up ct-ng config file to saner defaults
Peter on IRC reported some build failures for different targets.
They were of two kinds:
- missing/unknown stack unwinding support
- missing *_chk functions
The first is about configure not being able to automagically determine
if stack unwinding support is available for the target. The second is
about fortified build forgetting to build the fortified functions.
This applies to both glibc and eglibc.
After some discussions on IRC with Jacmet, it appears that we can
safely assume both of the following:
- virtually all targets of buildroot will have stack unwinding support
- we do not care about fortified builds (so far)
So, update the bundled crosstool-NG .config file to saner defaults:
- force unwind support
- disable fortified builds
[Peter: fix 'force non-fortified build' sed invocation] Reported-by: Peter Korsgaard <[email protected]> Signed-off-by: "Yann E. MORIN" <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Yann E. MORIN [Sat, 21 May 2011 22:05:41 +0000 (00:05 +0200)]
toolchain/crosstool-NG: update to 1.11.3
1.11.3 is the latest stable version, and it has a few improvements
we'll find usefull. For example, it hasa a boolean option for
disabling the {,e}glibc fortified build (instead of requiring us
to shoehorn it in extra cflags.
Thomas Petazzoni [Thu, 19 May 2011 17:23:29 +0000 (19:23 +0200)]
bind: give path to OpenSSL when OpenSSL is enabled
bind needs to be specifically told where OpenSSL is, otherwise, the
build fails with:
checking for OpenSSL library... configure: error: OpenSSL was not found in any of /usr /usr/local /usr/local/ssl /usr/pkg /usr/sfw; use --with-openssl=/path
If you don't want OpenSSL, use --without-openssl
projects / buildroot-mgba.git / log