From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3783 invoked by alias); 10 Dec 2010 10:45:15 -0000 Received: (qmail 3518 invoked by uid 22791); 10 Dec 2010 10:44:55 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 10 Dec 2010 10:44:09 +0000 Received: (qmail 3375 invoked from network); 10 Dec 2010 10:43:49 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 10 Dec 2010 10:43:49 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.72) (envelope-from ) id 1PR0S3-0002k0-R4; Fri, 10 Dec 2010 10:43:47 +0000 Date: Fri, 10 Dec 2010 10:45:00 -0000 From: "Joseph S. Myers" To: Mike Frysinger cc: binutils@sourceware.org, toolchain-devel@blackfin.uclinux.org Subject: Re: [PATCH] bfd/ld: handle ABI prefixes in version scripts In-Reply-To: <201012092252.25628.vapier@gentoo.org> Message-ID: References: <201007061601.24599.vapier@gentoo.org> <1291928188-30119-1-git-send-email-vapier@gentoo.org> <201012092252.25628.vapier@gentoo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2010-12/txt/msg00385.txt.bz2 On Thu, 9 Dec 2010, Mike Frysinger wrote: > > So it would seem you need to coordinate this change in some way with GCC, > > if I understand it correctly - possibly making GCC 4.6 for Blackfin > > require a new linker and replacing the duplicate version script with one > > just defining the two Blackfin-specific symbols. That doesn't solve the > > problem with old GCC and new linkers, though you could add a configure > > test to 4.3/4.4/4.5 release branches to reject new linkers for Blackfin. > > are there any examples of binutils version checking that i can look at basing > the work on ? There are lots of assembler checks that deal with various combinations of checking a version number (possibly for a unified tree build) and checking for features; see gcc_GAS_CHECK_FEATURE. -- Joseph S. Myers joseph@codesourcery.com