New: aarch64 support with gcc 4.8 toolchain
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 :
Quoted 1 line
Quoted 1 line
Quoted 1 line
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.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
https://bugs.busybox.net/show_bug.cgi?id=9876
Peter Korsgaard <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Peter Korsgaard <[email protected]> --- (In reply to Jean-pierre Cartal from comment #0)
You could remove the lp64 line from arch/Config.in.arm, but considering how old gcc 4.8 is compared to aarch64, does it really make sense to use such an old toolchain?
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9876
--- Comment #2 from Jean-pierre Cartal <[email protected]> --- Hi,
Thanks for your help.
Unfortunately we don't have much choice regarding the toolchain version as it is currently provided by a 3rd party. We might try to use buildroot toolchain since that would indeed solve our issue. Thanks for the tip on where to remove the lp64 option.
As a side note, wouldn't it make sense to disable aarch64 compilation with external gcc toolchains older than 4.9.x since it will not work ?
Regards.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9876
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|ASSIGNED |RESOLVED--- Comment #3 from Thomas Petazzoni <[email protected]> --- For custom external toolchains, we simply let the user specify which gcc version the toolchain uses, and check that at the beginning of the build. We don't try to prevent the user from using an unsupported gcc version depending on the selected architecture, and I don't think we want to go down this route. Especially since custom external toolchain quite often use vendor-specific gcc versions that are patched to support additional features/processors, and unnecessarily restricting the set of gcc versions to use would not be very nice. For example, a patched gcc 4.8 could very well support lp64.
So I don't think we'll try to solve this problem.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9876
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #4 from Yann E. MORIN <[email protected]> --- We don't try to prevent the user from using an unsupported gcc version depending on the selected architecture, and I don't think we want to go down this route.
So I don't think we'll try to solve this problem.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9876
--- Comment #5 from Yann E. MORIN <[email protected]> ---
Quoted 4 lines
We don't try to prevent the user from using an unsupported gcc version depending on the selected architecture, and I don't think we want to go down this route.
So I don't think we'll try to solve this problem.
Agreed.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9876] aarch64 support with gcc 4.8 toolchain
In reply to bugzilla at busybox.netOn 2017-05-25 13:21 +0000, bugzilla at busybox.net spake thusly:
Quoted 8 lines
https://bugs.busybox.net/show_bug.cgi?id=9876
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
Quoted 6 lines
--- Comment #4 from Yann E. MORIN <[email protected]> --- We don't try to prevent the user from using an unsupported gcc version depending on the selected architecture, and I don't think we want to go down this route.
So I don't think we'll try to solve this problem.
Woops... It seems I was not fast enough to cancel my reply after I accidentally hit "apply changes" in the tracker. Sorry...
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'