Cannot compile Orbit2-2.8.1 under Solaris
- From: Dan Oscarsson <Dan Oscarsson kiconsulting se>
- To: orbit-list gnome org
- Subject: Cannot compile Orbit2-2.8.1 under Solaris
- Date: Sat, 27 Sep 2003 16:17:54 +0200 (CEST)
Has anyone compiled Gnome under Solaris using Sun's own compilers?
Now when Gnome 2.4 came out I hoped that finally I could compile Gnome,
but no - not yet.
Currently it fails with Orbit2-2.8.1.
The log shows:
gmake[8]: Entering directory
`/df/src/Gnome2.4/ORBit2-2.8.1/include/orbit/orb-core'
(rm -f corba-defs.h corba-defs-stubs.c corba-defs-skels.c corba-defs-common.c
corba-defs-imodule.c corba-defs-skelimpl.c || true) > /dev/null
../../../src/idl-compiler/orbit-idl-2 -I../../../src/idl/CORBA_PIDL
-I../../../src/idl/CORBA -I../../../src/idl/interop --noskels --nodefskels
--nostubs --noidata --nocommon --showcpperrors --define=Object=OObject
--define=TypeCode=TTypeCode --deps ./.deps/corba-defs.idl.P
../../../src/orb/orb-core/corba-defs.idl
../../../src/orb/orb-core/corba-defs.idl:27: Error: parse error, expecting
`TOK_ENUM' or `TOK_STRUCT' or `TOK_UNION'
"<stdin>", cannot close output file
cc: acomp failed for -
** (process:25651): WARNING **: ../../../src/orb/orb-core/corba-defs.idl
compilation failed
orbit-idl-2 2.8.1 compiling
mode, show preprocessor errors, passes: headers skel_impl imodule
I have tried tracing all system calls, tried setting CPP to /usr/lib/cpp,
but cannot find what is wrong. The error message do not tell me very
much. I can see that the idl-compiler calls the c-compiler and that during
parsing its output the idl-compiler stops. Manually producing the
c-compiler produced files do not show me what is wrong. Is it possible
to get the idl-compiler to tell what line and what text that fails?
>From my tracing it looks like the idl-compiler calls:
cc -E -I- - -I../../../src/orb/orb-core -D__ORBIT_IDL__
-I../../../src/idl/CORBA_PIDL -I../../../src/idl/CORBA
-I../../../src/idl/interop -DObject=OObject -DTypeCode=TTypeCode <
"../../../src/orb/orb-core/corba-defs.idl"
and fails during parsing its output.
I have run the same using /usr/lib/cpp and the only significant difference
I can see is spaces, like:
< interface TTypeCode;
---
> interface TTypeCode ;
< exception UNKNOWN {unsigned long minor; completion_status
completed;};
< exception BAD_PARAM {unsigned long minor; completion_status
completed;};
---
> exception UNKNOWN { unsigned long minor ; completion_status
completed ; };
> exception BAD_PARAM { unsigned long minor ; completion_status
completed ; };
Can this be the problem?
Dan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]