From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15579 invoked by alias); 28 Apr 2004 20:01:55 -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 15571 invoked from network); 28 Apr 2004 20:01:52 -0000 Received: from unknown (HELO mta6.wss.scd.yahoo.com) (66.218.85.37) by sources.redhat.com with SMTP; 28 Apr 2004 20:01:52 -0000 Received: from specifixinc.com (24.7.123.142) by mta6.wss.scd.yahoo.com (7.0.016) (authenticated as jim@tuliptree.org) id 4072403F00CA304D; Wed, 28 Apr 2004 13:01:47 -0700 Message-ID: <40900DC4.1080504@specifixinc.com> Date: Wed, 28 Apr 2004 21:56:00 -0000 From: Jim Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716 MIME-Version: 1.0 To: Karl Vogel CC: gcc@gcc.gnu.org Subject: Re: HP/Compaq Tru64 linker semantics References: <6DED3619289CD311BCEB00508B8E133601A68654@nt-server2.antwerp.seagha.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg01338.txt.bz2 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. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com