libffi alpha--freebsd* configuration patch

Wed Mar 27 16:02:00 GMT 2002

Loren> There is no interesting information there. Spot checking 10 of
Loren> the new failures under gdb, I see this mysterious backtrace:
Loren> [ ... ]
Loren> Ahh, this is in a tree with shared libgcc finally enabled (in
Loren> gcc/config.gcc) for this port. I did nothing about this over in
Loren> libjava yet. Could this be somehow related?
> It is possible. Bryce also reported having a problem here.

I have since tested it both ways: once in a tree with shared libgcc
enabled and once in a tree with only static libgcc enabled (I also
made sure that all copies of the shared libgcc were removed from the
system between builds). The EH tests were not failing due to the this
change.
> I do see code in the libjava test suite to find libgcc_s.so.
> Maybe this code isn't working or otherwise needs help.
> Could you try running the test suite with `--verbose' and then look in
> libjava.log to see how LD_LIBRARY_PATH is set?
> We print it out like so:

> verbose "LD_LIBRARY_PATH = $env(LD_LIBRARY_PATH)"

Yes, that looks fine here.

libffi alpha*-*-freebsd* configuration patch

libffi alpha--freebsd* configuration patch