public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "J.H.M.Dassen" <jdassen@wi.leidenuniv.nl>
To: nkbj@image.dk, egcs@cygnus.com
Subject: Re: CPP_PREDEFINES
Date: Thu, 24 Sep 1998 02:37:00 -0000	[thread overview]
Message-ID: <199809240634.IAA13154@ultra5.wi.leidenuniv.nl> (raw)
In-Reply-To: <6ub5c5$9g4$1@noc.wi.leidenuniv.nl>

[Courtesy copy of Usenet posting]
J.H.M. Dassen <jdassen@wi.LeidenUniv.nl> wrote:
>Dejan Muhamedagic <dejan@yunix.co.yu> wrote:
>>imake doesn't work anymore because it depends on the architecture as well
>>as the platform.
>
>This is fixed in egcs ( http://egcs.cygnus.com ).

It has been pointed out to me that this isn't really true. An earlier
version of egcs (1.0.3 IIRC), had fixed this, but the __i386__ has been
removed again in 1.1.

In packaging 1.1 for Debian, I noticed a similar problem for alpha:
gcc/config/alpha/linux.h doesn't put -D__alpha in CPP_PREDEFINES .

While there may be valid reasons for cleaning out CPP_PREDEFINES, I think
this issue should be addressed in the egcs FAQ, and a suggestion for a
workaround for imake be included.

Ray
-- 
LEADERSHIP  A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch 
it'll be someone else's bones which go crack and not their own.       
- The Hipcrime Vocab by Chad C. Mulligan    

       reply	other threads:[~1998-09-24  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3608F893.1CFB@yunix.co.yu>
     [not found] ` <6ub5c5$9g4$1@noc.wi.leidenuniv.nl>
1998-09-24  2:37   ` J.H.M.Dassen [this message]
1998-09-24 14:32 CPP_PREDEFINES Steve Snyder

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=199809240634.IAA13154@ultra5.wi.leidenuniv.nl \
    --to=jdassen@wi.leidenuniv.nl \
    --cc=egcs@cygnus.com \
    --cc=nkbj@image.dk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).