From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3 v2] toolchain/external: add Linaro ARM 2014.11 ARMv7 EABIhf
Date: Sun, 29 Mar 2015 13:11:43 +0200 [thread overview]
Message-ID: <20150329131143.2288634c@free-electrons.com> (raw)
In-Reply-To: <09383bf10969ac4b1705180abd33576e52b5a3e6.1427556250.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sat, 28 Mar 2015 16:27:10 +0100, Yann E. MORIN wrote:
> - it is available only for x86_64 hosts
>
> - the toolchain is split in three parts:
> - the main archive, with the tools and a minimalist sysroot with
> just the strictly required stuff (e.g. just the C library and most
> libs as static libs, i.e. no shared libs but libc.so)
> - a secondary archive, with the complete sysroot , duplicationg most
> previously existing files in the minimal sysroot, above
> - a tertiary archive, with the 'runtime' content (whatever that
> could mean...); that one seems completely unnecessary for
> Buildroot.
>
> - the sys/types.h headers from the main sysroot is correct, while the
> one from the secondary archive (thus overwriting the main one) is
> broken, as it removes the definition of caddr_t (why? WHY?).
Can you report this bug to the Linaro folks?
>
> - there's a stray backup file for libstdc++
I already reported the stray backup file issue, but as part of my
original bug report. Maybe we should report it as a separate bug.
> +config BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM_2014_11
> + bool "Linaro arm 2014.11"
For Linaro toolchains, we've stopped adding version-specific Config.in
options. At any given time, we support only one Linaro toolchain, under
the option BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM.
> +# The Linaro 2014.11 toolchains are split in two parts:
> +# - the main archive, contains compiler and other tools, plus a minimal
No comma between 'archive' and 'contains'.
> +# sysroot without a lot of share dlibs (e.g. libstdc++.so)
> +# - a secondrary archive with another part of the sysroot (in that both
secondary
> +# the intersection and exclusion are non-empty)
"in that both the intersection and exclusion are non-empty" ?!?
> +# The standard package infra handles the main archive, and we use a
> +# post-extract hook to extract the secondary, sysroot archive
> +define TOOLCHAIN_EXTERNAL_LINARO_2014_11_EXTRACT_SYSROOT
> + $(call suitable-extractor,$(TOOLCHAIN_EXTERNAL_EXTRA_DOWNLOADS)) $(DL_DIR)/$(TOOLCHAIN_EXTERNAL_EXTRA_DOWNLOADS) | \
> + $(TAR) $(TAR_STRIP_COMPONENTS)=1 --hard-dereference -C $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/libc $(TAR_OPTIONS) -
> +endef
> +# The sysroot archive is kinda broken, keep the pieces together...
Maybe be more specific here about what is being done rather than just
"let's fix the breakage".
> +define TOOLCHAIN_EXTERNAL_LINARO_2014_11_FIX_TYPES_H
> + $(SED) 's/\(typedef __daddr_t daddr_t;\)/\1\ntypedef __caddr_t caddr_t;/' \
> + $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/libc/usr/include/sys/types.h
> +endef
> +define TOOLCHAIN_EXTERNAL_LINARO_2014_11_CLEAN_UP_32
> + rm -f $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/libc/usr/lib/libgcc_s.so.1.backup
> +endef
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-29 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 15:27 [Buildroot] [PATCH 0/3 v2] toolchain/external: add Linaro 2014.11 (branch yem/toolchain-linaro-2014.11) Yann E. MORIN
2015-03-28 15:27 ` [Buildroot] [PATCH 1/3 v2] toolchain/external: add Linaro ARM 2014.11 ARMv7 EABIhf Yann E. MORIN
2015-03-29 11:11 ` Thomas Petazzoni [this message]
2015-03-29 11:23 ` Yann E. MORIN
2015-03-28 15:27 ` [Buildroot] [PATCH 2/3 v2] toolchain/external: add Linaro ARM BE " Yann E. MORIN
2015-03-28 15:27 ` [Buildroot] [PATCH 3/3 v2] toolchain/external: add Linaro AArch64 2014.11 Yann E. MORIN
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=20150329131143.2288634c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox