This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Friday, December 10, 2010 05:43:47 Joseph S. Myers wrote: > 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. seems like gcc_GAS_VERSION_GTE_IFELSE should do what i want. these checks ok to put into gcc/config.gcc ? that's where all the blackfin-specific logic is found currently, but doesnt seem like any other targets run any sort of tests in that file -- they seem to be in configure.ac. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |