From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8138 invoked by alias); 18 Dec 2001 20:16:37 -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 8093 invoked from network); 18 Dec 2001 20:16:36 -0000 Received: from unknown (HELO cc730106-b.taylor1.mi.home.com) (24.13.63.84) by sources.redhat.com with SMTP; 18 Dec 2001 20:16:36 -0000 Received: from localhost (jsturm@localhost) by cc730106-b.taylor1.mi.home.com (8.9.3/8.9.3) with ESMTP id PAA11437; Tue, 18 Dec 2001 15:16:40 -0500 X-Authentication-Warning: mars.deadcafe.org: jsturm owned process doing -bs Date: Tue, 18 Dec 2001 12:45:00 -0000 From: Jeff Sturm X-Sender: jsturm@mars.deadcafe.org To: Arnaud Charlet cc: gcc@gcc.gnu.org Subject: Re: Use of -fPIC on Tru64 In-Reply-To: <20011218001347.B6541@dublin.int.act-europe.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-12/txt/msg01005.txt.bz2 On Tue, 18 Dec 2001, Arnaud Charlet wrote: > I appreciate and understand the motivation on systems such as Linux, but > Tru64 is very different in this respect, and I still haven't seen a good > argument to enable -fPIC on Tru64 for libgcc. Perhaps. But I haven't seen a good reason to disable it either. Why make the build system any more complicated than it need be, for goodness sake? Jeff