- May 03, 2010
-
-
Lionel Landwerlin authored
Signed-off-by:
Lionel Landwerlin <llandwerlin@gmail.com> Acked-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Lionel Landwerlin authored
Signed-off-by:
-
Peter Korsgaard authored
Signed-off-by: -
Lionel Landwerlin authored
Signed-off-by:
-
- May 02, 2010
-
-
Peter Korsgaard authored
These are ancient (2006) and upstream strongly discourage using them: ftp://sourceware.org/pub/gdb/old-releases/README Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
It got broken by the introduction of the new autotools infrastructure based on the generic infrastructure. Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
Instead of asking the user about the GNU target suffix, just compute it automatically from the other configuration options. Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
The ROOTFS_SUFFIX thing has been removed in 325bfd1c, so get rid of the last users. Signed-off-by:
-
Thomas Petazzoni authored
In both internal and external toolchain cases, KERNEL_CROSS was defined to *exactly* the same value as TARGET_CROSS. It isn't modified anywhere, and is just used by kernel compilation and pcmcia compilation. Therefore, get rid of KERNEL_CROSS and use TARGET_CROSS instead. Signed-off-by:
-
Thomas Petazzoni authored
The definition of TOOLCHAIN_DIR is the same regardless of whether external or internal toolchains are used. Moreover, move its definition together with all the other *_DIR definitions. Signed-off-by:
-
Thomas Petazzoni authored
Since new configuration options have been added in 0.9.31, the value of these configuration options should be determined, either by the default configuration file we provide, or by uclibc.mk process. The locale generation process should probably be improved in order to allow building other locales than just en_US. [Peter: fixup locale handling, add PROGRAM__NAME to defconfig] Signed-off-by:
-
Thomas Petazzoni authored
UCLIBC_HAS_NFTW is a new knob in 0.9.31, which allows the obsolete and deprecated ftw() to be compiled-out separatly from nftw(), which is part of POSIX. nftw() should probably be enabled by default in uClibc, and a bug has been opened about this on uClibc bug tracker (https://bugs.busybox.net/show_bug.cgi?id=1597 ). nftw() is, for example, used in Gtk+. Signed-off-by:
Paulius Zaleckas <paulius.zaleckas@gmail.com> Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Thomas Petazzoni authored
When FOO_LIBTOOL_PATCH is defined, assume that the same value should be used for HOST_FOO_LIBTOOL_PATCH. Signed-off-by:
-
Thomas Petazzoni authored
OpenSSL is not using the autotools as its build system. Therefore, we must use the generic infrastructure instead of the autotools one. Signed-off-by:
-
Thomas Petazzoni authored
Do not build against libgcrypt on the host, since we don't build libgcrypt ourself, and it might fail even when libgcrypt is installed on the host: ...configure... checking for libgcrypt-config... /usr/bin/libgcrypt-config Crypto extensions will be available. ...build... gcc: /usr/lib/libgcrypt.so: No such file or directory Signed-off-by:
-
Thomas Petazzoni authored
The autoreconf check was incorrect, missing a $ sign to properly reference a package-specific variable. There was no visible effect until now since : * The existing syntax allowed to access the value defined in the package specific .mk file, so when AUTORECONF was set to YES by a package, it was working. * The default value in Makefile.autotools.in was NO. In fact, when a package .mkf file wasn't defining the AUTORECONF variable, the Makefile.autotools.in test was testing the empty string against 'YES', which was false, leading to the AUTORECONF not being done, which was the desired effect. However, in a later patch, we intend to change this default value. Signed-off-by:
-
Peter Korsgaard authored
install -D needs the destination filename, not just it's directory, otherwise we end up with a pkgconfig file instead. Signed-off-by: -
Peter Korsgaard authored
Signed-off-by: -
Lionel Landwerlin authored
Signed-off-by:
-
Lionel Landwerlin authored
Signed-off-by:
-
Lionel Landwerlin authored
autoheader is used by autoreconf, therefor we need to give the right path to this tools for host/target autoreconfiguration. Signed-off-by:
-
Lionel Landwerlin authored
Signed-off-by:
-
Lionel Landwerlin authored
Signed-off-by:
-
Lionel Landwerlin authored
Signed-off-by:
-
Lionel Landwerlin authored
Signed-off-by:
-
- May 01, 2010
-
-
Luca Ceresoli authored
Fixes error: "Couldnt load module pthres" and similar. Original patch: svn://svn.berlios.de/tslib/trunk@56 . Signed-off-by:
Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by:
-
Paulius Zaleckas authored
When compiling GDB for target (in my case i386) it links wrong BFD library from host OS. This prevents GDB from compiling support for ELF and thus GDB is unusable on target. More about this issue was already posted at: http://lists.uclibc.org/pipermail/buildroot/2009-March/026585.html Fix this issue by forcing ELF support. Signed-off-by:
-
Gustavo Zacarias authored
Closes #719 Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
-
Gustavo Zacarias authored
Closes #803 Based on initial patch by rvpaasen@t3i.nl [Peter: lua/luac needs liblua.so.* on target] Signed-off-by:
-
Darius Augulis authored
[Peter: XF86DRIPROTO should only be selected if mesa is enabled] Signed-off-by:
Darius Augulis <augulis.darius@gmail.com> Signed-off-by:
-
Darius Augulis authored
While at it convert spaces to TABs Signed-off-by:
-
Paulius Zaleckas authored
Signed-off-by:
-
Darius Augulis authored
These packages have buggy configure script. It adds -L/lib flag for linker and thus wrong libraries are linked in. Workaround this issue by setting expat=yes in configure environment. Signed-off-by:
-
Paulius Zaleckas authored
Signed-off-by:
-
