- Jul 12, 2010
-
-
Gustavo Zacarias authored
Closes #2166 Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
- Jul 09, 2010
-
-
Karl Krach authored
Signed-off-by:
Karl Krach <mailinglists@blueSpirit.la> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
We don't have a BR2_SOFT_FLOAT_FP option, and -mfloat-abi should also be used for big endian ARM. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
- Jul 08, 2010
-
-
Luca Ceresoli authored
Commit 7192668c introduced a wrong spelling of BR2_TOOLCHAIN_EXTERNAL_GLIBC that prevented libnss_files.so and libnss_dns.so from being installed. Signed-off-by:
Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Luca Ceresoli authored
Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
The makefile uses pkg-config for libxml2 support. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
TARGET_CONFIG_ENV got removed in e721a7c0 (Merge TARGET_CONFIGURE_ENV into TARGET_CONFIGURE_OPTS), so remove it from the recent libsvgtiny package as well. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
-
H Hartley Sweeten authored
Version 1.41.12 was released May 18, 2010. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Acked-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
- Jul 07, 2010
-
-
Peter Korsgaard authored
The bzip2 make install target follows symlinks, so if busybox is enabled and the bzip/bunzip2 applets are installed, bin/busybox will get overwritten by bzip2. Fix it by ensuring any previously installed bzip2/bunzip2/bzcat (the applets available in busybox) are removed before running make install. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Darius Augulis authored
Signed-off-by:
Darius Augulis <augulis.darius@gmail.com>
-
Thomas Petazzoni authored
Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Now that TARGET_CC contains several space-separated words, it must be used quoted everywhere. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Following the changes to TARGET_CC/TARGET_CXX to include the --sysroot option, these variables not only contain the path to the compiler, but also the --sysroot option. For that reason, we cannot anymore just use "test -x" to test for the compiler presence. Instead, we see if $(TARGET_CC) -v and $(TARGET_CXX) -v return a zero status. Moreover, --sysroot now needs to be filtered out of $(TARGET_CC) and not $(TARGET_CFLAGS) when asking the toolchain for its original sysroot and arch sysroot. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
TARGET_CONFIGURE_ENV defines CFLAGS, LDFLAGS, CXXFLAGS and FCFLAGS, separatly from all other variables that are part of TARGET_CONFIGURE_OPTS. This is useless and not consistent with the HOST_CONFIGURE_ variables, therefore we merge TARGET_CONFIGURE_ENV into TARGET_CONFIGURE_OPTS and fix the few users of TARGET_CONFIGURE_ENV. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
We now have for quite some time a configuration cache used to speed-up the execution of ./configure scripts when compiling programs for the target. This commit introduces a similar concept when Buildroot compiles programs for the host. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
These shouldn't be needed. Even when the cross-compiler is in $(STAGING_DIR)/usr/bin, we anyway use an absolute path for TARGET_CC, TARGET_LD and al. Not having $(STAGING_DIR)/{usr/bin,bin} in the PATH will avoid having Buildroot trying to run target binaries. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Those variables are not standard. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
The definition of CC, LD, GCC, CPP, CXX and FC shouldn't contain the CFLAGS/LDFLAGS/CXXFLAGS, those should be passed through the appropriate variables. However, the --sysroot option is a particular case here: it needs to be part of the CC/LD/GCC/etc. definitions otherwise libtool strips it from the CFLAGS/LDFLAGS. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
The external toolchain and internal toolchain cases both need to use the --sysroot option, and they have almost identical LDFLAGS/CFLAGS/CXXFLAGS definition, so we can factorize these definitions. Moreover, the --isysroot option is implied by --sysroot so there's no need to specify both. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Just as we did for LD/LDFLAGS, pass CFLAGS and CXXFLAGS in their own variables. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
When building packages for the host, the *_FOR_BUILD and *_FOR_TARGET variables are not needed. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
We build host tools installed in $(HOST_DIR)/usr/bin, and some of them rely on host libraries in $(HOST_DIR)/usr/lib. So when these host tools are executed, they need to find the host libraries, which are not installed in a default location. In c1b6242f we tried to use LD_LIBRARY_PATH when building target packages to solve this problem. Unfortunately, LD_LIBRARY_PATH is not only used to find libraries at run-time, but also at compile time. So it leads the build of some packages, such as icu, to fail. Therefore, in 0d1830b0, we reverted the LD_LIBRARY_PATH idea. The other option to solve this problem was to hardcode a RPATH value in the host binaries that would reference the location of host libraries. We added this -Wl,-rpath option to HOST_CFLAGS in 6b939d40. Unfortunately, this caused problems when building binutils, as reported in bug 1789 so this change was reverted in e1a7d916. Then, we tried to use -Wl,-rpath in HOST_LDFLAGS, but it was causing problems with fakeroot not recognizing 'ld' as the GNU linker, since the -Wl,-rpath cannot be understood by 'ld' directly, only by 'gcc'. This commit is a new attempt at using HOST_LDFLAGS, but in this case we modified the definition of HOST_LD to *not* contain HOST_LDFLAGS. LDFLAGS are being set separatly. It solved the fakeroot issue and was tested against nearly 300 packages of Buildroot. For more details on this story, see http://lists.busybox.net/pipermail/buildroot/2010-June/035580.html http://lists.busybox.net/pipermail/buildroot/2010-June/035581.html http://lists.busybox.net/pipermail/buildroot/2010-June/035586.html http://lists.busybox.net/pipermail/buildroot/2010-June/035609.html https://bugs.busybox.net/show_bug.cgi?id=1789 Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
The existing cross-compilation patch works with our not completely correct TARGET_CONFIGURE_OPTS. With the correct variables (CFLAGS, LDFLAGS) being passed, fontconfig was trying to use target CFLAGS/LDFLAGS when building tools for the host. This updated patch fixes that problem by correctly using the CC_FOR_BUILD, CFLAGS_FOR_BUILD variables. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Passing LDFLAGS/CFLAGS when building for the host allows cmake to be compiled with the proper -rpath value (the -rpath option is added to HOST_LDFLAGS in a later commit). Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
- Jul 06, 2010
-
-
Peter Korsgaard authored
Thanks to Thomas for noticing. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
As it doesn't use a ./configure, we need to pass it each time. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
And fix the .mk file name while we're at it. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Peter Korsgaard authored
Closes #2143 Fixes crash on static linking without stdio / x86. Both patches are from upstream uClibc. Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Thomas Petazzoni authored
ruby is converted to the autotools infrastructure, and the dependency on host-ruby is added since a ruby interpreter is needed to build a ruby interpreter. Fortunately, this is taken into account in the ruby build process, and it first start to build a mini-interpreter that is used to build the rest. However, this doesn't take the cross-compilation case into account, so we have to build ruby for the host. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
The .mk file was hacking the CC_FOR_BUILD value so that $(STAGING_DIR)/usr/include is added to the include path. This is not correct since $(STAGING_DIR) contains target stuff, not host stuff. The correct fix is to add a dependency on host-xproto_xproto, which will install the needed headers in $(HOST_DIR)/usr/include. In addition to that, a patch is added to make xlib_libXt build system behave properly in the cross-compilation case, where the makestrs tool needs to be built on the host as part of the compilation process. This was working before because of our quirky TARGET_CONFIGURE_OPTS, but those are going to be fixed in a future commit. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
gperf on the host is needed, since it is used by xcb-util to generate a perfect hash function. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Webkit depends on libjpeg, so add it as a dependency. Webkit also uses icu but fails to find it if we don't pass ac_cv_path_icu_config to its ./configure script. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
Until now, the function copy_toolchain_lib_root was copying a given library to the target filesystem by assuming that it should be at the same place it was in the toolchain sysroot. However, with Buildroot hiding libstdc++ in /usr/<target-name>/lib(64), this isn't correct, and it is probably safer not to rely on the toolchain organization anyway. Therefore : * Instead of having a single EXTERNAL_LIBS variable, we now have LIB_EXTERNAL_LIBS and USR_LIB_EXTERNAL_LIBS, which respectively list the libraries that should be copied to /lib and /usr/lib. As of today, only libstdc++ is part of the second list. * The copy_toolchain_lib_root takes another argument, which is the destination directory of the library, relative to $(TARGET_DIR) Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Thomas Petazzoni authored
Most toolchains have their libraries either in /lib or /usr/lib relative to their ARCH_SYSROOT_DIR. Buildroot toolchains, however, have basic libraries in /lib, and libstdc++/libgcc_s in /usr/<target-name>/lib(64). Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Thomas Petazzoni authored
The patch is already in upstream uClibc, in the master branch, at http://git.buildroot.net/uClibc/commit/?id=6f1daaaf2d94c1e6184add44eda38b0781b88cf0 . Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-