This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Removal of VAX/VMS support
Hi Ben, Hi Douglas,
>> Gcc has abandoned VAX/VMS. Is there any objection to removing it
>> from binutils? EVAX aka AlphaVMS support would, of course, remain.
> This raising an interesting question. I'm not sure if binutils has
> adopted a policy of target shooting yet -- perhaps it would make sense
> for ports that are clearly deprecated (ie. no GCC or GDB support any
> longer) and are bitrotting?
Yeah - I have been thinking about it.
I think you are right. There is little point in providing tools for
platforms that no longer exist. We must be careful however not to
exclude platforms just because they do not have a gcc/gdb port. There
are quite a few targets which do not use the big boys of the compiler
world (ie gcc and gdb) but which still use these tools.
So - what about a patch like this ?
Any objections ?
Cheers
Nick
2003-07-30 Nick Clifton <nickc@redhat.com>
* config.bfd: Check for and fail on encountering obsolete
configurations unless --enable-obsolete is used.
Index: bfd/config.bfd
===================================================================
RCS file: /cvs/src/src/bfd/config.bfd,v
retrieving revision 1.143
diff -c -3 -p -r1.143 config.bfd
*** bfd/config.bfd 17 Jul 2003 14:27:38 -0000 1.143
--- bfd/config.bfd 30 Jul 2003 15:47:21 -0000
*************** targ64_selvecs=
*** 29,34 ****
--- 29,49 ----
targ_cflags=
targ_underscore=no
+ # Catch obsolete configurations.
+ case $targ in
+ m88k-*-* \
+ | vax-*-vms* \
+ )
+ if test "x$enable_obsolete" != xyes; then
+ echo "*** Configuration $targ is obsolete." >&2
+ echo "*** Specify --enable-obsolete to build it anyway." >&2
+ echo "*** Support will be REMOVED in the next major release of BINUTILS," >&2
+ echo "*** unless a maintainer comes forward." >&2
+ exit 1
+ fi;;
+ esac
+
+
targ_cpu=`echo $targ | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'`
case "${targ_cpu}" in
alpha*) targ_archs=bfd_alpha_arch ;;