On 05/08/2014 02:28 PM, Peter Maydell wrote:
On 8 May 2014 13:18, Andreas Färber <afaer...@suse.de> wrote:
Am 08.05.2014 10:26, schrieb Doug Kwan:
Add a new user mode target for little-endian PPC64.

Signed-off-by: Doug Kwan <dougk...@google.com>
---
  configure                              | 6 ++++++
  default-configs/ppc64el-linux-user.mak | 1 +
  2 files changed, 7 insertions(+)
  create mode 100644 default-configs/ppc64el-linux-user.mak

diff --git a/configure b/configure
index ac2fa15..ce44044 100755
--- a/configure
+++ b/configure
@@ -4917,6 +4917,12 @@ case "$target_name" in
      echo "TARGET_ABI32=y" >> $config_target_mak
      gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml 
power-spe.xml"
    ;;
+  ppc64el)
In SUSE's build system and everywhere I read people talking about it,
including your 2/3, it's called ppc64le. Why did you choose ppc64el?
In general we should follow what the kernel does, ie
the output of 'uname -m' (which hopefully coincides with
the gcc triplet name). What is that for this case?

$ uname -a
Linux shiraz-1 3.15.0-rc4-2-default+ #22 SMP Wed May 7 22:57:22 CEST 2014 ppc64le ppc64le ppc64le GNU/Linux

Thanks a lot for the catch. Just because Debian has it all backwards we don't have to as well ;).


Alex


Reply via email to