Re: __i386__ and cpp

[hjl at lucon dot org (H.J. Lu)]

> 
> 
>   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
> directory?
> 

Assuming script does work, I have a version which I have verified by
building XFree86 3.3.2,  I suggest we install it only if it is
asked for. By that, I mean prefix == /usr and it is on Linux. We can
add a file "install.cpp" in config. Linux can adds it to Makefile.
Then it will check if prefix == /usr before installing it. I prefer
to put the script in /usr/bin and make a symlink to /lib. I can provide
a whole patch for it.


-- 
H.J. Lu (hjl@gnu.org)