Re: Shared Libraries and naming conventions
> > You have to use the GNU c compiler with glibc2. Thats unacceptable to
> > all the other compiler vendors. Things like Compaq releasing their own
> > optimising compiler go completely up the spout because of this. So it
> > favours one vendor. The vendor in question may not have caused it, but
> > its a clear and large problem.
> For those of us not aware of the details, could you please explain how
> this happens?
/* Copyright (C) 1993, 1997, 1998 Free Software Foundation, Inc.
This file is part of the GNU IO Library.
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2, or (at
your option) any later version.
This library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with this library; see the file COPYING. If not, write to
the Free Software Foundation, 59 Temple Place - Suite 330, Boston,
MA 02111-1307, USA.
As a special exception, if you link this library with files
compiled with a GNU compiler to produce an executable, this does
not cause the resulting executable to be covered by the GNU General
Public License. This exception does not however invalidate any
other reasons why the executable file might be covered by the GNU
General Public License. */
And note a -GNU- compiler. Not even another GPL compiler. You can't even
use it with a competing free software product to produce non free binaries.