Hi.

Lurie wrote:
> I was about to compile keepassx when I noticed I already had an old binary in 
> the bin, so I've tried that and it just worked :)
> 
> Might as well be luck, but it does work the same (the only difference from 
> the version I later compiled with stdcxx this time
> is that a combo-box doesn't have its background set properly).
> 
> Btw, I'm using QT4.3.1 (previous keepassx has been compiled for 
> QT4.3.0+libcstd), compiled 4.3.1 with SunStudio 12 + stdcxx,
> could also be that old keepassx binary hasn't been compiled with any 
> optimizations (no sse2, cmov, etc...).
> 
> Do you have an stdcxx.jam (jam2) for boost so that we could try compiling 
> that cleanly as well ?. I've modded the sun.jam directly
> and inserted the required options, most of the libraries compile with no 
> changes, but two didn't:

Yes, i just put it up:

http://www.stefanteleman.org/libstdcxx/boost/

I plan on making the BOOST test harness results available over the next day or 
two -- hopefully tomorrow late evening.

> 1) filesystem
> 
> "libs/filesystem/src/operations.cpp", line 1219: Error: malloc is not a 
> member of std.
> "libs/filesystem/src/operations.cpp", line 1227: Error: free is not a member 
> of std.
> fixed by adding an include for stdlib.h, after that it compiles fine
> 
> 2) python
> "/usr/include/python2.4/pyport.h", line 381: Error: Only one of a set of 
> overloaded functions can be extern "C".
> The code in question is:
> #ifdef SOLARIS                                                                
>                                     
> /* Unchecked */                                                               
>                                     
> extern int gethostname(char *, int);                                          
>                                   
> #endif      
> fixed by commenting out that in pyport.h

I don't really know why python believes that Solaris doesn't have 
gethostname(3C). :-)

> and then:
> "libs/python/src/object/class.cpp", line 458: Error: Overloading ambiguity 
> between
> "boost::python::api::getattr<boost::python::scope, char[11], 
> boost::python::str>(const boost::python::scope&, const char(&)[11], const 
> boost::python::str&)" and "boost::python::api::getattr(const 
> boost::python::api::object&, const char*, const boost::python::api::object&)",
> fixed with an explicit cast, after that it compiles fine,

Have to check this one out. I haven't seen it in my build logs, though.

--Stefan

-- 
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM


Reply via email to