David Zaltron ha scritto:
Regards,

i'm trying to compile Ganglia v.3.03 on a SunOS 5.10, but i've found those errors trying to build the system; the following text is the output of the make process.

#uname -a
SunOS lab02 5.10 Generic_118822-18 sun4u sparc SUNW,Ultra-Enterprise-10000


# make
(...)
In file included from /usr/include/sys/wait.h:24,
                 from /usr/include/stdlib.h:22,
                 from daemon_init.c:6:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
(...)
In file included from /usr/include/sys/procset.h:24,
                 from /usr/include/sys/wait.h:25,
                 from /usr/include/stdlib.h:22,
                 from daemon_init.c:6:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from /usr/include/stdlib.h:22,
                 from daemon_init.c:6:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
In file included from daemon_init.c:12:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
daemon_init.c: In function `update_pidfile':
daemon_init.c:37: warning: int format, pid_t arg (arg 3)
daemon_init.c:40: warning: int format, pid_t arg (arg 4)


I've found the solution, the problem was a misconfiguraiton of the gcc 3.3.2, as reported in the sunfreeware site:

--------
Note that this version of gcc was created on build 60 of Solaris 10. If you are using a higher version, you will need to redo some of the header files. This is done by doing the following steps:

cd /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/install-tools/

Put the line SHELL=/bin/sh on the first line of the mkheaders.conf
file.  Then run

./mkheaders

This will correct some files and make the build 60 gcc usable on
higher builds.  I have tested this on build 72 and it works fine.
------------

After doing this, all run correctly.


Reply via email to