This is the mail archive of the
mailing list for the GCC project.
Re: __i386__ and cpp
- To: Jeffrey A Law <law at cygnus dot com>
- Subject: Re: __i386__ and cpp
- From: Christopher Seawood <cls at seawood dot org>
- Date: Tue, 3 Mar 1998 09:50:59 -0800 (PST)
- cc: "H.J. Lu" <hjl at lucon dot org>, egcs at cygnus dot com
- Reply-To: Christopher Seawood <cls at seawood dot org>
On Tue, 3 Mar 1998, Jeffrey A Law wrote:
> In message <m0y9Xl6-00058fC@ocean.lucon.org>you write:
> > >
> > >
> > > In message <m0y3T4L-0004ecC@ocean.lucon.org>you write:
> > > > __i386__ has been dropped from cpp in 1996. It
> > > > causes a problem for imake since it calls cpp
> > > > directly. It would be nice for egcs 1.0.2 to
> > > > define __i386__ on all x86 platforms.
> > > Actually, it looks like Imake is involing /lib/cpp, which is
> > > a symlink into the gcc-2.7 gcc-lib directory on my linux boxes.
> > >
> > > So how exactly are folks getting the egcs cpp when they're using
> > > imake?
> > >
> > How about people who uses egcs 1.0.1 as their only compiler :-)?
> > They will make such a link.
> So, do we just provide the script in the source dir for the user to
> install, or do we actually arrange to install it in the library
Is this script really needed? Are there any other cases of programs
checking for i386 via cpp? If imake is the only one, why go thru the
trouble of the script for one specific case?
>From the discussions that I've seen so far, the problem appears to be more
with the imake source than gcc. I've rarely seen imake invoked directly.
Wouldn't it be much easier to edit xmkmf and add -Di386 to the args list?
Also, I'm not sure if it's been mentioned, but when XFree86 is recompiled
with egcs, the problem goes away as imake defines -Di386 itself.