- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: aCC doesn't like OCCI_STD_NAMESPACE::
Operating System - Linux
1755994
Members
3223
Online
108839
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2002 10:15 AM
06-05-2002 10:15 AM
aCC doesn't like OCCI_STD_NAMESPACE::
I'm having trouble building an Oracle OCCI app that also uses Iona Orbix on HP-UX 11i This app works fine on Tru64 Compaq UNIX. I'm using aCC V3.33, Oracle 9iRAC, and Iona Orbix E2A Std Edition. The problem is that the compile of a sample Oracle OCCI program
/opt/aCC/bin/aCC -c -v -AP +DAportable -mt -I$ORACLE_BASE/rdbms/demo
-I$ORACLE_BASE/rdbms/public occidml.cpp
where occidml.cpp is:
#include
#include
#include
#include
using namespace oracle::occi;
using namespace std;
gets errors like this:
Error 19: "/ora1/oracle/OraHome1/rdbms/demo/occiCommon.h", line 586 # Unexpected
'std'.
void getVector( const AnyData &any, OCCI_STD_NAMESPACE::vector &ve
ct, Type typ ) ;
^^^^^^^^^^^^^^^^^^
where compiler complains about std::vector and such. This should be perfectly legal if #include has already happened, and I made sure it did.
However, with -AA the problem goes away. I can't figure out why this matters. My workaround at present is to take out all occurrences of OCCI_STD_NAMESPACE:: in rdbms/demo/occi*.h, when I do this it compiles and links and runs fine. However, I have to link against -lstd_v2 -lCsup_v2 (apparently Oracle built its libraries with -AA.
This whole thing is a pain because Orbix was NOT built with -AA I can't get Orbix to link successfully with -AA (another problem).
My best attempt was:
shlib_dir=$IT_PRODUCT_DIR/orbix_art/2.0/cxx/lib
inc_dir=$IT_PRODUCT_DIR/orbix_art/2.0/cxx/include
aCC -v -AA -DIT_STD +DAportable -mt +p -I$inc_dir -o orbix_test orbix_test.cpp -L$shlib_dir -L$IT_PRODUCT_DIR/shlib -L$IT_PRODUCT_DIR/shlib/default -Wl,+n -Wl,+k -Wl,-E -Wl,-Bimmediate -Wl,-Bverbose -Wl,-Bsymbolic -Wl,+s -Wl,+vshlibunsats -lit_art
where orbix_test.cpp was:
#include "rtods.hh"
int main( int argc, char * argv[])
{
return 0;
}
which includes the IDL-generated client stub include file and nothing else. The above example compiles and links fine when -AA -DIT_STD are removed from compile/link command.
/opt/aCC/bin/aCC -c -v -AP +DAportable -mt -I$ORACLE_BASE/rdbms/demo
-I$ORACLE_BASE/rdbms/public occidml.cpp
where occidml.cpp is:
#include
#include
#include
#include
using namespace oracle::occi;
using namespace std;
gets errors like this:
Error 19: "/ora1/oracle/OraHome1/rdbms/demo/occiCommon.h", line 586 # Unexpected
'std'.
void getVector( const AnyData &any, OCCI_STD_NAMESPACE::vector
ct, Type typ ) ;
^^^^^^^^^^^^^^^^^^
where compiler complains about std::vector and such. This should be perfectly legal if #include
However, with -AA the problem goes away. I can't figure out why this matters. My workaround at present is to take out all occurrences of OCCI_STD_NAMESPACE:: in rdbms/demo/occi*.h, when I do this it compiles and links and runs fine. However, I have to link against -lstd_v2 -lCsup_v2 (apparently Oracle built its libraries with -AA.
This whole thing is a pain because Orbix was NOT built with -AA I can't get Orbix to link successfully with -AA (another problem).
My best attempt was:
shlib_dir=$IT_PRODUCT_DIR/orbix_art/2.0/cxx/lib
inc_dir=$IT_PRODUCT_DIR/orbix_art/2.0/cxx/include
aCC -v -AA -DIT_STD +DAportable -mt +p -I$inc_dir -o orbix_test orbix_test.cpp -L$shlib_dir -L$IT_PRODUCT_DIR/shlib -L$IT_PRODUCT_DIR/shlib/default -Wl,+n -Wl,+k -Wl,-E -Wl,-Bimmediate -Wl,-Bverbose -Wl,-Bsymbolic -Wl,+s -Wl,+vshlibunsats -lit_art
where orbix_test.cpp was:
#include "rtods.hh"
int main( int argc, char * argv[])
{
return 0;
}
which includes the IDL-generated client stub include file and nothing else. The above example compiles and links fine when -AA -DIT_STD are removed from compile/link command.
- Tags:
- -AA
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2006 09:53 PM
03-08-2006 09:53 PM
Re: aCC doesn't like OCCI_STD_NAMESPACE::
As you found namespace std is not available unless you use -AA. You may be able to define OCCI_STD_NAMESPACE to empty?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP