summaryrefslogtreecommitdiffstats
path: root/toolchain/external-toolchain/ext-tool.mk
Commit message (Collapse)AuthorAgeFilesLines
* DNS resolv problem with glibcAnders Darander2009-09-151-1/+1
| | | | | | | | | | Fix problem with dns resolv, by copying the libnss_dns.so to the rootfs. Using glibc from external toolchain, name resolving does not work, unless libnss_dns.so is available on the target. Signed-off-by: Anders Darander <ad@datarespons.se> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Fix PROGRAM_INVOCATION handling with external toolchainsThomas Petazzoni2009-07-311-1/+3
| | | | | | | | | | | | | BR2_UCLIBC_PROGRAM_INVOCATION is a toolchain configuration option, like BR2_INET_IPV6, BR2_INET_RPC, on which some packages depend. Therefore, it should be handled like BR2_INET_IPV6 and BR2_INET_RPC in order to work properly with external toolchains. Since we move it out of toolchain/uClibc/Config.in into toolchain/Config.in.2, we rename the option to BR2_PROGRAM_INVOCATION (since BR2_INET_RPC and others don't have UCLIBC in their name). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: check cross-compiler existenceThomas Petazzoni2009-07-171-0/+10
| | | | | | | | | As a minimal test to the external toolchain, check that $(TARGET_CC) is actually an existing executable file. That way, if the user misconfigures the toolchain path and/or prefix, a meaningful error message will be shown. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: respect $(Q)Thomas Petazzoni2009-07-171-5/+5
| | | | | | | | Use $(Q) in external toolchain support so that the user can get the full output by passing V=1 to make, and still get a nice and clean output by default. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: copy the C++ standard library if neededThomas Petazzoni2009-07-171-0/+4
| | | | | | | | Obey the BR2_INSTALL_LIBSTDCPP configuration option to copy the C++ standard library to the target. Suggested by Lionel Landwerlin <lionel.landwerlin@openwide.fr>. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: do not copy useless symbolic linksThomas Petazzoni2009-07-171-1/+1
| | | | | | | Do not copy .so symbolic links to target when not needed. Only copy .so.X symbolic links and the library itself. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: more documentation about the principlesThomas Petazzoni2009-07-171-0/+31
| | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: use LANG=C when calling gcc -vThomas Petazzoni2009-07-171-2/+2
| | | | | | | | | | | | Lionel Landwerlin <lionel.landwerlin@openwide.fr> reported that using the external toolchain support when LANG=fr_FR.UTF-8 doesn't work, since the messages printed by gcc -v are translated in another language, defeating the grep ^Configured test. Therefore, as per Lionel suggestion, we force LANG=C when calling $(TARGET_CC) -v. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external-toolchain: better documentation, cleanup, sysroot checkThomas Petazzoni2009-07-171-34/+81
| | | | | | | | | | | | | | | | * Introduce documentation for each function of ext-tool.mk, and document all parameters of the functions. * Pass SYSROOT_DIR as argument to all functions that require it, instead of computing it manually everywhere * Use $(shell) instead of backquotes * Check that the SYSROOT_DIR variable is not empty, which means that the external toolchain doesn't support --sysroot. In that case, bail out with a nice error message. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* external toolchain: fix libraries copy and add ARM ABI checkThomas Petazzoni2009-07-161-20/+37
| | | | | | | | | | Instead of hardcoding the C library versions, just copy the version available in $SYSROOT_DIR/lib. Add a check on the ARM ABI configured in Buildroot with regard to the ABI of the external toolchain provided. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Improve external toolchain checksThomas Petazzoni2009-06-151-0/+51
| | | | | | | | | | | | | | | | | | | | | This patch adds some checks on the external toolchains. First, it checks that the C library selection is correct, by looking if gcc is able to find the main C library file through the -print-file-name option. Then, it attempts to check if the Buildroot toolchain options match the configuration of the toolchain : * for glibc, it checks that IPv6, RPC, locales, wide-char, large file support Buildroot options are enabled, since with glibc all these features are always available (at least this is the assumption we make) ; * for uClibc, it checks the Buildroot options with the uClibc configuration file in $SYSROOT_DIR/usr/include/bits/uClibc_config.h Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Simple glibc-based external toolchain supportThomas Petazzoni2009-06-151-8/+16
| | | | | | | | | | | | | | | | | | | | The current Buildroot works just well with sysrootable glibc toolchains, using the external toolchain feature. The only thing that needs to be customized is the set of libraries that must be compiled to the target. The following patch takes a simple approach to making it easier for users to use glibc toolchains. It just adds a uClibc/glibc choice in the external toolchain menu. Then, depending on that selection, the configuration system will choose a sane default value for the library files list. The other advantage of having a uClibc/glibc choice is that in the future, we'll be able to add checks verifying that the external toolchain configuration matches the features selected in Buildroot (in terms of IPv6, RPC, locales or large file support). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: revert r25193 (Change binary toolchain configuration)Peter Korsgaard2009-02-041-1/+0
| | | | As discussed on the list.
* Change binary toolchain configuration, soUlf Samuelsson2009-01-311-0/+1
| | | | | | | | | | | that the options become visible just below the config, instead of at bottom of screen Create a more useful default as toolchain path. Allow generation of a script which sets up paths to a binary toolchain generated by buildroot.
* toolchain/external-toolchain/ext-tool.mk: Support non sysroot-able toolchainsDaniel Laird2009-01-121-3/+3
| | | | | | | Only copy the sysroot files if the toolchain was built with sysroot support. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* Another external toolchain support solutionThomas Petazzoni2008-12-131-0/+6
| | | | | | | | | | | | | | | | | | | | * In toolchain/external-toolchain/ext-tool.mk, copy the contents of the sysroot directory to the staging dir. * In package/Makefile.in, add a --sysroot CFLAGS pointing to the staging dir * Remove the CFLAGS and LDFLAGS definition from TARGET_CONFIGURE_OPTS. I haven't investigated exactly why, but with these options, DirectFB fails to build because it cannot find PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP, even if DirectFB's Makefile properly sets -D_GNU_SOURCE. I have already sent this patch on December, 2nd to the mailing-list, but got no feedback. So let's commit and see what happens :-) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* More external toolchain fixesPeter Korsgaard2008-11-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix issues with binary external toolchains Fix two problems encountered while using an external binary toolchain generated by crosstool-ng: - Don't remove the ending / in LIB_DIR, otherwise find $LIB_DIR -maxdepth 1 doesn't find any file in the case LIB_DIR is a symbolic link and not a directory. For some reason, find -maxdepth 1 doesn't have the same behaviour on directories and symbolic links. Demonstration: $ mkdir foobar $ touch foobar/t1 $ touch foobar/t2 $ ln -s foobar barfoo $ find foobar -maxdepth 1 -name 't*' foobar/t1 foobar/t2 $ find barfoo -maxdepth 1 -name 't*' $ find barfoo/ -maxdepth 1 -name 't*' barfoo/t1 barfoo/t2 * Make sure the libraries are writable, otherwise the strip operation might fail. The library files may not be writable if the toolchain is not writable (which may happen if one wants to prevent anyone from overwriting the toolchain, which is done by crosstool-ng, for example). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Typo fix in toolchain/external-toolchain/ext-tool.mkPeter Korsgaard2008-10-171-1/+1
| | | | | | From: Grant Likely <grant.likely@secretlab.ca> Comment block header documentation typo
* - global whitespace trimmingBernhard Reutner-Fischer2007-08-221-37/+37
|
* - random whitespace cleanupBernhard Reutner-Fischer2007-08-221-1/+1
|
* - semicolon touchup. No other changesBernhard Reutner-Fischer2007-08-221-4/+4
|
* Some 'find' commands get a little picky."Steven J. Hill"2007-04-191-1/+1
|
* Support building using an external toolchain. Questions to the mailing list ↵"Steven J. Hill"2007-02-061-0/+56
and all other comments to <biteme@devnull.com>.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-08 10:55:19 +0000