From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9876] New: aarch64 support with gcc 4.8 toolchain
Date: Wed, 17 May 2017 11:34:55 +0000 [thread overview]
Message-ID: <bug-9876-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9876
Bug ID: 9876
Summary: aarch64 support with gcc 4.8 toolchain
Product: buildroot
Version: 2017.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
Hello,
I'm trying to compile for the aarch64 architecture using an external gcc 4.8
toolchain.
However I get the following error :
>>> toolchain-external-custom Installing to staging directory
/usr/bin/install -D -m 0755
/home/jpcartal/Dev/Ssd/buildroot/buildroot-2017.02/N30_test/build/toolchain-external-custom/toolchain-wrapper
/home/jpcartal/Dev/Ssd/buildroot/buildroot-2017.02/N30_test/host/usr/bin/toolchain-wrapper
aarch64-linux-gcc: error: unrecognized command line option '-mabi=lp64'
My understanding is that the mabi=lp64 option is only available on gcc 4.9.x
and newer.
Is there any solution available to compile for aarch64 architecture with a gcc
4.8.x toolchain ?
Thanks for your help.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-05-17 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 11:34 bugzilla at busybox.net [this message]
2017-05-17 12:32 ` [Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain bugzilla at busybox.net
2017-05-17 12:38 ` bugzilla at busybox.net
2017-05-25 13:16 ` bugzilla at busybox.net
2017-05-25 13:21 ` bugzilla at busybox.net
2017-05-25 13:32 ` Yann E. MORIN
2017-05-25 13:22 ` bugzilla at busybox.net
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=bug-9876-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.