From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v2 3/5] aarch64: ilp32: add ilp32 compiler and linker flags
Date: Fri, 10 Apr 2015 09:36:45 -0300 [thread overview]
Message-ID: <5527C3DD.6050401@zacarias.com.ar> (raw)
In-Reply-To: <1426672192-21041-4-git-send-email-bamvor.zhangjian@huawei.com>
On 03/18/2015 06:49 AM, Zhang Jian(Bamvor) wrote:
> +ifeq ($(BR2_AARCH64_ILP32)$(BR2_aarch64),yy)
> +TARGET_ABI += -mabi=ilp32 -Xlinker -maarch64linux32
> +endif
> +
> +ifeq ($(BR2_AARCH64_ILP32)$(BR2_aarch64_be),yy)
> +TARGET_ABI += -mabi=ilp32 -Xlinker -EB -Xlinker -maarch64linux32b
> +endif
Ok, but...
> -TARGET_LDFLAGS = $(call qstrip,$(BR2_TARGET_LDFLAGS))
> +TARGET_LDFLAGS = $(call qstrip,$(BR2_TARGET_LDFLAGS)) $(TARGET_ABI)
...you're throwing -mabi at ld, i don't think ld understands that and
would probably break other architectures like PowerPC e500.
Regards.
next prev parent reply other threads:[~2015-04-10 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 9:49 [Buildroot] [RFC PATCH v2 0/5] Add ILP32 support in aarch64 Zhang Jian
2015-03-18 9:49 ` [Buildroot] [RFC PATCH v2 1/5] aarch64: add big endian(aarch64_be) support Zhang Jian
2015-04-10 12:24 ` Gustavo Zacarias
2015-03-18 9:49 ` [Buildroot] [RFC PATCH v2 2/5] aarch64: ilp32: handle special file name Zhang Jian
2015-04-10 12:35 ` Gustavo Zacarias
2015-04-13 10:12 ` Bamvor Jian Zhang
2015-04-13 10:16 ` Bamvor Jian Zhang
2015-03-18 9:49 ` [Buildroot] [RFC PATCH v2 3/5] aarch64: ilp32: add ilp32 compiler and linker flags Zhang Jian
2015-04-10 12:36 ` Gustavo Zacarias [this message]
2015-04-13 10:06 ` Bamvor Jian Zhang
2015-03-18 9:49 ` [Buildroot] [RFC PATCH v2 4/5] aarch64: ilp32: add ilp32 build config Zhang Jian
2015-04-10 12:46 ` Gustavo Zacarias
2015-04-13 10:02 ` Bamvor Jian Zhang
2015-03-18 9:49 ` [Buildroot] [RFC PATCH v2 5/5] aarch64: ilp32 defconfig examples Zhang Jian
2015-04-10 9:16 ` [Buildroot] [RFC PATCH v2 0/5] Add ILP32 support in aarch64 Bamvor Jian Zhang
2015-07-12 16:45 ` Thomas Petazzoni
2015-07-13 2:21 ` Zhangjian
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=5527C3DD.6050401@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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