Jack Howarth <howa...@bromo.med.uc.edu> writes:
> Have you built gcc trunk with --enable-plugin on either
> Solaris or Irix? What is the expectation of which compiler is
No need: plugins just work on both platforms, both with the vendor tools
and gld (on Solaris, gld is currently broken for IRIX).
> I find on Irix 6.5 that the system compiler lacks -rdynamic so
> that part of the test would fail unless a gcc compiler is
Doesn't matter: even if you bootstrap with the vendor compiler (works on
Solaris, still on my agenda for IRIX), stages 2 and 3 are built with
gcc. With the native linkers, -rdynamic isn't needed and
gcc/configure.ac handles this just fine. In my case, I had to introduce
-rdynamic support into gcc so plugins work with gld:
PATCH: Handle -rdynamic on Solaris 2 with GNU ld
http://gcc.gnu.org/ml/gcc-patches/2010-03/msg01458.html
> used. On Solaris 9, I have an ancient vendor supplied gcc 3.2.3
> which doesn't seem to support -rdynamic either. It is unclear
> to me how many additional utilities are expected to be installed
> for FSF gcc to build on hosts like Irix or Solaris these days.
That's certainly an important goal: currently, we have several hidden
dependencies like that that influence what features the GCC just build
has. This should be made more transparent.
> ps My inclination is to proceed with the current patch and
> adjust it for Solaris and Irix later after the base tool
> set is agreed upon for those hosts. That is, will users be
> able to bootstrap FSF gcc using the system compiler and
> --enable-plugin or will they have to install a previous
> FSF gcc first.
As I said, the bootstrap compiler isn't relevant here. But *please*
avoid introducing new failure modes for other platforms in your effort
to improve Darwin support.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
