[omniORB] Newbie - Compiler Error on MacOSX for Echo Tutorial

[bido@mac.com]

To provide further clarification for PROBLEM 2:

My system does not have an nmake command. So I can execute

nmake /f dir.mak [<build option>]

Looking at the dir.mk It all seems geared towards the x86 
architecture...
Maybe I should have configure the omniORB installed differently for
I accepted all the defaults but the root location which I chose 
/usr/local.

Thanks!
-FB



On Monday, November 25, 2002, at 12:23  AM, bido@mac.com wrote:

> Thanks Bjorn,
>
> Note that I'll have two problems going on in this same thread:
>
> PROBLEM 1 - SOLVED - (Compiling my own copy/pasted version of echo 
> example eg1.cc)
> I switched to g++ and it worked fine -see prior post.
>
> PROBLEM 2 - UNSOLVED- (Building the packaged examples)
>  It did not build. Here's what I got:
>
> [122:src/examples/echo] bido% make
> dir=../../../stub;  if [ ! -d $dir ]; then (umask 002; set -x; mkdir 
> -p $dir); fi
> rm -f ../../../stub/echo.idl
> ../../../bin/powerpc_darwin_1.3/omniidl -bcxx -Wba -Wbtp 
> -C../../../stub  ../../../idl/echo.idl
> make: ../../../bin/powerpc_darwin_1.3/omniidl: Command not found
> make: *** [../../../stub/echo.hh] Error 127
>
> The only thing that I did was to uncomment a line in config.mk file 
> file:
>
> #platform = powerpc_aix_4.3_xlc5
> #platform = powerpc_linux_2.2_glibc
> platform = powerpc_darwin_1.3
> #platform = hppa_hpux_10.20
> #platform = hppa_hpux_11.00
>
> Note in the make output above, it references 
> /bin/powerpc_darwin_1.3/omniidl
> but the dir powerpc_darwin_1.3 does not exist under omniORB-4.0.0/bin. 
> There is
> however a dir named x86_win32 which has no relevance in my system.
>
> Any hints on this matter?
>
> On Sunday, November 24, 2002, at 04:18  AM, bjorn rohde jensen wrote:
>
>> Hi,
>>
>>  Why dont you just do a 'make' in the examples dir? I am
>> fairly sure, that builds the examples.
>>  The error from gcc surprises me a bit. I would have
>> expected gcc not to have liked being asked to generate an
>> object file from a C++ style header file:) The .hh's are
>> supposed to be included by your sources implementing or
>> using the interfaces defined in the corresponding IDL file.
>>  You really should use g++ for C++ code and for linking
>> C++ object files, gcc is for C code. There are differences
>> in the defines and supporting libs added by gcc and g++.
>>
>> Yours sincerely,
>>
>> Bjorn
>>
>> _______________________________________________
>> omniORB-list mailing list
>> omniORB-list@omniorb-support.com
>> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>