From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: external-toolchain gcc
Date: Mon, 02 Feb 2009 13:20:09 +0100 [thread overview]
Message-ID: <87k589ghdy.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090131205000.AC6B47621A@busybox.osuosl.org> (ulf@uclibc.org's message of "Sat\, 31 Jan 2009 20\:50\:00 +0000 \(UTC\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2009-01-31 20:49:59 +0000 (Sat, 31 Jan 2009)
ulf> New Revision: 25193
ulf> Log:
ulf> Change binary toolchain configuration, so
ulf> that the options become visible just below
ulf> the config, instead of at bottom of screen
ulf> Create a more useful default as toolchain path.
ulf> Allow generation of a script which sets up
ulf> paths to a binary toolchain generated by buildroot.
What bug does this fix? Please DON'T add any new features to svn now.
ulf> Modified: trunk/buildroot/toolchain/external-toolchain/Config.in.2
ulf> ===================================================================
ulf> --- trunk/buildroot/toolchain/external-toolchain/Config.in.2 2009-01-31 20:44:04 UTC (rev 25192)
ulf> +++ trunk/buildroot/toolchain/external-toolchain/Config.in.2 2009-01-31 20:49:59 UTC (rev 25193)
ulf> @@ -3,9 +3,12 @@
ulf> if BR2_TOOLCHAIN_EXTERNAL
ulf> config BR2_TOOLCHAIN_EXTERNAL_PATH
ulf> string "External toolchain path"
ulf> - default "/path/to/staging_dir/usr"
ulf> + default "$(GCCROOT)"
ulf> help
ulf> Path to where the external toolchain is installed.
ulf> + Either define GCCROOT in your environment
ulf> + or an absolute path like:
ulf> + "/path/to/staging_dir/usr"
NACK. Let's not add any more magic environment variables (and
certainly not when they are not prefixed with BUILDROOT_).
ulf> config BR2_TOOLCHAIN_EXTERNAL_PREFIX
ulf> string "External toolchain prefix"
ulf> --- trunk/buildroot/toolchain/external-toolchain/ext-tool.mk 2009-01-31 20:44:04 UTC (rev 25192)
ulf> +++ trunk/buildroot/toolchain/external-toolchain/ext-tool.mk 2009-01-31 20:49:59 UTC (rev 25193)
ulf> @@ -60,3 +60,4 @@
ulf> $(call copy_toolchain_lib_root, $$libs, /lib, $(BR2_TOOLCHAIN_EXTERNAL_STRIP)); \
ulf> done
ulf> $(call copy_toolchain_sysroot)
ulf> +
Why?
ulf> Modified: trunk/buildroot/toolchain/gcc/gcc-uclibc-4.x.mk
ulf> ===================================================================
ulf> --- trunk/buildroot/toolchain/gcc/gcc-uclibc-4.x.mk 2009-01-31 20:44:04 UTC (rev 25192)
ulf> +++ trunk/buildroot/toolchain/gcc/gcc-uclibc-4.x.mk 2009-01-31 20:49:59 UTC (rev 25193)
ulf> @@ -498,5 +498,23 @@
ulf> @echo GCC_PATCH_DIR=$(GCC_PATCH_DIR)
ulf> @echo GCC_SITE=$(GCC_SITE)
ulf> +GCCSCRIPT=$(ARCH)-uclibc-gcc-$(BR2_GCC_VERSION).sh
ulf> +
ulf> +gccscript:
ulf> + @rm -f $(GCCSCRIPT)
ulf> + @rm -f gcc.sh
ulf> + @echo "#!/bin/sh" > $(GCCSCRIPT)
ulf> + @echo "# $(ARCH) cross compiler toolchain created $(DATE)" >> $(GCCSCRIPT)
ulf> + @echo "# gcc-$(BR2_GCC_VERSION)" >> $(GCCSCRIPT)
ulf> + @echo "# binutils-$(BR2_BINUTILS_VERSION)" >> $(GCCSCRIPT)
ulf> + @echo "# uClibc-$(UCLIBC_VER)" >> $(GCCSCRIPT)
ulf> + @echo "export GCCROOT=$(BR2_STAGING_DIR)/usr" >> $(GCCSCRIPT)
ulf> + @echo "export PATH=\$$GCCROOT/bin:\$$PATH" >> $(GCCSCRIPT)
ulf> + @echo "export GCCPREFIX=$(ARCH)-linux" >> $(GCCSCRIPT)
ulf> + @echo "export CROSS_COMPILE=\$$GCCPREFIX-" >> $(GCCSCRIPT)
ulf> + @chmod a+x $(GCCSCRIPT)
ulf> + @ln -s $(GCCSCRIPT) gcc.sh
ulf> + @echo "$(GCCSCRIPT) created"
ulf> + @more $(GCCSCRIPT)
And this neither.
Please revert.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-02 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 20:50 [Buildroot] svn commit: trunk/buildroot/toolchain: external-toolchain gcc ulf at uclibc.org
2009-02-02 12:20 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-04 13:42 jacmet at uclibc.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k589ghdy.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.