From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1961 invoked by alias); 9 Jul 2009 13:43:27 -0000 Received: (qmail 1951 invoked by uid 22791); 9 Jul 2009 13:43:26 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Jul 2009 13:43:21 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 5BF45108D2; Thu, 9 Jul 2009 13:43:19 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 42877108D0; Thu, 9 Jul 2009 13:43:19 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MOtuA-00029m-LM; Thu, 09 Jul 2009 09:43:18 -0400 Date: Thu, 09 Jul 2009 13:43:00 -0000 From: Daniel Jacobowitz To: Basile STARYNKEVITCH Cc: gcc@gcc.gnu.org Subject: Re: libiberty should be a shared library when cc1 has plugin enabled. Message-ID: <20090709134318.GA8237@caradoc.them.org> Mail-Followup-To: Basile STARYNKEVITCH , gcc@gcc.gnu.org References: <20090709084949.GA27192@hector.lesours> <20090709125004.GA4445@caradoc.them.org> <4A55EA0D.2080509@starynkevitch.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A55EA0D.2080509@starynkevitch.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00167.txt.bz2 On Thu, Jul 09, 2009 at 03:01:01PM +0200, Basile STARYNKEVITCH wrote: > In simpler words, *.so have to be compiled with -fPIC, and libiberty > is not compiled with -fPIC. We build a PIC libiberty already. While Ralf's point about static data is valid, the functions likely to be in libiberty on any platform supporting plugins should not suffer from this problem. If you're concerned about it, then build a subset. I've considered a separation of libiberty into replacements and utilities, anyway. -- Daniel Jacobowitz CodeSourcery