Enable shared lib tests for frv, lm32, m32r, microblaze, nds32 and or1k

[Alan Modra]

On Fri, Dec 08, 2017 at 06:06:27PM +0000, Kyrill Tkachov wrote:
> I'm seeing 202 unexpected failures on aarch64-none-elf with this patch.
> With errors telling me to recompile with -fPIC or
> "newlib/libgloss/aarch64/syscalls.c:639:(.text._sbrk+0x6c): dangerous
> relocation: unsupported relocation"
> Should the tests perhaps be skipped on a bare-metal target?

aarch64-none-elf uses ld/emulparams/aarch64elf.em, which enables
shared lib and PIE support.  So it seems to me that shared lib support
ought to be tested..

If the aarch64-elf environment never provides the necessary shared
libs for these tests to pass, I think you'd be better off disabling
the ld shared lib support.  If you sometimes do have shared libs, then
the situation isn't much different to one I hit on powerpc linux
occasionally:  People report testsuite failures due to not having
static libraries installed.

Well, that's the purist argument.  Pragmatic considerations might say
otherwise.  I'm fine with putting an exception into
check_shared_lib_support for aarch64-*-elf if that's what target
maintainers decide.

-- 
Alan Modra
Australia Development Lab, IBM