Possible bug in 'ln -s target dir' check code --

I am probably incorrectly interpreting the autoconf code that checks whether or not 'ln -s target dir' works.  It seems the check code is satisfied if


  mkdir a

  touch b

  ln -s b a


works without aborting.  On Ubuntu this does create a 'b' symlink in 'a' but that symlink is an infinite a/b->a/b.  In fact I think the only way to succeed is to use


  ln -s $PWD/b a


i.e., the ln app should be a heck of a lot smarter.


--  Thanks,

--    Paul Townsend