[Symphony] Building symphony with -library=stlport4

Irit Katriel iritkatriel at googlemail.com
Tue Nov 10 13:15:03 EST 2009


I just built symphony on a Solaris machine or the first time. I did not use
the default configuration, and here are some of the problem I ran into
(probably relevant to other Coin projects as well).

I wanted the libraries to work with a 64-bit application that uses boost,
and is therefore compiled and linked with -mt -m64 -library=stlport4
-library=no%Cstd.  So I added these options to the symphony build.

1. The most painful problem was with C library functions - with the
compilation flags I gave, printf, fabs, malloc, free, strlen, memset, and so
on were not recognized. This is because they are in std namespace when you
include them via <cstdio>, etc rather than <stdio.h>, etc.    I believe the
c++ coding standard requires to use std::printf, std::fabs, and so on.

2. The second hurdle was passing the additional flags to the linker. Since
it is invoked by libtool, I needed to pass "-XCClinker -mt -XCClinker -m64
-XCClinker -library=stlport4 -XCClinker -library=no%Cstd"  as additional
arguments for libtool. It could probably help to have an environment
variable for this purpose (LIBTOOL_ARGS?) which is picked up by the
configuration scripts.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/symphony/attachments/20091110/7bebc825/attachment.html>


More information about the Symphony mailing list