This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: the GCC Project is a system vendor for GNU/Linux (Re: GCC vs GLIBC)


Yes, I totally agree with the following.  I would like
to add that the issue at hand is an entire GNU matter.
 There is no need to even involve the system vendors
(distributors) in the decision process. Hopefully the
GCC SC and the GLIBC SC can together decide what to
do, or, if coming to that, involve the FSF (RMS) to
make a decision (I assume you guys prefer to decide
among yourselves first...). 

It is best for the interests of all Linux users if the
relationship between GLIBC and GCC is identical among
all GNU/Linux distributions.  You don't want the gcc
mailing list to be flooded with questions like "why
the binary compiled with gcc 3.x I just built myself
does not run properly in distribution XXX with glibc
2.2.x?" Linux distributors can have many freedoms, but
this libgcc-glibc matter should be one freedom they
can do without.
Tighter integration between GLIBC and GCC (when viewed
from the external applications) is good for free
software.

Mr. Mitchell, Mr. Drepper, etc., whoever is willing to
set aside his own objections to find a way to
compromise or to yield to the other side, you are our
hero and the GNU/Linux community will salute you.


--- Fergus Henderson <fjh@cs.mu.oz.au> wrote:
> 
> Even if the GCC/GLIBC developers don't constitute a
> system vendor,
> I think it is very important for the future of free
> software... This
> requires some leadership.
> 
> If we deliberately leave it up to each individual
> system vendor to decide,
> then in the absense of leadership it is very likely
> that they will come to
> different decisions.  
> 
> So I think it would be a very good idea for the GCC
> and GLIBC developers
> to come to some agreement about recommended
> practices for system vendors
> 
> > We have given people more rope -- enough rope to
> fix some long-standing
> > problems.  The problem is that the people may
> choose to hang themselves
> > with the rope.
> 
> I don't think that metaphor properly captures the
> situation.
> It's not just about the system vendors choosing to
> hang themselves;
> the problem is that the system vendors may choose
> different solutions,
> each of which individually works fine, but which are
> incompatible,
> and the end result may be that *everyone* in the
> free software community
> suffers.
> 
> -- 
> Fergus Henderson <fjh@cs.mu.oz.au>  
> 


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]