This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: VAX Ultrix bootstrap failure with gcc-2.96
- To: bkorb at sco dot COM
- Subject: Re: VAX Ultrix bootstrap failure with gcc-2.96
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Fri, 16 Jun 2000 11:52:14 -0400 (EDT)
- Cc: dave at hiauly1 dot hia dot nrc dot ca, gcc-patches at gcc dot gnu dot org
> From: Bruce Korb <bkorb@sco.COM>
>
> "Kaveh R. Ghazi" wrote:
> > > I confess to being unclear whether we are talking about
> > > getting the GCC built or compiling end user programs.
> >
> > We are talking about compiling end user programs.
>
> I distinguish because during the build of GCC, you can
> define symbols like GETGROUPS_T any way you want.
> You cannot insert such symbols into system headers without
> polluting name space and, in fact, conflicting with a symbol
> that configure will often define for its clients (us included :).
Yes, I understand the namespace pollution issue. I think the solution
that Dave is working on will not leave GETGROUPS_T in unistd.h, but I
have yet to actually see it. :-)
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions