[Monotone-devel] Re: Problems compiling on Solaris 9 with GCC 3.3.2

[wildjim]

  Thanks for the idea, Graydon, but I've since been digging down that route, and
GCC (on Solaris) is a bit of a pain when it comes to selecting which 'ld' to
link with:

http://article.gmane.org/gmane.comp.lib.boost.user/4010
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10590
http://gcc.gnu.org/onlinedocs/gcc-3.3.2/gccint/Collect2.html

  I've tried putting a 'real-ld' in the $PATH, but it seems to ignore it.  So
far, creating a symlink to GNU ld early on in one of GCC's '-print-search-dirs'
search folders (try 'gcc -print-search-dirs') partly works, but screws up some
other compiles... it seems GNU's ld is definitely not the best choice on
Solaris!!

  I was hoping to not duplicate someone else's fix, but I'm now trying to see if
there's any easy-ish way to change the default linker for Boost.Jam even when
you set TOOLS=gcc...  I get the feeling I'm going to have to hack some Jamfiles
or Jamrules or Boost.Jam itself, once I understand how the thing works, so I'll
go bother the Boost mailing list about this, instead.


  But is it difficult to tell Monotone to not compile-in/use the Unix tests,
then?


On Mon, 15 Dec 2003 16:11:46 -0500, graydon hoare wrote:

> 
> Will Robertson wrote:
> >  I'm having problems getting Boost to compile -- which may be related  
> > to GCC3 on Solaris defaulting to using Solaris 'ld' (/usr/ccs/bin/ld)  
> > which has problems with GCC3's translation of -shared & -static  
> > together -- but it only seems to be a problem in the test-suite.
> >  I know I might be posting to the wrong list, but does anyone have any  
> > ideas how to persuade it to use GNU ld, for a start, but also whether  
> > it even matters to Monotone if this part of Boost hasn't worked?  And  
> > thridly whether Monotone has any similar dependencies on GNU ld?
> 
> well, you can always hack the solution up with a shell script in $PATH 
> called 'ld' which does 'exec /path/to/gnu/ld $*' but that's pretty 
> terrible. otherwise, hm.. which part of boost exactly is having this 
> failure? libboost_unit_test_framework.a? we only need that for building 
> unit_tests, so you could do without I suppose.
> 
> >  I'll keep trying in the meantime, but I'd appreciate any pointers, or  
> > helpful retelling of experiences.
> 
> unfortunately I have no experience building boost on solaris. you might 
> want to try the boost mailing lists, at www.boost.org.
> 
> -graydon