From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3462 invoked by alias); 28 Apr 2004 20:37:07 -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 3455 invoked from network); 28 Apr 2004 20:37:06 -0000 Received: from unknown (HELO mailout.TechFak.Uni-Bielefeld.DE) (129.70.136.245) by sources.redhat.com with SMTP; 28 Apr 2004 20:37:06 -0000 Received: from xayide.TechFak.Uni-Bielefeld.DE.TechFak.Uni-Bielefeld.DE (xayide.TechFak.Uni-Bielefeld.DE [129.70.137.35]) by momotombo.TechFak.Uni-Bielefeld.DE (8.12.11/8.12.11/TechFak/2004/02/24/sjaenick) with ESMTP id i3SKb5pI004267; Wed, 28 Apr 2004 22:37:06 +0200 (MEST) To: Jim Wilson Cc: Karl Vogel , gcc@gcc.gnu.org Subject: Re: HP/Compaq Tru64 linker semantics References: <6DED3619289CD311BCEB00508B8E133601A68654@nt-server2.antwerp.seagha.com> <40900DC4.1080504@specifixinc.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Rainer Orth Date: Wed, 28 Apr 2004 22:40:00 -0000 In-Reply-To: Jim Wilson's message of "Wed, 28 Apr 2004 13:02:12 -0700" Message-ID: X-SW-Source: 2004-04/txt/msg01341.txt.bz2 Jim Wilson writes: > Karl Vogel wrote: > > I was wondering what the general opinion is.. follow GNU ld as close as > > possible? Or follow the standard way of the platform?! > > I would suggest that we should follow what the platform does. People > porting to Tru64 will expect gcc to work the same way as the native > compiler, and if it doesn't, then packages with builtin Tru64 > assumptions may fail. Fully agreed, even though this case of local vs. vendor supplied libdb has bitten me as well. Even though this default (searching for all shared libraries before the static ones) is highly unusual on Unix systems, we should follow the vendor here so GCC users don't get another surprise when using GCC. One caveat, though: currently one cannot pass -oldstyle_liblookup through collect2 to ld, which is quite tedious. This has been reported already http://gcc.gnu.org/ml/gcc-bugs/1999-09n/msg00912.html and there's a PR for this, other/1963, but it is unfixed an has been (erroneously, I think) been closed as a duplicate of PR other/5762. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Faculty of Technology, Bielefeld University