#32062 closed defect (fixed)
omniORB @4.1.4 build error with clang
Reported by: | arnim.balzer@… | Owned by: | stromnov (Andrey Stromnov) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | clang | Cc: | ryandesign (Ryan Carsten Schmidt), matejken@…, macports.org@…, cdeil (Christoph Deil), michaelld (Michael Dickens) |
Port: | omniORB |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi,
I tried installing the omniORB port after reinstalling my MacBook Air with Lion and the port did not compile any more (for the error see below). However, using install omniorb configure.compiler=apple-gcc-4.2 configure.cxx=g++-apple-4.2 fixed the problem. Just wanted to let you know.
Cheers
Arnim
P.S.: The error output
:info:build + /Developer/usr/bin/clang++ -o catior -L/opt/local/lib -arch x86_64 -pipe -O2 -arch x86_64 -fno-common -bind_at_load -L../../../../lib -L../../../../lib catior.o -lomniORB4 -lomnithread :info:build Undefined symbols for architecture x86_64: :info:build "operator<<=(unsigned int&, cdrStream&)", referenced from: :info:build _CORBA_Unbounded_Sequence<IOP::TaggedProfile>::operator<<=(cdrStream&) in catior.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[4]: *** [catior] Error 1 :info:build make[3]: *** [export] Error 1 :info:build make[2]: *** [export] Error 1 :info:build make[1]: *** [export] Error 1
Change History (15)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Milestone: | MacPorts 2.0.4 |
Owner: | changed from macports-tickets@… to stromnov@… |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | clang added |
---|---|
Summary: | omniORB @4.1.4 build error → omniORB @4.1.4 build error with clang |
comment:7 follow-up: 10 Changed 13 years ago by cdeil (Christoph Deil)
I see the same error as Arnim.
@ryandesign: configure.compiler=llvm-gcc-4.2
does work with omniorb 4.1.4.
I also tried to upgrade to the latest version 4.1.6, but that seems broken for Lion (XCode 4.2):
Using llvm-gcc-4.2 the error is:
/Developer/usr/bin/llvm-g++-4.2 -c -pipe -O2 -arch x86_64 -fno-common -bind_at_load -I/opt/local/include -I.. -I./.. -I../../../../include/omniORB4/internal -I../../../../include/omniORB4/internal -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY -DOMNIORB_VERSION_STRING='"4.1.6"' -DOMNIORB_VERSION_HEX='0x040106F1' -DCONFIG_DEFAULT_LOCATION='"/opt/local/etc/omniORB.cfg"' -DCONFIG_ENV='"OMNIORB_CONFIG"' -DUnixArchitecture -I. -I. -I../../../../include -I../../../../include -D__OSVERSION__=1 -D__darwin__ -D__x86_64__ -o static/corbaOrb.o corbaOrb.cc corbaOrb.cc: In member function ‘void omniOrbORB::do_shutdown(CORBA::Boolean)’: corbaOrb.cc:1092: error: ‘NO_RESOURCES_UnableToStartThread’ was not declared in this scope make[4]: *** [static/corbaOrb.o] Error 1
Using clang the error is:
/Developer/usr/bin/clang++ -c -pipe -O2 -arch x86_64 -fno-common -bind_at_load -I/opt/local/include -I.. -I./.. -I../../../../include/omniORB4/internal -I../../../../include/omniORB4/internal -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY -DOMNIORB_VERSION_STRING='"4.1.6"' -DOMNIORB_VERSION_HEX='0x040106F1' -DCONFIG_DEFAULT_LOCATION='"/opt/local/etc/omniORB.cfg"' -DCONFIG_ENV='"OMNIORB_CONFIG"' -DUnixArchitecture -I. -I. -I../../../../include -I../../../../include -D__OSVERSION__=1 -D__darwin__ -D__x86_64__ -o static/corbaOrb.o corbaOrb.cc clang: warning: argument unused during compilation: '-bind_at_load' corbaOrb.cc:1092:7: error: use of undeclared identifier 'NO_RESOURCES_UnableToStartThread' OMNIORB_THROW(NO_RESOURCES, ^ /opt/local/include/omniORB4/omniORB.h:732:52: note: instantiated from: _OMNI_NS(omniExHelper)::name(__FILE__, __LINE__, minor, completion) ^ corbaOrb.cc:1093:7: note: instantiated from: NO_RESOURCES_UnableToStartThread, ^ 1 error generated. make[4]: *** [static/corbaOrb.o] Error 1
comment:8 Changed 13 years ago by cdeil (Christoph Deil)
Python 2.7 works for me, can you add a variant?
I'm completely new to omniorb. It is not clear to me what the relation of the python variant of the omniorb port is and the py26-omniORBpy port. Maybe this could be mentioned briefly in the port / variant descriptions?
omniORB has the variants: python26: Enable python support with python 2.6 py26-omniORBpy @3.4 (python, devel) Python bindings for omniORB
I'll report the compile errors upstream now.
comment:9 Changed 13 years ago by cdeil (Christoph Deil)
OmniORB mailing list posts:
[omniORB] OmniORB 4.1.4 and 4.1.6 compile errors with clang / llvm-gcc on Mac OS X 10.7 (Lion)
http://www.omniorb-support.com/pipermail/omniorb-list/2012-January/031194.html
[omniORB] Which python versions does OmniORB support?
http://www.omniorb-support.com/pipermail/omniorb-list/2012-January/031195.html
comment:10 Changed 13 years ago by lockhart (Thomas Lockhart)
@ryandesign:
configure.compiler=llvm-gcc-4.2
does work with omniorb 4.1.4.I also tried to upgrade to the latest version 4.1.6, but that seems broken for Lion (XCode 4.2):
Using llvm-gcc-4.2 the error is:
/Developer/usr/bin/llvm-g++-4.2 -c -pipe -O2 -arch x86_64 -fno-common -bind_at_load -I/opt/local/include -I.. -I./.. -I../../../../include/omniORB4/internal -I../../../../include/omniORB4/internal -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY -DOMNIORB_VERSION_STRING='"4.1.6"' -DOMNIORB_VERSION_HEX='0x040106F1' -DCONFIG_DEFAULT_LOCATION='"/opt/local/etc/omniORB.cfg"' -DCONFIG_ENV='"OMNIORB_CONFIG"' -DUnixArchitecture -I. -I. -I../../../../include -I../../../../include -D__OSVERSION__=1 -D__darwin__ -D__x86_64__ -o static/corbaOrb.o corbaOrb.cc corbaOrb.cc: In member function ‘void omniOrbORB::do_shutdown(CORBA::Boolean)’: corbaOrb.cc:1092: error: ‘NO_RESOURCES_UnableToStartThread’ was not declared in this scope make[4]: *** [static/corbaOrb.o] Error 1
I can confirm that 4.1.6 builds on Lion using the llvm-gcc-4.2 compiler and XCode-4.2.1 and I see the same problems with "operator<<=()" when trying to use clang. Builds fine using python-2.7 as a variant. Will look for an open ticket or will open one to get updated to 4.1.6.
comment:12 Changed 13 years ago by michaelld (Michael Dickens)
I have the NO_RESOURCES issue on Mac OS X 10.6.8, XCode 3.2.3, gcc 4.2.1 (/usr/bin/g++-4.2), trying to install omniorb 4.1.6 +python26. This port does work with +python27 on my setup, so I'll use that. Though y'all might want to know about the python26 issue.
comment:13 Changed 12 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:14 follow-up: 15 Changed 12 years ago by matejken@…
I updated to omniORB-4.1.6_0+python26.darwin_11.x86_64.tbz2 on Lion today. I use Xcode 4.3.3 and Apple clang version 3.1 (tags/Apple/clang-318.0.61).
Building still fails with the following error:
:info:build corbaOrb.cc:1093:7: error: use of undeclared identifier 'NO_RESOURCES_UnableToStartThread' :info:build NO_RESOURCES_UnableToStartThread, :info:build ^ :info:build /opt/local/include/omniORB4/omniORB.h:732:52: note: expanded from macro 'OMNIORB_THROW' :info:build _OMNI_NS(omniExHelper)::name(__FILE__, __LINE__, minor, completion) :info:build
comment:15 Changed 12 years ago by matejken@…
Replying to matejken@…:
I updated to omniORB-4.1.6_0+python26.darwin_11.x86_64.tbz2 on Lion today. I use Xcode 4.3.3 and Apple clang version 3.1 (tags/Apple/clang-318.0.61).
Building still fails with the following error:
I removed all versions of omniORB and installed it again. This time it installed flawlessly.
Replying to arnim.balzer@…:
We would prefer to use llvm-gcc-4.2 if that works. Does it? See wiki:ProblemHotlist#compiler.