PATCH for libiberty when NOT using --enable-shared

[Jeffrey A Law]

  In message < 13666.38256.637388.842113@slsvhmt >you write:
  > Jeff, the recent changes to libiberty introduced a default for
  > enable_shared which is different from what the toplevel scripts are
  > using.
  > 
  > If one omits --enable-shared, ${enable_shared}'s value is "" which is
  > then used by libiberty's config.table to say `OK, the user didn't
  > explicitly say "no", so we're going to build a shared lib'.
  > 
  > This small patch corrects it.
I don't think that's right -- look at the toplevel configure files,
they should have set enable_shared to "no" if no specification of
enable_shared was provided by the user.

Something more subtle is going on.  I just haven't found it yet :-)
Jeff