From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7664 invoked by alias); 24 May 2003 14:23:08 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 7589 invoked from network); 24 May 2003 14:23:08 -0000 Received: from unknown (HELO nile.gnat.com) (205.232.38.5) by sources.redhat.com with SMTP; 24 May 2003 14:23:08 -0000 Received: by nile.gnat.com (Postfix, from userid 338) id BAC9BF2D64; Sat, 24 May 2003 10:23:07 -0400 (EDT) To: dj@redhat.com, neroden@twcny.rr.com Subject: Re: Libiberty license roundup (questions/potential problems) Cc: gcc@gcc.gnu.org Message-Id: <20030524142307.BAC9BF2D64@nile.gnat.com> Date: Sat, 24 May 2003 14:59:00 -0000 From: dewar@gnat.com (Robert Dewar) X-SW-Source: 2003-05/txt/msg02193.txt.bz2 > Ah, so libiberty is always statically linked, and only individual .o > files are linked with any particular program, so source files under > different licenses aren't unmanagably comingled? We should add a note > somewhere to the effect that it has to remain this way. :-) A little note here is that GNAT contains built in mechanisms (and an explicit pragma License) to ensure against invalid mixing of licenses. This is activated by default by the -gnatg switch used to compile GNAT sources. We have found it quite useful in avoiding any mistakes (in particular, a file with the exception clause is not allowed to WITH a file without the clause.