On Tuesday 15 February 2011, Carminati Federico wrote:
Hello Michael,
thanks a lot for looking into my problem. It turns out that Mac OS X
behaves a bit oddly, in the sense that the name of the directory of
installation is in the libraries as well as in the executable. I solved the
problem
On 02/14/2011 03:11 AM, Carminati Federico wrote:
Hello Michael,
thanks for your answer. Indeed it is a very complex built system, so the
link line is
/opt/gcc-4.5.1/bin/g++-DDarwin -DDATE_SYS=Darwin -Dlong32='int'
-Dlong64='long long' -DdatePointer='long' -O -g -pipe
Hello Michael,
thanks a lot for looking into my problem. It turns out that Mac OS X behaves
a bit oddly, in the sense that the name of the directory of installation is in
the libraries as well as in the executable. I solved the problem with a single
line setting the properties of the library
Hello Michael,
thanks for your answer. Indeed it is a very complex built system, so the
link line is
/opt/gcc-4.5.1/bin/g++-DDarwin -DDATE_SYS=Darwin -Dlong32='int'
-Dlong64='long long' -DdatePointer='long' -O -g -pipe -fbounds-check
-fsigned-char -fno-common -fmessage-length=0