Patch to make trunk compile on m68k-next-nextstep3 with 3 = 3.2

[Jeffrey A Law]

  In message < 199809281658.JAA05316@aldrington.ppp.cs.sfu.ca >you write:
  > Maybe I wasn't clear. I was saying that we could require that 3.2 users
  > upgrade their assembler (and not that they should upgrade their entire
  > OS). Since the assembler is free software, they can get the version from
  > 3.3 (or even compile it from the source for last NeXT OS, 4.2). EGCS
  > routinely has requirements about what assembler people can be using (see
  > the FAQ), so I didn't see this as treating NEXTSTEP differently from
  > other operating systems.
Oh.  Then how easy is it to get that new assembler?

Ie, I'm sitting here with my 3.2 box, I don't have 3.3 or 4.2 handy, and from
what I can tell the binutils releases do not support my target.  So how do I
upgrade?  Is there some source or binaries I can ftp?  If so, where are they?
Can I call up NeXT to get the code?  If so, is there something specific I
should ask for?

  > ... in another message, Jeff adds:
  > > Instead of having different configs for 3.2 vs 3.3, maybe we should
  > > be testing for gas functionality and enabling the new code only when
  > > we detect the specific gas feature that we need.
  > 
  > Well, that's fine too. NeXT's Assemblers prior to 3.3 don't support the
  > `.section' or `.zerofill' directives, so that's what we'd test (we only
  > use the former right now).  NeXT's `.section' directive is likely
  > different from other GNU assemblers, and looks like this:
Checking would be fairly simple.  We just cobble up a testfile, and try to
assemble it.  If gas chokes, then we don't have a new enough assembler.

What gets tricky is once we know our assembler is lame, how do we make things
work?  Presumably we can disable the new code via some well place ifdefs?

jeff