Re: Errors while compiling Orbacus 4.3 on HP-UX

Darren Middleman <[email protected]> Thu, 29 Sep 2005 09:00:44 -0230
Newsgroups gmane.comp.corba.orbacus
Organization IONA | Making Software Work Together TM
Message-ID <[email protected]>
Hi Bharath,

> I am getting the following errors while compiling Orbacus 4.3 on HP-UX 11.
> Can you please let me know how to resolve this.
> 
> My compiler version is aCC 3.37
> Thanks,
> Bharath
> 
> *******************************
> making all in cpp
>         rm -f ../../../bin/idlcpp
>         LIBPATH=xxx ; unset LIBPATH ; \
>         cc -I../../../include -o ../../../bin/idlcpp cccp.c cexp.c
> cccp.c:
> cexp.c:
> (Bundled) cc: "y.tab.c", line 360: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 360: error 1000: Unexpected symbol: 
> "unsigned".
> (Bundled) cc: "y.tab.c", line 395: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 395: error 1000: Unexpected symbol: 
> "unsigned".
> (Bundled) cc: "y.tab.c", line 405: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 405: error 1000: Unexpected symbol: 
> "yysigned_char".
> (Bundled) cc: "y.tab.c", line 424: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 424: error 1000: Unexpected symbol: 
> "unsigned".
> (Bundled) cc: "y.tab.c", line 437: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 437: error 1000: Unexpected symbol: "char".
> (Bundled) cc: "y.tab.c", line 437: warning 5: "const" will become a keyword.
> (Bundled) cc: "y.tab.c", line 437: error 1000: Unexpected symbol: "yytname".
> (Bundled) cc: error 2017: Cannot recover from earlier errors, terminating.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 

As you can see from the error messages, the problem is being caused by the
bundled HP C compiler that comes with HP-UX.  This compiler isn't as
complete as a usual C compiler so it won't work for Orbacus.  

If you have installed a complete HP C compiler on your system, you should 
make sure that the path to the 'cc' command is in your PATH environment
variable.  Alternatively, you can use the aCC flag '-Ae' to turn on ANSI C
c89 mode.  This should allow you to compile the C portions of Orbacus.
Run the 'runconfig' script selecting your options for the HP-UX build.
Before you execute the '. ./go' command, edit the config.env file and make
the following change:

  Change the line:

    CC='cc'; export CC

  to:

    CC='aCC -Ae'; export CC

Now run '. ./go' and compile Orbacus as usual.  Note that if you
reconfigure Orbacus, you will need to make this change again.

You could also change a line in 'runconfig' so that you won't have to keep
making this change any time you re-configure Orbacus.  In 'runconfig', locate
the block that selects the options for HP-UX (should be around line 835) and 
make the following change:

      $cpp_hp_1100 ) # HP aC++ for HPUX 11.00
          env_CC="aCC -Ae"
                  ^^^^^^^

The 'runconfig' script should now use the 'aCC -Ae' option as your C compiler
instead of 'cc'.

Regards,
Darren

-- 
Darren Middleman, Software Engineer
Team Orbacus - Your CORBA Source
Email: mailto:[email protected]
WWW: http://www.orbacus.com/
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html