linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, jdl@jdl.com
Subject: Re: DTC/dts modifications
Date: Tue, 2 May 2006 00:00:35 +0200	[thread overview]
Message-ID: <20060501220034.GA22651@iram.es> (raw)
In-Reply-To: <00CD15B8-F448-4985-8EEC-3BBF61C0110B@kernel.crashing.org>

On Mon, May 01, 2006 at 03:28:34PM -0500, Kumar Gala wrote:
> 
> Cool, here's an invocation that seems to work well.  Not sure what  
> causes linux = 1 (thus I need the -U linux).  Also address the line  
> information that is normally spit out.
> 
> cpp -U linux -P -x assembler-with-cpp foo.dts

Try to add the -undef parameter:

`-undef'
     Do not predefine any system-specific or GCC-specific macros.  The
     standard predefined macros remain defined.

On this machine, the number of lines from:

cpp -dM -x assembler-with-cpp /dev/null

drops from 83 (among which linux, unix, PPC, and powerpc do not start
with underscores) to 5(!) when I add the -undef option. The only ones
left are:

#define __linux__ 1
#define __STDC_HOSTED__ 1
#define __unix__ 1
#define __gnu_linux__ 1
#define __ASSEMBLER__ 1

but at least they all have leading and trailing double underscores.

	Regards,
	Gabriel

  parent reply	other threads:[~2006-05-01 22:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29 16:00 DTC/dts modifications Kumar Gala
2006-05-01 19:33 ` Jon Loeliger
2006-05-01 19:39   ` Kumar Gala
2006-05-01 19:45     ` Jon Loeliger
2006-05-01 19:52       ` Kumar Gala
2006-05-01 20:07         ` Kim Phillips
2006-05-01 20:28           ` Kumar Gala
2006-05-01 21:26             ` Segher Boessenkool
2006-05-01 22:00             ` Gabriel Paubert [this message]
2006-05-01 22:59             ` Andreas Schwab
2006-05-01 23:34         ` Benjamin Herrenschmidt
2006-05-02  0:17           ` Segher Boessenkool
2006-05-01 22:14     ` Paul Mackerras

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=20060501220034.GA22651@iram.es \
    --to=paubert@iram.es \
    --cc=galak@kernel.crashing.org \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).