On 2 Sep 2004 15:22:39 -0000, Andy Dougherty via RT <[EMAIL PROTECTED]> wrote: > I'm not quite sure if I understand you correctly, since you don't want c++ > if Configure.pl chooses gcc. Perhaps you meant icu's configure would find > gcc? Or perhaps you mean 'g++' but happen to be calling it 'c++'? Let me > try re-stating the problem.
I mean g++/c++. On my system c++ looks to be a hard link to g++. I referred to it as c++ since that's what it is called in a similar hack in the Linux hints file. > This doesn't work. On some systems (not just Solaris) you can't mix g++ > and cc and expect the standard system linker to work. I don't have the Sun Pro compiler installed, but it makes sense you wouldn't be able to mix that, and g++. However, it appears that it was building parrot with gcc, and at least parts of icu with g++, then trying to link with gcc. This doesn't seem to work if you need libstdc++ to be linked in. I imagine that's why the Linux hints file has the hack that it does. > Further, on some systems (and again, not just Solaris) if you use c++ code > anywhere, you have to use the same c++ compiler as the linker. This seems to be exactly the issue I ran into. > I think the correct fix for this issue would be two patches to > Configure.pl: First, given the existing choice for $cc, pick the > appropriate $cxx compiler. Second, given the existing choices for $cc and > $cxx, pick the appropriate value for $link. I doubt that just guessing > based on the name alone will be sufficient. It will probably be necessary > to actually try the commands out. Sounds like that'd work, and is a more generic fix for the problem. I'm new to all this and didn't want to make a big change, just wanted to figure out a way to get it compiling for people that'd like to be able to build parrot on Solaris. The solaris hints file looked to already contain a similar hack for the Sun Pro compiler, so seemed like a reasonable fix.
