Jean-Marc Lasgouttes wrote:
> It seems that I am really not able to compile 1.3.0cvs on tru64 unix
> with cxx. Reasons are:
>
> - there is no snprintf in tru64 4.0f, so xforms has to provide its
> own. the one provided in xforms lib does not compile on tru64, but
> it does after a patch that I sent to the xforms list. So far, so
> good.
I'm surprised, as I too had to send a patch to get things to compile,
but it was included in 1.0release. (I use 4.0e here).
I've unsubscribed from the xforms list at work and your post isn't
yet int he archive. Care to tell me what you had to do?
> - LyX's configure script does not know that it has to use -lformssnp
> on systems that do not have snprintf. I have a patch for that. So
> far so good.
That is because it uses the snprintf functions in src/support. It
shouldn't matter whether these functions come from libformssnp.a (as
they do when compiling one of the xforms demo programs) or from
libsupport.a (as they do here when compiling LyX under 4.0e).
> - boost really thinks that all C functions are in std:: and uses
> std::fprintf and things like that all over the place. This is not
> good at all with cxx and probably sun's CC. I am not sure what to
> do about that.
There is a cxx compilation flag, -nopure_cname, that the
DEC/Compaq/HP support people told me to use. Here I configure LyX
with:
CC="cc -std1"
export CC
CFLAGS="-O2"
export CFLAGS
CXX="cxx -std strict_ansi"
export CXX
CXXFLAGS="-nopure_cname -nocleanup -msg_display_number -msg_disable
11,193,236,261,401,445,450,611 -w1 -ptr
${PWD}/${BUILDDIR}/lyx_cxx_repository -O2"
export CXXFLAGS
HTH
--
Angus
