On Wed, 27 Jul 2011, Will Coleda wrote:
> > Replying to [comment:6 dukeleto]:
> > > Compiling with gcc, but linking with g++ seems odd to me. For instance,
> > all our GCC farm smokers either do everything with gcc or everything with
> > g++.
> >
> > Back in the day, when I was very young in Parrot years, I was having
> > trouble getting Parrot to build on Mac. I consulted with the elders.
> > They (well, Coke) gave me the shell script (with `cc=gcc` but `link=g++`
> > and `ld=g++`) which has worked ever since. So it may seem odd, but it has
> > provided me/us with a consistent benchmark.
>
> Those directions date when parrot and ICU were both in the CVS repo,
> and we needed to jump through more hoops.
It may well be that such hoops are necessary on Darwin anymore, and if
that is all you mean to imply, then you are correct.
However, in general, Parrot should still jump through the same hoops.
ICU (or part of it, at least) is compiled with a C++ compiler. By
default, parrot tries to link with ICU if available. In order for that to
work on Solaris (and possibly other systems as well) the linker needs to
be a C++ compiler. It doesn't matter if ICU was built as part of the
parrot package (as was the case long ago) or if ICU was built and
installed independently. It's still a C++ library that parrot will link
to, so parrot still needs to use a link editor that understands C++
libraries. (See TT #309 for a specific example of the error messages that
ensued when the link was accidentally changed to use cc instead of CC on
OpenSolaris.)
--
Andy Dougherty [email protected]_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
