All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Definition of __sparc64__ in gcc
Date: Mon, 16 May 2016 12:23:08 +0000	[thread overview]
Message-ID: <5739BBAC.2030804@physik.fu-berlin.de> (raw)

Hello!

While looking at the FTBFS of Firefox, I noticed that Firefox, more
precisely ipc/chromium was checking for the definition of __sparc64__
to configure the code for sparc64 [1].

However, when looking at the actual gcc configuration dump, it's
apparent that __sparc64__ is actually not used but __arch64__:

root@landau:~# echo | gcc -E -dM - |grep __arch64__
#define __arch64__ 1
root@landau:~# echo | gcc -E -dM - |grep __sparc64__
root@landau:~#

Changing the header in Firefox's code base actually fixed this
particular issue with the firefox package on Debian.

Thus, my suspicion is that there might be other packages which are
incorrectly configured on sparc64 and consequently either failing
to build from source, crashing their testsuite or crashing during
operation.

A list of the possibly affected packages can be found in [2].

Any comments?

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug‚4449
> [2] https://codesearch.debian.net/results/__sparc64__/page_0

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

             reply	other threads:[~2016-05-16 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 12:23 John Paul Adrian Glaubitz [this message]
2016-05-16 15:08 ` Definition of __sparc64__ in gcc David Miller
2016-05-16 15:14 ` John Paul Adrian Glaubitz

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=5739BBAC.2030804@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=sparclinux@vger.kernel.org \
    /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.