On 11/07/2014 12:19 PM, Andrew Haley wrote:
On 11/07/2014 06:10 PM, Christian Thalinger wrote:
On Nov 7, 2014, at 9:55 AM, Andrew Haley <a...@redhat.com> wrote:
On 11/07/2014 05:42 PM, Christian Thalinger wrote:
On Nov 7, 2014, at 9:21 AM, Andrew Haley <a...@redhat.com> wrote:
The first patch: top-level build machinery changes.
http://cr.openjdk.java.net/~aph/8064357-rev-1/
<http://cr.openjdk.java.net/~aph/8064357-rev-1/>
common/autoconf/flags.m4
+ aarch64)
+ ZERO_ARCHFLAG=""
+ ;;
Why is this required on aarch64 but not all the other architectures?
I think it's because GCC rejects "-m64”.
That’s interesting. I thought -m<archbits> is some kind of common
flag that works on all architectures.
No, all the "-m" stuff is target-dependent.
Can someone verify this?
mustang-01:~ $ gcc -m64 hello.c
gcc: error: unrecognized command line option '-m64'
mustang-01:~ $ gcc --version
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-16)
Also the man page lists -m64 under only specific targets.
--
- DML
