[omniORB] building 2.5 on NT

Mark Snowdon mark@y-com.co.uk
Thu, 19 Mar 1998 09:18:55 -0000


Hello,

Sorry if this is a stupid question...everyone has to start somewhere !

I have attempted to build the NT(sp3) distribution of Omniorb 2.5, using =
VC++ 5(sp3), the build fails on omniidl2 with the following:

+ rm -f omniidl2.exe
+ ../../../bin/x86_win32/linkwrapper -out:omniidl2.exe =
-libpath:../../../lib/x86
_win32 driver/drv_init.o driver/drv_private.o driver/drv_main.o =
driver/drv_args.
o driver/drv_fork.o driver/drv_link.o driver/drv_preproc.o =
omniORB2_be/omniORB2_
be.lib fe/fe.lib ast/ast.lib util/util.lib narrow/narrow.lib =
advapi32.lib omniOR
B2_be/omniORB2_be.lib fe/fe.lib ast/ast.lib util/util.lib =
narrow/narrow.lib
Microsoft (R) 32-Bit Incremental Linker Version 5.02.7132
Copyright (C) Microsoft Corp 1992-1997. All rights reserved.

ast.lib(ast_string.o) : error LNK2001: unresolved external symbol =
"public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QAE@XZ)
ast.lib(ast_predefined_type.o) : error LNK2001: unresolved external =
symbol "public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QAE@XZ)
ast.lib(ast_structure.o) : error LNK2001: unresolved external symbol =
"public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QAE@XZ)
ast.lib(ast_union.o) : error LNK2001: unresolved external symbol =
"public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QAE@XZ)
ast.lib(ast_sequence.o) : error LNK2001: unresolved external symbol =
"public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QAE@XZ)
omniORB2_be.lib(o2be_union.o) : error LNK2001: unresolved external =
symbol "public: __thiscall AST_ConcreteType::AST_ConcreteType(void)" =
(??0AST_ConcreteType@@QA
E@XZ)
omniORB2_be.lib(o2be_array.o) : error LNK2001: unresolved external =
symbol "publi
etc...

All the errors relate to routines in ast, yet the ast.lib seems to have =
made OK, and is being linked.  Is this a problem with the idl_narrow =
macros ?

Am I missing something obvious ?


Mark Snowdon