libffi: switch to using a Git version, brings Microblaze and Xtensa support
We already had backported patches for the Blackfin and AArch64
support, and now we would have needed to also backport the Xtensa
support and the Microblaze support. This starts to get crazy.
Let's switch to using a Git version from Github, until libffi finally
releases a new stable version.
In order to achieve this, we also need to:
* autoreconf the package, so that a libffi.pc file gets generated
* manually install the libffi.pc file, because it doesn't get
installed by libffi Makefile, for some reason
* remove the part of the target post install hook that was messing
with libffi.pc, since it was modifying the one in STAGING_DIR
(which is odd for a target post install hook), and the libffi.pc
file is anyway not installed to the target anymore.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Chris Zankel [Mon, 4 Feb 2013 12:52:08 +0000 (12:52 +0000)]
util-linux: add support for Xtensa
[Thomas Petazzoni: rename patch to not have the package version in the
patch file name, adjust the commit title.]
Signed-off-by: Chris Zankel <chris@zankel.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
As we are going to add an Xtensa related patch that needs to be
applied *after* the AArch64 patch, let's first add a number to each
util-linux patch file name, so that we know they will be applied in
the right order.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
The external toolchain wrapper sets sysroot etc. to an absolute path.
By changing this to a relative path, it is possible to move the host
directory to a different location and still have a working build
system.
This only works for a downloaded external toolchain. For a pre-installed
external toolchain, it is possible to move the host directory to a
different location, but not the external toolchain directory (it does work
if the external toolchain directory lies within the host directory). For
an internal or crosstool-ng toolchain, there is no wrapper so updating the
sysroot path should be done in a different way.
See http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html
for information about others things to do to make the host directory
relocatable.
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>
While the fix makes gnutls build without wchar, it doesn't actually work as
there's no rpl_wctomb implementation so the .so ends up with an undefined
reference to wctomb:
./host/usr/bin/arm-linux-nm -D staging/usr/lib/libgnutls.so.28|grep wctomb
U wctomb
Causing linker errors for packages trying to use it:
CCLD msmtp
host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libgnutls.so:
undefined reference to `wctomb'
collect2: ld returned 1 exit status
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
gdb 7.4.1 fails with the following error
gdb-7.4.1/gdb/linux-nat.h:79:18: error: field 'siginfo' has incomplete type
because gdb use 'struct siginfo' instead of 'struct siginfo_t'.
Crosstool-NG allready use the patches to prevent this error so use this
patches for buildroot too.
see also http://permalink.gmane.org/gmane.comp.gcc.cross-compiling/15305
Stefan Fröberg [Wed, 30 Jan 2013 02:46:40 +0000 (02:46 +0000)]
pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files
This patch will add <pkg>_CONFIG_FIXUP variable to buildroot infra.
It's purpose is to inform buildroot that the package in question
contains some $(STAGING_DIR)/usr/bin/*-config files and that we
want to automatically fix prefixes of such files.
It is often the case that many packages call these
files during their configuration step to determine 3rd party
library package locations and any flags needed to link against them.
For example:
Some package might try to check the existense and linking flags
of NSPR package by calling $(STAGING_DIR)/usr/bin/nspr-config --prefix.
Without this fix. NSPR would return /usr/ as it's prefix which is
wrong when cross-compiling.
Correct would be $(STAGING_DIR)/usr.
All packages that have <pkg>_INSTALL_STAGING = YES defined and
also install some config file(s) into $(STAGING_DIR)/usr/bin must
hereafter also define <pkg>_CONFIG_FIXUP with the correspondig
filename(s).
This commit fixes the exact same problem than 21a0c11a90f9ff19c78a5f32e0a2e9064fd28054, but for the gdbserver
build. The problem is that when you use the Crosstool-NG toolchain
backend, gawk gets built as a dependency of Crosstool-NG. So the gdb
configure scripts detects it, and assumes it is in the PATH (because
the gdb configure step gets run with TARGET_MAKE_ENV).
But then, the build fails, because it tries to run gawk, but gawk
isn't in the PATH, because we forget to use this TARGET_MAKE_ENV
variable when building gdbserver.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
tvheadend requires an atomic_add operation. Either you have a gcc >=
4.3 toolchain and it uses the gcc intrinsics, or it has special code
for x86, x86-64, PPC and ARM. So in the context of Buildroot, the only
really problematic architecture is avr32, which uses gcc 4.2.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
We have a patch that allows neard to build even on toolchain using old
kernel headers that lack the nfc.h header. However, after the bump to
neard 0.9, this patch was not updated to take into account the two new
plugins that neard has added.
Marek Belisko [Mon, 7 Jan 2013 10:43:18 +0000 (10:43 +0000)]
lvm2: add option for application library
[Peter: make mutual exclusive with dmsetup-only, drop special install / make] Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Marek Belisko [Fri, 18 Jan 2013 12:08:46 +0000 (12:08 +0000)]
lvm2: Install devmapper.pc to staging/target pkgconfig directory.
Without this change if some package which have dependency on device mapper
and use pkgconfig to check version always fail to find library because
devmapper.pc file wasn't installed.
Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Simon Dawson [Sun, 20 Jan 2013 11:55:41 +0000 (11:55 +0000)]
avr32: support uClibc 0.9.33.2
Add a uClibc patch from OpenWRT, and tweak an existing patch to cope with
the lack of a dup3 Linux syscall on avr32. This allow uClibc 0.9.33.2 to be
built for avr32.
[Peter: add upstream url for openwrt patch] Signed-off-by: Simon Dawson <spdawson@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
arch/Config.in.arm: Use armv6k for arm1136jf-s rev1
According to the ARM1136JF-S and ARM1136J-S Revision r1p5 Technical Reference
Manual, from release rev1 (r1pn), the ARM1136JF-S processor implements the ARMv6
instruction set with the ARMv6k additions.
This patch differentiates the ARM1136JF-S revisions 0 and 1 in order to use
either ARMv6j (e.g. on Freescale i.MX31) or ARMv6k (e.g. on Freescale i.MX35).
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
blackfin: add 2012r2 and remove 2010rc1 toolchains
Remove the old 2010RC1 toolchain and add the new 2012R2-RC2 toolchain.
On related good news the new toolchain fixes:
http://autobuild.buildroot.net/results/eac5bd4f4766d98431e72a3c81492a962c85fa98/
since it's got unshare() support now.
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Danomi Manchego [Wed, 30 Jan 2013 17:26:37 +0000 (17:26 +0000)]
cjson: change source to svn repo
The original cJSON submittal downloaded a .zip file from SourceForge.
The .zip file did not have a version number, making it impossible
to gaurantee that the same archive is downloaded on any given build.
It also required a custom EXTRACT command.
This patch changes the source for cJSON to the svn repository
listed on the sf project web page - giving us an actual version
number, and letting us use buildroot's normal extraction functionality.
Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Chris Zankel [Tue, 22 Jan 2013 10:33:19 +0000 (10:33 +0000)]
xtensa: sqlite requires special compiler option
Some of the generated object files are too large for PC-relative addressing,
so use the -mtext-section-literals compiler flag to move symbols closer to
the code.
[Peter: fix commit message] Signed-off-by: Chris Zankel <chris@zankel.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Gustavo Zacarias [Tue, 29 Jan 2013 11:20:04 +0000 (11:20 +0000)]
olsr: bump to version 0.6.4
Bump olsrd to version 0.6.4
Fixes:
http://autobuild.buildroot.net/results/553c8157cd83ca60475caacc119779c778806781/
which is due to the old version not being friendly with newer flex
versions.
Enabled more plugins to make it more useful.
Switch to forked mode in the init script to avoid console noise.
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Stephan Hoffmann [Mon, 28 Jan 2013 23:53:52 +0000 (23:53 +0000)]
New package: cache-calibrator
The Calibrator is a small C program that is supposed to analyze
a computers (cache-) memory system and extract the following
parameters:
number of cache levels
for each cache level:
its size
its linesize
its access/miss latency
main memory access latency
number of TLB levels
for each TLB level:
its capacity (i.e. number of entries)
the pagesize used
the TLB miss latency
http://homepages.cwi.nl/~manegold/Calibrator/
It is also recommended as a load generator for realtime testing in:
Daniel Nelson [Sun, 27 Jan 2013 15:38:56 +0000 (15:38 +0000)]
python3: Fix pyc-only related runtime exceptions
Python3 changes the pyc lookup strategy, ignoring the
__pycache__ directory if the .py file is missing. Change
install location to enable use of .pyc without their parent .py
See http://www.python.org/dev/peps/pep-3147
[Peter: add patch header] Signed-off-by: Daniel Nelson <daniel@sigpwr.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout at mind.be>
(untested) Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Thomas Petazzoni [Sun, 27 Jan 2013 05:35:12 +0000 (05:35 +0000)]
olsr: rework build and install procedure
This commit reworks the build and install steps of the olsr package,
to fix a number of problems and do minor improvements:
1. The build step was doing "make <foo>" for each
plugin. Unfortunately, inside olsr build system, doing "make
<foo>" for a plugin triggers a clean of the plugin directory, a
build, and then an installation of the plugin. This installation
fails because DESTDIR is not passed at the install step. This
leads to build issues like
http://autobuild.buildroot.org/results/a9fed78cd0b3991763a797c38387edd4157fbdb9/build-end.log. To
fix this, we call make in each plugin's directory, which is what
"make <foo>" was doing internally.
2. The install step was manually installing the olsrd binary. We now
instead use the install_bin make target that comes in olsr's build
system.
3. The install step was manually installing the olsr plugins. We now
instead use the install make target available in each plugin's
makefile.
4. We use 'install' to install the init script, which avoids the
manual creation of /etc/init.d.
5. We use 'install' to install the sample configuration file.
6. We remove the useless strip commands.
7. We add a patch that allows us to pass LDCONFIG=/bin/true to avoid
ldconfig being called during the installation process.
8. We remove commands from the clean step that were in fact
uninstallation commands. We don't bother re-adding those commands
in an uninstallation step, since it is now generally accepted that
the uninstall step is quite useless and should be deprecated.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Thomas Petazzoni [Sun, 27 Jan 2013 05:07:19 +0000 (05:07 +0000)]
polkit: don't build documentation and examples
Building the manpages of polkit fails with issues in xsltproc. Since
we are generally not that much interested in documentation, we disable
them. This solves the build issues like
http://autobuild.buildroot.org/results/751b71a594fa04924c7c3bb8f2c460ce1e44aa90/build-end.log.
While we're at it, we also disable the build of the polkit example
programs.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Patrick Gerber [Tue, 22 Jan 2013 00:09:32 +0000 (00:09 +0000)]
Yavta: new package
[Peter: License is GPLv2+, move out of package/multimedia] Signed-off-by: Patrick Gerber <kpa_info@yahoo.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
projects / coffee / buildroot.git / log