Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Lossage do to #ifndef __ASSEMBLY__ in mipsregs.h
Date: Thu, 22 Jan 2004 16:02:26 -0800	[thread overview]
Message-ID: <40106492.6050400@avtrex.com> (raw)
In-Reply-To: <20040122235619.GR23173@rembrandt.csv.ica.uni-stuttgart.de>

Thiemo Seufer wrote:

>David Daney wrote:
>  
>
>>I am using gcc 3.3.1 to compile the linux_2_4 kernel obtained from cvs a 
>>couple of days ago.
>>    
>>
>[snip]
>  
>
>>-#endif /* !defined (_LANGUAGE_ASSEMBLY) */
>>+#endif /* !__ASSEMBLY__ */
>>
>>#endif /* _ASM_MIPSREGS_H */
>>
>>Why the change?
>>    
>>
>
>__ASSEMBLY__ is defined by the Linux build system in order to have a
>compiler independent test.
>
I am starting to understand this.

>
>  
>
>>I will fix my local mipsregs.h so that I can continue, but it seems like 
>>the sources in CVS should be changed to allow gcc 3.3.1 to work.
>>    
>>
>
>It works here (for my configs). Your linux tree seems to be broken.
>
>
>Thiemo
>  
>
I am porting my BSP from 2.4.18 to the latest, and it seems I may have 
some Makefile incompatibility.  So I withdraw my criticism of 
defined(__ASSEMBLY__).

David Daney

      reply	other threads:[~2004-01-23  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 23:19 Lossage do to #ifndef __ASSEMBLY__ in mipsregs.h David Daney
2004-01-22 23:56 ` Thiemo Seufer
2004-01-23  0:02   ` David Daney [this message]

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=40106492.6050400@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.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