On Sunday, November 2, 2003, at 06:41  AM, Valeriy E. Ushakov wrote:

> . if we want to keep our implementations for those libgcc functions we
>   will be linking our sources and libgcc sources, so we need to ensure
>   the licenses are compatible (e.g. no ad clause, etc).

As long as:

	* libgcc sources are not compiled into any other library

	* libgcc is linked into the resulting library or program
	  in order to support use of GCC

...then there should be no problem with the libgcc license (which is 
"GPL + exception when used with GCC").  Here is the exception clause:

  -- snip --
In addition to the permissions in the GNU General Public License, the
Free Software Foundation gives you unlimited permission to link the
compiled version of this file into combinations with other programs,
and to distribute those combinations without any restriction coming
from the use of this file.  (The General Public License restrictions
do apply in other respects; for example, they cover modification of
the file, and distribution when not linked into a combine
executable.)
  -- snip --

Now, I suppose the question is "what about a shared libgcc?"  This is 
where interpretation of "link the compiled version of this file into 
combinations with other problems" comes into play.  Perhaps this should 
be clarified with the GCC steering committee / FSF.

         -- Jason R. Thorpe <thorpej@wasabisystems.com>