All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [GIT PULL] unify sparc header files
Date: Sat, 05 Jul 2008 23:03:48 +0000	[thread overview]
Message-ID: <20080705230348.GA18213@uranus.ravnborg.org> (raw)
In-Reply-To: <20080628220235.GA3169@uranus.ravnborg.org>

On Sat, Jul 05, 2008 at 10:55:10PM +0200, Sam Ravnborg wrote:
> > 
> > So this looks correct except that we include the wrong header file.
> > So the test:
> > #if defined(__sparc__) && defined(__arch64__)
> > 
> > is the bad one.
> ....
> > 
> > We can fix the -Usparc64 for the vmlinux.lds file if the right check is:
> > #if defined(__sparc__) && defined(sparc64)
> 
> I think this is the right way to go so I have locally
> committed the following patch.
Hmm, I was fooled by something else. My sparc64 gcc does NOT
define the sparc64 symbol.
I defines:
__sparc_v9__
and
__arch64__

to say this is sparc64.

So I really need the output of:
touch foo.c; cpp -dM foo.c

to select the right combination of options before I can
proceed.

	Sam

  parent reply	other threads:[~2008-07-05 23:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-28 22:02 [GIT PULL] unify sparc header files Sam Ravnborg
2008-06-28 22:29 ` Sam Ravnborg
2008-06-29  6:27 ` Sam Ravnborg
2008-06-30 19:49 ` Adrian Bunk
2008-07-03  7:50 ` David Miller
2008-07-03  8:12 ` David Miller
2008-07-03 10:01 ` David Miller
2008-07-03 13:45 ` Sam Ravnborg
2008-07-03 20:02 ` Adrian Bunk
2008-07-03 20:15 ` David Miller
2008-07-03 20:29 ` Sam Ravnborg
2008-07-03 20:29 ` Sam Ravnborg
2008-07-04 21:10 ` Sam Ravnborg
2008-07-05 20:55 ` Sam Ravnborg
2008-07-05 23:03 ` Sam Ravnborg [this message]
2008-07-06  1:56 ` David Miller
2008-07-06  1:57 ` David Miller
2008-07-06 20:06 ` Sam Ravnborg
2008-07-07  1:18 ` David Miller
2008-07-07  7:46 ` Sam Ravnborg
2008-07-07  7:54 ` David Miller
2008-07-07 20:54 ` Sam Ravnborg
2008-07-08  9:33 ` David Miller
2008-07-09  4:27 ` Sam Ravnborg
2008-07-15  5:58 ` David Miller

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=20080705230348.GA18213@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --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.