f



[ciao-users] Utility library not being found on ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2

Hello again,
	I am still attempting to install BBN's quo system and I was just 
informed that I should use ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2.  This is the 
reason for using an older version.

     CIAO VERSION: 0.4.2
     TAO VERSION : 1.4.2
     ACE VERSION : 5.4.2

     HOST MACHINE and OPERATING SYSTEM: Dell Dimension 8100 w/ Gentoo 
Linux (2.6 kernel)

     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
     COMPILER NAME AND VERSION (AND PATCHLEVEL):

     AREA/CLASS/EXAMPLE AFFECTED:
CCF library

     DOES THE PROBLEM AFFECT:
         COMPILATION?
             If so, what do your $ACE_ROOT/ace/config.h:
// -*- C++ -*-
//
// config-linux.h,v 4.41 2004/04/22 20:54:00 shuston Exp

// The following configuration file is designed to work for Linux
// platforms using GNU C++.

#ifndef ACE_CONFIG_LINUX_H
#define ACE_CONFIG_LINUX_H
#include /**/ "ace/pre.h"

#define ACE_PLATFORM_CONFIG config-linux.h

#include "ace/config-linux-common.h"

#define ACE_HAS_SVR4_DYNAMIC_LINKING
#define ACE_HAS_AUTOMATIC_INIT_FINI
#define ACE_HAS_DLSYM_SEGFAULT_ON_INVALID_HANDLE

#if !defined (ACE_MT_SAFE)
#define ACE_MT_SAFE 1                           // JCEJ 12/22/96        
#1
#endif

#if ACE_MT_SAFE
// Yes, we do have threads.
#define ACE_HAS_THREADS
// And they're even POSIX pthreads (LinuxThreads implementation)
#define ACE_HAS_PTHREADS
// ... and the final standard even!
#define ACE_HAS_PTHREADS_STD

#if !defined (ACE_HAS_PTHREADS_UNIX98_EXT)
#  define ACE_LACKS_RWLOCK_T
#else
#  define ACE_HAS_RECURSIVE_MUTEXES
#endif  /* !ACE_HAS_PTHREADS_UNIX98_EXT */

#define ACE_HAS_THREAD_SPECIFIC_STORAGE     // jcej 12/22/96         #2

#define ACE_HAS_RECURSIVE_THR_EXIT_SEMANTICS    // JCEJ 1/7-8/96

#if defined(__GLIBC__)
// Platform supports reentrant functions (i.e., all the POSIX *_r
// functions).
#define ACE_HAS_REENTRANT_FUNCTIONS

#if (__GLIBC__ < 2) || (__GLIBC__ == 2 && __GLIBC_MINOR__ < 1)
    // Older versions of glibc lacked reentrant netdb functions
#  define ACE_LACKS_NETDB_REENTRANT_FUNCTIONS

    // glibc < 2.1 lacks pthread_attr_setstacksize()
#  define ACE_LACKS_THREAD_STACK_SIZE
#endif /* (__GLIBC__ < 2) || (__GLIBC__ == 2 && __GLIBC_MINOR__ < 1) */

// uses ctime_r & asctime_r with only two parameters vs. three
#define ACE_HAS_2_PARAM_ASCTIME_R_AND_CTIME_R
#endif

#endif  /* ACE_MT_SAFE */


#include /**/ "ace/post.h"

#endif /* ACE_CONFIG_LINUX_H */
  and
             $ACE_ROOT/include/makeinclude/platform_macros.GNU contain?
exceptions=1
interface_repo=1
cidl=1
ssl=1
include $(ACE_ROOT)/include/makeinclude/platform_linux.GNU
         LINKING?
             On Unix systems, did you run make realclean first?
         EXECUTION?
         OTHER (please specify)?
[Please indicate whether ACE/TAO/CIAO, your application, or both are 
affected.]

     SYNOPSIS:
Can't find Utility?

     DESCRIPTION:
when I try to build CCF, the compiler throws up all over itself.  Very 
messy.

andy@bender /usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF $ make
make[1]: Entering directory 
`/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
make[2]: Entering directory 
`/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'

GNUmakefile: 
/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL/GNUmakefile.CIDL 
MAKEFLAGS=w

g++ -W -Wall -Wpointer-arith -O3 -g -pipe    -D_REENTRANT 
-DACE_HAS_AIO_CALLS -D_GNU_SOURCE   -I/usr/local/ACE_wrappers 
-DACE_HAS_EXCEPTIONS -D__ACE_INLINE__ -I../..  -c  -o 
..obj/LexicalAnalyzer.o LexicalAnalyzer.cpp
In file included from ../../CCF/IDL2/Token.hpp:12,
                  from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
                  from LexicalAnalyzer.cpp:5:
.../../CCF/CompilerElements/ReferenceCounting.hpp:8:59: 
Utility/ReferenceCounting/ReferenceCounting.hpp: No such file or 
directory
In file included from ../../CCF/IDL2/Token.hpp:12,
                  from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
                  from LexicalAnalyzer.cpp:5:
.../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: `Utility' 
has not been declared
.../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: expected 
namespace-name before ';' token
.../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: unknown 
namespace `<declaration error>'
In file included from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
                  from LexicalAnalyzer.cpp:5:
.../../CCF/IDL2/Token.hpp:21: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:21: error: expected template-name before '<' 
token
.../../CCF/IDL2/Token.hpp:21: error: expected `{' before '<' token
.../../CCF/IDL2/Token.hpp:21: error: expected unqualified-id before '<' 
token
.../../CCF/IDL2/Token.hpp:21: error: expected `,' or `;' before '<' token
.../../CCF/IDL2/Token.hpp:59: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:59: error: expected init-declarator before '<' 
token
.../../CCF/IDL2/Token.hpp:59: error: expected `,' or `;' before '<' token
.../../CCF/IDL2/Token.hpp:63: error: `TokenPtr' was not declared in this 
scope
.../../CCF/IDL2/Token.hpp:64: error: template argument 1 is invalid
.../../CCF/IDL2/Token.hpp:64: error: template argument 2 is invalid
.../../CCF/IDL2/Token.hpp:64: error: ISO C++ forbids declaration of 
`TokenList' with no type
.../../CCF/IDL2/Token.hpp:67: error: `TokenPtr' has not been declared
.../../CCF/IDL2/Token.hpp:68: error: ISO C++ forbids declaration of `t' 
with no type
.../../CCF/IDL2/Token.hpp: In function `std::ostream& 
CCF::IDL2::operator<<(std::ostream&, int&)':
.../../CCF/IDL2/Token.hpp:69: error: base operand of `->' is not a 
pointer
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:77: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::EndOfStream::EndOfStream(long unsigned int)':
.../../CCF/IDL2/Token.hpp:80: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::EndOfStream'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:86: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:86: error: expected init-declarator before '<' 
token
.../../CCF/IDL2/Token.hpp:86: error: expected `,' or `;' before '<' token
.../../CCF/IDL2/Token.hpp:93: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::Keyword::Keyword(std::string, long unsigned int)':
.../../CCF/IDL2/Token.hpp:96: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::Keyword'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:102: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:102: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:102: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:109: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::Punctuation::Punctuation(std::string, long unsigned int)':
.../../CCF/IDL2/Token.hpp:112: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::Punctuation'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:121: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:121: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:121: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:129: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::Operator::Operator(std::string, long unsigned int)':
.../../CCF/IDL2/Token.hpp:132: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::Operator'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:141: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:141: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:141: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:149: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::Identifier::Identifier(std::string, long unsigned int)':
.../../CCF/IDL2/Token.hpp:152: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::Identifier'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:158: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:158: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:158: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:175: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:175: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:175: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:192: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:192: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:192: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp:200: error: invalid use of undefined type 
`class CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
CCF::IDL2::Token'
.../../CCF/IDL2/Token.hpp: In constructor 
`CCF::IDL2::Literal::Literal(std::string, long unsigned int)':
.../../CCF/IDL2/Token.hpp:203: error: type `class CCF::IDL2::Token' is 
not a direct base of `CCF::IDL2::Literal'
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:209: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:209: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:209: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp: In member function `bool 
CCF::IDL2::BooleanLiteral::value() const':
.../../CCF/IDL2/Token.hpp:227: error: `lexeme' undeclared (first use 
this function)
.../../CCF/IDL2/Token.hpp:227: error: (Each undeclared identifier is 
reported only once for each function it appears in.)
.../../CCF/IDL2/Token.hpp: In member function `virtual void 
CCF::IDL2::BooleanLiteral::print(std::ostream&)':
.../../CCF/IDL2/Token.hpp:233: error: `lexeme' undeclared (first use 
this function)
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:238: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:238: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:238: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp: In member function `virtual void 
CCF::IDL2::CharacterLiteral::print(std::ostream&)':
.../../CCF/IDL2/Token.hpp:263: error: `lexeme' undeclared (first use 
this function)
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:271: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:271: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:271: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp: In member function `virtual void 
CCF::IDL2::IntegerLiteral::print(std::ostream&)':
.../../CCF/IDL2/Token.hpp:297: error: `lexeme' undeclared (first use 
this function)
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:305: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:305: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:305: error: expected `,' or `;' before '<' 
token
.../../CCF/IDL2/Token.hpp: In member function `virtual void 
CCF::IDL2::StringLiteral::print(std::ostream&)':
.../../CCF/IDL2/Token.hpp:335: error: `lexeme' undeclared (first use 
this function)
.../../CCF/IDL2/Token.hpp: At global scope:
.../../CCF/IDL2/Token.hpp:343: error: `ReferenceCounting' has not been 
declared
.../../CCF/IDL2/Token.hpp:343: error: expected init-declarator before 
'<' token
.../../CCF/IDL2/Token.hpp:343: error: expected `,' or `;' before '<' 
token
In file included from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
                  from LexicalAnalyzer.cpp:5:
.../../CCF/IDL2/LexicalAnalyzer.hpp:26: error: `TokenPtr' was not 
declared in this scope
.../../CCF/IDL2/LexicalAnalyzer.hpp:27: error: template argument 1 is 
invalid
.../../CCF/IDL2/LexicalAnalyzer.hpp:44: error: `TokenPtr' does not name 
a type
.../../CCF/IDL2/LexicalAnalyzer.hpp:51: error: `TokenPtr' does not name 
a type
.../../CCF/IDL2/LexicalAnalyzer.hpp:55: error: `TokenPtr' has not been 
declared
.../../CCF/IDL2/LexicalAnalyzer.hpp:55: error: ISO C++ forbids 
declaration of `token' with no type
.../../CCF/IDL2/LexicalAnalyzer.hpp:58: error: `TokenPtr' has not been 
declared
.../../CCF/IDL2/LexicalAnalyzer.hpp:58: error: ISO C++ forbids 
declaration of `token' with no type
.../../CCF/IDL2/LexicalAnalyzer.hpp:61: error: `TokenPtr' has not been 
declared
.../../CCF/IDL2/LexicalAnalyzer.hpp:61: error: ISO C++ forbids 
declaration of `token' with no type
.../../CCF/IDL2/LexicalAnalyzer.hpp:64: error: `TokenPtr' has not been 
declared
.../../CCF/IDL2/LexicalAnalyzer.hpp:64: error: ISO C++ forbids 
declaration of `token' with no type
.../../CCF/IDL2/LexicalAnalyzer.hpp:70: error: `TokenPtr' has not been 
declared
.../../CCF/IDL2/LexicalAnalyzer.hpp:70: error: ISO C++ forbids 
declaration of `token' with no type
make[2]: *** [.obj/LexicalAnalyzer.o] Error 1
make[2]: Leaving directory 
`/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
make[1]: *** [CIDL] Error 2
make[1]: Leaving directory 
`/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
make: *** [all] Error 2

my Config.rules:
# file      : Config.rules
# author    : Boris Kolpackov <boris@dre.vanderbilt.edu>
# cvs-id    : Config.rules,v 1.8 2004/01/15 20:38:13 boris Exp

# You may provide correct values for your configuration here.
#

# Set either BOOST_ROOT or BOOST_LIB & BOOST_INCLUDE. In case
# only BOOST_ROOT is set then BOOST_LIB=$(BOOST_ROOT)/lib and
# BOOST_INCLUDE=$(BOOST_ROOT)
#

BOOST_ROOT    ?=
BOOST_LIB     ?=
BOOST_INCLUDE ?=


UTILITY_ROOT        ?=/usr/local/Utility-1.2.2
UTILITY_INCLUDE     ?=/usr/local/Utility-1.2.2
UTILITY_BUILD_RULES ?=/usr/local/Utility-1.2.2/BuildRules


# You normally would not want to edit anything below.
#


     REPEAT BY:
run make in the CCF folder as seen above.

     SAMPLE FIX/WORKAROUND:

0
Andrew
3/7/2005 12:04:04 AM
comp.soft-sys.ace 20326 articles. 1 followers. marlow.andrew (167) is leader. Post Follow

2 Replies
914 Views

Similar Articles

[PageSpeed] 27

--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Andrew,

Thanks for using the PRF.

Andrew Bonventre <andrew.bonventre@tufts.edu> writes:

>     SYNOPSIS:
> Can't find Utility?

Utility library is required to build CCF (which is a CIDL compiler
frontend) as well as a couple of boost libraries. You can find
detailed instructions on where to get them by reading

$CIAO_ROOT/CCF/Documentation/Build.html

or online

http://www.cs.wustl.edu/~schmidt/ACE_wrappers/TAO/CIAO/CCF/Documentation/Build.html

Also note that you can always get a precompiled binary of CIDLC (even for
older releases of CIAO) here:

http://www.dre.vanderbilt.edu/cidlc/binary/


hth,
-boris

--jI8keyz6grp/JLjh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iQGVAwUBQiwCiMiAKQuuCE8dAQI21Av/XCjz6yaOMttP4Aa/wlr9S71S7hyr6STB
KC4Vhkjxo956BwYmCL22dYg8Hb6cwcE+D6IBeYY0CxeZI4TWKl3ouQOcT1l3G2zy
5+3lybbVejBcAH4qTpA89Ve2c+MVTr2WlxsXGWZkSoe7MSAXbizCrFDC/wUfIuFa
GE4QlNV8WUOFrCHzYAzjy9XPH5FWUoHVp3rOOwxjsch5yZsi1CGusGtEZmZa+hG2
MJL7kR9zESFMO4ToBaQholCPGIFXETlPmMXEbdeKO7f9+cTnZeuxVz+i+FAQxND0
FHejRp7HB9gBEquyNiX8VzvN3HEhoeHa48UtxN7v05t+td3uRmtKqygQjg1JPrO1
x1O6hxR5f3+KkgnzZNQXqbM5S5yQn2w8cQa7+w67i0cNKsLb/6Ezpw1NxicpjKrq
7w3IPI4PwHLegCeb6DbjJ108EQbcI3XpJbIBvDM/Z3ZagHODQe7xtKT/UiN5sF0L
uxbNxjeHnAOVFbazL0dwEpaODjq1JqmD
=mYww
-----END PGP SIGNATURE-----

--jI8keyz6grp/JLjh--

0
Boris
3/7/2005 7:20:35 AM
You can download a specific version of CIDL instead of compiling it on your 
own - I will get back to you with the specific version you need shortly.


----- Original Message ----- 
From: "Andrew Bonventre" <andrew.bonventre@tufts.edu>
To: <ciao-users@cs.wustl.edu>
Sent: Sunday, March 06, 2005 6:53 PM
Subject: [ciao-users] Utility library not being found on ACE/TAO/CIAO 
5.4.2/1.4.2/0.4.2


> Hello again,
> I am still attempting to install BBN's quo system and I was just informed 
> that I should use ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2.  This is the reason for 
> using an older version.
>
>     CIAO VERSION: 0.4.2
>     TAO VERSION : 1.4.2
>     ACE VERSION : 5.4.2
>
>     HOST MACHINE and OPERATING SYSTEM: Dell Dimension 8100 w/ Gentoo Linux 
> (2.6 kernel)
>
>     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>     COMPILER NAME AND VERSION (AND PATCHLEVEL):
>
>     AREA/CLASS/EXAMPLE AFFECTED:
> CCF library
>
>     DOES THE PROBLEM AFFECT:
>         COMPILATION?
>             If so, what do your $ACE_ROOT/ace/config.h:
> // -*- C++ -*-
> //
> // config-linux.h,v 4.41 2004/04/22 20:54:00 shuston Exp
>
> // The following configuration file is designed to work for Linux
> // platforms using GNU C++.
>
> #ifndef ACE_CONFIG_LINUX_H
> #define ACE_CONFIG_LINUX_H
> #include /**/ "ace/pre.h"
>
> #define ACE_PLATFORM_CONFIG config-linux.h
>
> #include "ace/config-linux-common.h"
>
> #define ACE_HAS_SVR4_DYNAMIC_LINKING
> #define ACE_HAS_AUTOMATIC_INIT_FINI
> #define ACE_HAS_DLSYM_SEGFAULT_ON_INVALID_HANDLE
>
> #if !defined (ACE_MT_SAFE)
> #define ACE_MT_SAFE 1                           // JCEJ 12/22/96        #1
> #endif
>
> #if ACE_MT_SAFE
> // Yes, we do have threads.
> #define ACE_HAS_THREADS
> // And they're even POSIX pthreads (LinuxThreads implementation)
> #define ACE_HAS_PTHREADS
> // ... and the final standard even!
> #define ACE_HAS_PTHREADS_STD
>
> #if !defined (ACE_HAS_PTHREADS_UNIX98_EXT)
> #  define ACE_LACKS_RWLOCK_T
> #else
> #  define ACE_HAS_RECURSIVE_MUTEXES
> #endif  /* !ACE_HAS_PTHREADS_UNIX98_EXT */
>
> #define ACE_HAS_THREAD_SPECIFIC_STORAGE     // jcej 12/22/96         #2
>
> #define ACE_HAS_RECURSIVE_THR_EXIT_SEMANTICS    // JCEJ 1/7-8/96
>
> #if defined(__GLIBC__)
> // Platform supports reentrant functions (i.e., all the POSIX *_r
> // functions).
> #define ACE_HAS_REENTRANT_FUNCTIONS
>
> #if (__GLIBC__ < 2) || (__GLIBC__ == 2 && __GLIBC_MINOR__ < 1)
>    // Older versions of glibc lacked reentrant netdb functions
> #  define ACE_LACKS_NETDB_REENTRANT_FUNCTIONS
>
>    // glibc < 2.1 lacks pthread_attr_setstacksize()
> #  define ACE_LACKS_THREAD_STACK_SIZE
> #endif /* (__GLIBC__ < 2) || (__GLIBC__ == 2 && __GLIBC_MINOR__ < 1) */
>
> // uses ctime_r & asctime_r with only two parameters vs. three
> #define ACE_HAS_2_PARAM_ASCTIME_R_AND_CTIME_R
> #endif
>
> #endif  /* ACE_MT_SAFE */
>
>
> #include /**/ "ace/post.h"
>
> #endif /* ACE_CONFIG_LINUX_H */
>  and
>             $ACE_ROOT/include/makeinclude/platform_macros.GNU contain?
> exceptions=1
> interface_repo=1
> cidl=1
> ssl=1
> include $(ACE_ROOT)/include/makeinclude/platform_linux.GNU
>         LINKING?
>             On Unix systems, did you run make realclean first?
>         EXECUTION?
>         OTHER (please specify)?
> [Please indicate whether ACE/TAO/CIAO, your application, or both are 
> affected.]
>
>     SYNOPSIS:
> Can't find Utility?
>
>     DESCRIPTION:
> when I try to build CCF, the compiler throws up all over itself.  Very 
> messy.
>
> andy@bender /usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF $ make
> make[1]: Entering directory 
> `/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
> make[2]: Entering directory 
> `/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
>
> GNUmakefile: 
> /usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL/GNUmakefile.CIDL MAKEFLAGS=w
>
> g++ -W -Wall -Wpointer-arith -O3 -g -pipe    -D_REENTRANT -DACE_HAS_AIO_CALLS 
>  -D_GNU_SOURCE   -I/usr/local/ACE_wrappers -DACE_HAS_EXCEPTIONS -D__ACE_INLINE__ 
>  -I../..  -c  -o .obj/LexicalAnalyzer.o LexicalAnalyzer.cpp
> In file included from ../../CCF/IDL2/Token.hpp:12,
>                  from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
>                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
>                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
>                  from LexicalAnalyzer.cpp:5:
> ../../CCF/CompilerElements/ReferenceCounting.hpp:8:59: 
> Utility/ReferenceCounting/ReferenceCounting.hpp: No such file or directory
> In file included from ../../CCF/IDL2/Token.hpp:12,
>                  from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
>                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
>                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
>                  from LexicalAnalyzer.cpp:5:
> ../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: `Utility' has 
> not been declared
> ../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: expected 
> namespace-name before ';' token
> ../../CCF/CompilerElements/ReferenceCounting.hpp:10: error: unknown 
> namespace `<declaration error>'
> In file included from ../../CCF/IDL2/LexicalAnalyzer.hpp:16,
>                  from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
>                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
>                  from LexicalAnalyzer.cpp:5:
> ../../CCF/IDL2/Token.hpp:21: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:21: error: expected template-name before '<' 
> token
> ../../CCF/IDL2/Token.hpp:21: error: expected `{' before '<' token
> ../../CCF/IDL2/Token.hpp:21: error: expected unqualified-id before '<' 
> token
> ../../CCF/IDL2/Token.hpp:21: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:59: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:59: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:59: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:63: error: `TokenPtr' was not declared in this 
> scope
> ../../CCF/IDL2/Token.hpp:64: error: template argument 1 is invalid
> ../../CCF/IDL2/Token.hpp:64: error: template argument 2 is invalid
> ../../CCF/IDL2/Token.hpp:64: error: ISO C++ forbids declaration of 
> `TokenList' with no type
> ../../CCF/IDL2/Token.hpp:67: error: `TokenPtr' has not been declared
> ../../CCF/IDL2/Token.hpp:68: error: ISO C++ forbids declaration of `t' 
> with no type
> ../../CCF/IDL2/Token.hpp: In function `std::ostream& 
> CCF::IDL2::operator<<(std::ostream&, int&)':
> ../../CCF/IDL2/Token.hpp:69: error: base operand of `->' is not a pointer
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:77: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::EndOfStream::EndOfStream(long unsigned int)':
> ../../CCF/IDL2/Token.hpp:80: error: type `class CCF::IDL2::Token' is not a 
> direct base of `CCF::IDL2::EndOfStream'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:86: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:86: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:86: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:93: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::Keyword::Keyword(std::string, long unsigned int)':
> ../../CCF/IDL2/Token.hpp:96: error: type `class CCF::IDL2::Token' is not a 
> direct base of `CCF::IDL2::Keyword'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:102: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:102: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:102: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:109: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::Punctuation::Punctuation(std::string, long unsigned int)':
> ../../CCF/IDL2/Token.hpp:112: error: type `class CCF::IDL2::Token' is not 
> a direct base of `CCF::IDL2::Punctuation'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:121: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:121: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:121: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:129: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::Operator::Operator(std::string, long unsigned int)':
> ../../CCF/IDL2/Token.hpp:132: error: type `class CCF::IDL2::Token' is not 
> a direct base of `CCF::IDL2::Operator'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:141: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:141: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:141: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:149: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::Identifier::Identifier(std::string, long unsigned int)':
> ../../CCF/IDL2/Token.hpp:152: error: type `class CCF::IDL2::Token' is not 
> a direct base of `CCF::IDL2::Identifier'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:158: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:158: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:158: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:175: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:175: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:175: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:192: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:192: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:192: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp:200: error: invalid use of undefined type `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp:21: error: forward declaration of `class 
> CCF::IDL2::Token'
> ../../CCF/IDL2/Token.hpp: In constructor 
> `CCF::IDL2::Literal::Literal(std::string, long unsigned int)':
> ../../CCF/IDL2/Token.hpp:203: error: type `class CCF::IDL2::Token' is not 
> a direct base of `CCF::IDL2::Literal'
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:209: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:209: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:209: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp: In member function `bool 
> CCF::IDL2::BooleanLiteral::value() const':
> ../../CCF/IDL2/Token.hpp:227: error: `lexeme' undeclared (first use this 
> function)
> ../../CCF/IDL2/Token.hpp:227: error: (Each undeclared identifier is 
> reported only once for each function it appears in.)
> ../../CCF/IDL2/Token.hpp: In member function `virtual void 
> CCF::IDL2::BooleanLiteral::print(std::ostream&)':
> ../../CCF/IDL2/Token.hpp:233: error: `lexeme' undeclared (first use this 
> function)
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:238: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:238: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:238: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp: In member function `virtual void 
> CCF::IDL2::CharacterLiteral::print(std::ostream&)':
> ../../CCF/IDL2/Token.hpp:263: error: `lexeme' undeclared (first use this 
> function)
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:271: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:271: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:271: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp: In member function `virtual void 
> CCF::IDL2::IntegerLiteral::print(std::ostream&)':
> ../../CCF/IDL2/Token.hpp:297: error: `lexeme' undeclared (first use this 
> function)
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:305: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:305: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:305: error: expected `,' or `;' before '<' token
> ../../CCF/IDL2/Token.hpp: In member function `virtual void 
> CCF::IDL2::StringLiteral::print(std::ostream&)':
> ../../CCF/IDL2/Token.hpp:335: error: `lexeme' undeclared (first use this 
> function)
> ../../CCF/IDL2/Token.hpp: At global scope:
> ../../CCF/IDL2/Token.hpp:343: error: `ReferenceCounting' has not been 
> declared
> ../../CCF/IDL2/Token.hpp:343: error: expected init-declarator before '<' 
> token
> ../../CCF/IDL2/Token.hpp:343: error: expected `,' or `;' before '<' token
> In file included from ../../CCF/IDL3/LexicalAnalyzer.hpp:8,
>                  from ../../CCF/CIDL/LexicalAnalyzer.hpp:8,
>                  from LexicalAnalyzer.cpp:5:
> ../../CCF/IDL2/LexicalAnalyzer.hpp:26: error: `TokenPtr' was not declared 
> in this scope
> ../../CCF/IDL2/LexicalAnalyzer.hpp:27: error: template argument 1 is 
> invalid
> ../../CCF/IDL2/LexicalAnalyzer.hpp:44: error: `TokenPtr' does not name a 
> type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:51: error: `TokenPtr' does not name a 
> type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:55: error: `TokenPtr' has not been 
> declared
> ../../CCF/IDL2/LexicalAnalyzer.hpp:55: error: ISO C++ forbids declaration 
> of `token' with no type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:58: error: `TokenPtr' has not been 
> declared
> ../../CCF/IDL2/LexicalAnalyzer.hpp:58: error: ISO C++ forbids declaration 
> of `token' with no type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:61: error: `TokenPtr' has not been 
> declared
> ../../CCF/IDL2/LexicalAnalyzer.hpp:61: error: ISO C++ forbids declaration 
> of `token' with no type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:64: error: `TokenPtr' has not been 
> declared
> ../../CCF/IDL2/LexicalAnalyzer.hpp:64: error: ISO C++ forbids declaration 
> of `token' with no type
> ../../CCF/IDL2/LexicalAnalyzer.hpp:70: error: `TokenPtr' has not been 
> declared
> ../../CCF/IDL2/LexicalAnalyzer.hpp:70: error: ISO C++ forbids declaration 
> of `token' with no type
> make[2]: *** [.obj/LexicalAnalyzer.o] Error 1
> make[2]: Leaving directory `/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
> make[1]: *** [CIDL] Error 2
> make[1]: Leaving directory `/usr/local/ACE_wrappers/TAO/CIAO/CCF/CCF/CIDL'
> make: *** [all] Error 2
>
> my Config.rules:
> # file      : Config.rules
> # author    : Boris Kolpackov <boris@dre.vanderbilt.edu>
> # cvs-id    : Config.rules,v 1.8 2004/01/15 20:38:13 boris Exp
>
> # You may provide correct values for your configuration here.
> #
>
> # Set either BOOST_ROOT or BOOST_LIB & BOOST_INCLUDE. In case
> # only BOOST_ROOT is set then BOOST_LIB=$(BOOST_ROOT)/lib and
> # BOOST_INCLUDE=$(BOOST_ROOT)
> #
>
> BOOST_ROOT    ?=
> BOOST_LIB     ?=
> BOOST_INCLUDE ?=
>
>
> UTILITY_ROOT        ?=/usr/local/Utility-1.2.2
> UTILITY_INCLUDE     ?=/usr/local/Utility-1.2.2
> UTILITY_BUILD_RULES ?=/usr/local/Utility-1.2.2/BuildRules
>
>
> # You normally would not want to edit anything below.
> #
>
>
>     REPEAT BY:
> run make in the CCF folder as seen above.
>
>     SAMPLE FIX/WORKAROUND: 













































































































































































































































































































































































0
Praveen
3/7/2005 2:52:28 PM
Reply:

Similar Artilces:

[tao-users] Use of TAO_OutputCDR and ACE_Message_Block in CORBA::Any from TAO 1.4.1|ACE 5.4.1 to TAO2.2.0|ACE 6.2.0
This is a multipart message in MIME format. ------=_NextPart_000_00BF_01CEA8D4.9E005C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable TAO VERSION: 2.2.0 ACE VERSION: 6.2.0 =20 HOST MACHINE and OPERATING SYSTEM: x86_64 and Red Hat - Linux 2.6.18-194.26.1.el5 =20 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: =20 COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc (GCC) 4.8.1 =20 THE $ACE_ROOT/ace/config.h FILE: config-linux.h =20 THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE: platform_linux.GNU =20 CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features (used by MPC when you generate your own makefiles): =20 AREA/CLASS/EXAMPLE AFFECTED: TAO_OutputCDR and ACE_Message_Block. =20 DOES THE PROBLEM AFFECT: EXECUTION. My application is affected. =20 SYNOPSIS: The code that extract data from CORBA::Any using TAO_OutputCDR and ACE_Message_Block for user defined types works properly in the old platform (TAO 1.4.1|ACE 5.4.1), but not in the new one(ACE 6.2.0). =20 DESCRIPTION: The code in the =93REPEAT BY=94 section works fine in the old platform = for user defined types, that is, the TAO_OutputCDR and ACE_Message_Block objects have the same length, but in the new platform th...

ACE 5.4.2 + TAO 1.4.2 client, ORBacus 4.1.2 NameService, and JACOrb 1.4.1 servants
Hi everyone, Background: ----------- I'm very new to CORBA, ACE & TAO. I'm trying to integrate with a 3rd party system which exposes a CORBA object model to clients. This system is composed of JACOrb 1.4.1 servers registering with an ORBacus 4.1.2 NameService. We've got existing software that uses ACE 5.4.2, and the 3rd party documentation mentions that people have used TAO (no version specified) previously to integrate with their system, so I'm trying out TAO 1.4.2 as a natural solution to the problem. Environment Specifics: ---------------------- - ACE 5.4.2 + TAO 1.4.2 clients - running on a variant of RedHat Enterprise Linux 4.x (x86 platform) - compiled with gcc-c++-3.4.3-22.1 - ORBacus 4.1.2 NameService, and JACorb 1.4.1 servants (the 3rd Party stuff) - running on SunOS 5.9 What I'm trying to do: ---------------------- To get started, I'm trying to create a simple "hi3rdParty" app which acquires a reference to the remote ORBacus NameService so that I can then get at the other services. Here's the code I'm using: try { // ------ begin common CORBA init -------- // First initialize the ORB - that will remove some arguments... // NOTE: we're gonna try and use "-ORBInitRef NameService=corbaloc:iiop:theServer:5000/NameService" // to find the naming service. CORBA::ORB_var orb = CORBA::ORB_init(argc, argv, "&quo...

[ciao-users] ACE+TAO+CIAO
Hi, We are pleased to announce a new beta of ACE-5.4.5, TAO-1.4.5 and CIAO-0.4.5. This beta contains a number of time/space optimizations, including POA/Skeleton refactoring and TypeCode reimplementation. It also fixes a number of important bugs reported by our users, which we greatly appreciate, as always. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta will be updated in the next few hours! We encourage you to download the new beta, use it with your applications, and let us know if you encounter any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenotes for the status of various ongoing projects at the DOC groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. Overviews of our recent progress and upcoming plans are available at $ACE_ROOT/NEWS $TAO_ROOT/NEWS $CIAO_ROOT/NEWS The overall succeeded test results gathered from all our daily builds is 98% for the ACE tests and 93% for the TAO tests. Please see http://www.dre.vanderbilt.edu/scoreboard/ for a summary of these tests. Our goal is to get these tests close to 100% for the next major release (i.e., ACE 6.0,...

[ace-users] Re: a little bug of ACE-5.4.1+TAO-1.4.1+CIAO-0.4.1.tar.gz
Hi Adam, Please upgrade to ACE+TAO x.4.8, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". The DOC groups at Washington University, UC Irvine, and Vanderbilt University only provide "best effort" support for non-sponsors for the latest beta kit, as described in http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/ACE-bug-process.html Thus, if you need more "predictable" help for ACE 5.4.1, I recommend that you check out http://www.cs.wustl.edu/~schmidt/commercial-support.html for a list of companies that will provide you with ACE+TAO commercial support. Thanks, Doug >> When I compile this version, it prompts me the following errors that >> /*------ >> gmake[6]: *** No rule to make target `Client_Request_Interceptor.cpp', >> needed by `.obj/Client_Request_Interceptor.o'. Stop. >> ------*/ >> >> Then I find there is something wrong about the directory: >> /export/home/adam/ace.5.4.1.cc.64/TAO/tests/Portable_Interceptors/Request_Interceptor_Flow >> There are two files whose file names suffix are very strange. >> 1. Client_Request_Interceptor.cp >> 2. Server_Request_Interceptor.cp >> After I rename them from .cp to .cpp >> >> I wonder if this is a bug or some thing I configure wrong? >> >> Regards, >> Adam >> -...

Does 4/2/2= (4/2)/2 =1 OR = 4/(2/2)=4
I don't have matlab and I am trying to translate some simple matlab code. Does 4/2/2 = (4/2)/2 = 1 or 4/2/2 = 4/(2/2) = 4 On 9/11/2012 9:43 AM, sarah.englander@gmail.com wrote: > I don't have matlab and I am trying to translate some simple matlab code. > > Does 4/2/2 = (4/2)/2 = 1 yes. At a given precedence level (and obviously two of the same operators are the same level) evaluation proceeds from LtoR. ....snip... <http://www.mathworks.com/help/techdoc/matlab_prog/f0-40063.html#f0-38155> -- dpb <none@non.net> wrote in message <...

RE: [ace-users] segfault on linux x86-64 with ACE/TAO 5.4.4/1.4.4 #2
Hi, > Thanks for the reply. > The reason why I posted the stacktrace is that I have > currently no clue how to > reproduce a small testcase. But I will keep trying. > > I had the hope that someone familiar with ACE_Malloc_T<> > could shed light on > this subject. As I said the curious thing is that it works > with 32bit and > fails with 64bit. The only thing that I can imagine off is that somewhere a 64bit pointer is by accident handled as 32bit. Johnny ...

RE: [tao-users] Re: [ace-users] Re: Announcing the release of the new beta (ACE-5.4.10, TAO-1.4.10 and CIAO-0.4.10)
Hi, > > >> We encourage you to download the new beta, use it with your > > >> applications, and let us know soon if you encounter any problems > > >> since we plan to cut the x.5 release by February 28th. > > > > As per Wallace's comments, we have an aggressive schedule > for the x.5 > > release to meet the needs of some major sponsors. If > people can give > > x.4.10 a "test drive" in the next couple of days and report problems > > they encounter we'll try to ensure that we fix any > showstoppers before > > According to bugzilla bug 2323 is not fixed yet. > > http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=2323 > > For us it is a show stopper. We use the OCI version which does not > have problems related to this bug but it would be nice to be able to > use the latest version with more fixes. FYI, the reason that this test now fails is because Ossama added several new test cases which wheren't in the test in the past, this uncovered some bugs which according to our information where already there a long time. Johnny "Johnny Willemsen" <jwillemsen@remedy.nl> writes: > > > >> We encourage you to download the new beta, use it with your > > > >> applications, and let us know soon if you encounter any problems > > > >> sinc...

ACE+TAO+CIAO
Hi, We are happy to announce a new beta of ACE-5.4.4, TAO-1.4.4 and CIAO-0.4.4. This beta provides improved support for VxWorks 5.5.1 using static libraries and fixes a number of important bugs reported by our users. Thanks to all our users for reporting these issues. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta will be updated in the next few hours! We highly encourage you to download the present beta and use it with your applications and let us know if there are any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We would also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenotes for the status of various ongoing projects at the doc groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. The overall succeeded test results gathered from all our daily builds is 97% for the ACE tests and 92% for the TAO tests. In addition the following is a list of noteworthy changes since the last beta. Please refer to the ChangeLog for more details on the problem and the nature of fixes applied. Changes common to ACE+TAO+CIAO ============================== .. Removed MPC code that creates unused and unnecessary subfolders in Visual ...

[ciao-users] ACE+TAO+CIAO
Hi, We are pleased to announce a new beta of ACE-5.4.7, TAO-1.4.7 and CIAO-0.4.7. Since the x.4.6 beta had so many changes and improvements, we wanted to get this new beta out quickly to fix several important bugs reported by our users, which we greatly appreciate, as always. We've also added a number of subsetting improvements that reduce the static/dynamic footprint of ACE+TAO significantly. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta is also available. We encourage you to download the new beta, use it with your applications, and let us know if you encounter any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenotes for the status of various ongoing projects at the DOC groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. Overviews of our recent progress and upcoming plans are available at $ACE_ROOT/NEWS $TAO_ROOT/NEWS $CIAO_ROOT/NEWS The overall success rates for the test results gathered from all our daily builds is 98% for the ACE tests and 95% for the TAO tests. Please see http://www.dre.vanderbilt.edu/scoreboard/ for a summary of these tests...

[ciao-users] ACE+TAO+CIAO
Hi, We are pleased to announce a new beta of ACE-5.4.6, TAO-1.4.6 and CIAO-0.4.6. Since the x.4.5 beta had so many changes and improvements, we wanted to get this new beta out quickly to fix several important bugs reported by our users, which we greatly appreciate, as always. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta will be updated in the next few hours. We encourage you to download the new beta, use it with your applications, and let us know if you encounter any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenotes for the status of various ongoing projects at the DOC groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. Overviews of our recent progress and upcoming plans are available at $ACE_ROOT/NEWS $TAO_ROOT/NEWS $CIAO_ROOT/NEWS The overall success rates for the test results gathered from all our daily builds is 98% for the ACE tests and 94% for the TAO tests. Please see http://www.dre.vanderbilt.edu/scoreboard/ for a summary of these tests. Our goal is to get these tests close to 100% for the next major release (i.e., ACE 6.0, TAO 2.0, and C...

[ace-users] Re: [tao-support] Has ACE 5.4.4/TAO 1.4.4 been built with gcc 4.0.0 yet
Hi Robert, > When building ACE 5.4.4/TAO 1.4.4 using gcc 4.0.0 under fedora core > 4 test 2 on an x86 platform I get a lot of errors mainly to do with > template instantiations. Has anyone successfully build TAO/ACE using > the latest gcc ? We just added GCC 4.0.0 support to ACE+TAO recently. The forthcoming x.4.5 beta should work nicely with GCC 4.0.0. We hope to have this available very shortly (there's just one remaining snag with typecodes that should be fixed in the next day or so). If you'd like to give things a try before we release x.4.5 please download the contents of ACE+TAO from our CVS repo at http://cvs.doc.wustl.edu/ and see if it works for you on your platform. If not, please let us know and we'll try to make sure that it's working before we put out the beta release. Thanks, Doug I've tried the CVS version on macosx 10.4, with gcc4.0 and still got the same intantiation problem. On 5/9/05, Douglas C. Schmidt <schmidt@cs.wustl.edu> wrote: > > Hi Robert, > > > When building ACE 5.4.4/TAO 1.4.4 using gcc 4.0.0 under fedora core > > 4 test 2 on an x86 platform I get a lot of errors mainly to do with > > template instantiations. Has anyone successfully build TAO/ACE using > > the latest gcc ? > > We just added GCC 4.0.0 support to ACE+TAO recently. The forthcoming > x.4.5 beta should work nicely with GCC 4.0.0. We hope to ha...

RE: [ace-users] ACE+TAO+CIAO
Hi, Please use the prf form and which configuration you build. I personally think you have an old version of ACE/TAO on the system that is used. Regards, Johnny > -----Original Message----- > From: owner-ace-users@cse.wustl.edu > [mailto:owner-ace-users@cse.wustl.edu] On Behalf Of Domingos Monteiro > Sent: donderdag 9 juni 2005 18:05 > To: Simon McQueen > Cc: ace-users@cs.wustl.edu > Subject: Re: [ace-users] ACE+TAO+CIAO - 5.4.6 + 1.4.6 + 0.4.6 released > > Hi, > > I've just dowloaded this version > I've started to compile ACE with > - MSVC 7.1 > - Win XP > And get the following link errors: > > Message_Block.obj : error LNK2005: "public: virtual void __thiscall > ACE_Deadline_Message_Strategy::convert_priority(class ACE_Time_Value > &,class ACE_Message_Block const &)" > (?convert_priority@ACE_Deadline_Message_Strategy@@UAEXAAVACE_T > ime_Value@@ABVACE_Message_Block@@@Z) > already defined in CDR_Size.obj > Message_Block.obj : error LNK2005: "public: virtual void __thiscall > ACE_Laxity_Message_Strategy::convert_priority(class ACE_Time_Value > &,class ACE_Message_Block const &)" > (?convert_priority@ACE_Laxity_Message_Strategy@@UAEXAAVACE_Tim > e_Value@@ABVACE_Message_Block@@@Z) > already defined in CDR_Size.obj > SString.obj : error LNK2005: "public: __thiscall > ACE_NS_WString::ACE_N...

RE: Subject: Building ACE 5.3.1 on Mac OS X (Tiger) 10.4.2 was [ace-users] Building ACE on Mac OSX 10.4 #2
Hi Doug, > > Thanks for using the PRF. > > >> ACE VERSION: 5.3.1 > > This version of ACE is ANCIENT. The forthcoming ACE 5.4.8 beta should > work "out of the box" for Mac OS X Tiger. If you want a preview, > please download the version in our CVS repo at I know it isn't the most recent version available, but this version is used extensively across the corporation. Changing the version of ACE all these products used will cause the architect's heads to explode ;) Is it your opinion that 5.3.1 is hopeless cause on Tiger? > http://cvs.doc.wustl.edu/ I will try it out, and let you know how it works. Thanks, Jason ...

RE: Subject: Building ACE 5.3.1 on Mac OS X (Tiger) 10.4.2 was [ace-users] Building ACE on Mac OSX 10.4 #2
Hi Jason, > > >> ACE VERSION: 5.3.1 > > > > This version of ACE is ANCIENT. The forthcoming ACE 5.4.8 > beta should > > work "out of the box" for Mac OS X Tiger. If you want a preview, > > please download the version in our CVS repo at > > I know it isn't the most recent version available, but this > version is used > extensively across the corporation. Changing the version of > ACE all these > products used will cause the architect's heads to explode ;) ;-) Right - this is where the value of commercial support providers comes into play. DOC's research efforts continue to march on as they should, while commercial product efforts are best served by sticking with a version of ACE over time. Companies such as Riverace can make a 5.3-base version work on Mac OS X Tiger, for instance, as well as make sure that when your product is ready for an upgrade, the new version of ACE won't surprise you. I'd be happy to discuss further how we can help you and your architects - we don't want any heads to explode :-) -Steve -- Steve Huston, Riverace Corporation Helping you succeed with ACE See http://www.riverace.com/support.htm ...

Re: Subject: Building ACE 5.3.1 on Mac OS X (Tiger) 10.4.2 was [ace-users] Building ACE on Mac OSX 10.4 #2
Hi Jason, >> I know it isn't the most recent version available, but this version >> is used extensively across the corporation. Changing the version of >> ACE all these products used will cause the architect's heads to >> explode ;) >> >> Is it your opinion that 5.3.1 is hopeless cause on Tiger? It'll take some work, but companies like Riverace, Remedy, and OCI can help out with this stuff if staying with 5.3.1 is essential. Please see http://www.cs.wustl.edu/~schmidt/commercial-support.html for help with this stuff. >> > http://cvs.doc.wustl.edu/ >> I will try it out, and let you know how it works. Great - if there are any problems please let us know quickly so that we can get the fixes into the x.4.8 beta. Thanks, Doug -- Dr. Douglas C. Schmidt Professor and Associate Chair Electrical Engineering and Computer Science TEL: (615) 343-8197 Institute for Software Integrated Systems WEB: www.dre.vanderbilt.edu/~schmidt Vanderbilt University, Nashville TN, 37203 NET: d.schmidt@vanderbilt.edu ...

[ciao-users] Announcing the release of the new beta (ACE-5.4.8, TAO-1.4.8 and CIAO-0.4.8)
[The following is on behalf of the PrismTech build-czars!] Hi, We are pleased to announce a new beta of ACE-5.4.8, TAO-1.4.8, and CIAO-0.4.8. We are currently working hard on the long-awaited x.5 release, which is slated to appear in early 2006. We therefore wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate as always. We've added a number of sub-setting improvements that reduce the static/dynamic footprint of ACE+TAO significantly (www.dre.vanderbilt.edu/Stats has all the details). We've also finally added support for Real-time CCM to CIAO and DAnCE. This beta is contains the results of our major footprint reduction effort that started in the summer of 2004. Between August 1st 2004 and October 14th 2005 the footprint reduction for the ORB_Init application has been 20%. Dependent on the parts of TAO you use the reduction can even be more. This reduction is inclusive all the extensions that have been made to TAO the last year. Interested users should check out http://www.dre.vanderbilt.edu/Stats/ for more details. Note that the footprint has increased slightly again due to emulated exceptions having been disabled in favour of native C++ exceptions in all stats builds. We have deprecated support for emulated exceptions since there are no sponsors for this configuration. If you require emulated exceptions please contact one of the companies listed in http://w...

[ace-users] Announcing the release of the new beta (ACE-5.4.9, TAO-1.4.9 and CIAO-0.4.9)
Hi, We are pleased to announce a new beta of ACE-5.4.9, TAO-1.4.9, and CIAO-0.4.9. The documentation for this beta kit will be available shortly. We are still working very hard on the x.5 release, which is scheduled to be released by the beginning of March if all goes well. We wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate, as always. We've also added a number of improvements to the various components in ACE, TAO and CIAO. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta is also available. We encourage you to download the new beta, use it with your applications, and let us know if you encounter any problems. Please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We also request that you take a look at $TAO_ROOT/docs/releasenotes for the status of various ongoing projects at the DOC groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. Overviews of our recent progress and upcoming plans are available at $ACE_ROOT/NEWS $TAO_ROOT/NEWS $CIAO_ROOT/NEWS The overall success rates for the test results gathered from all our daily builds is 95.68% for the ACE tests and 88.6% for the TAO tests. Please see http://www.dr...

[ciao-users] Announcing the release of the new beta (ACE-5.4.9, TAO-1.4.9 and CIAO-0.4.9)
Hi, We are pleased to announce a new beta of ACE-5.4.9, TAO-1.4.9, and CIAO-0.4.9. The documentation for this beta kit will be available shortly. We are still working very hard on the x.5 release, which is scheduled to be released by the beginning of March if all goes well. We wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate, as always. We've also added a number of improvements to the various components in ACE, TAO and CIAO. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta is also available. We encourage you to download the new beta, use it with your applications, and let us know if you encounter any problems. Please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We also request that you take a look at $TAO_ROOT/docs/releasenotes for the status of various ongoing projects at the DOC groups of WashU, UCI, and Vanderbilt to move ACE+TAO+CIAO forward. Overviews of our recent progress and upcoming plans are available at $ACE_ROOT/NEWS $TAO_ROOT/NEWS $CIAO_ROOT/NEWS The overall success rates for the test results gathered from all our daily builds is 95.68% for the ACE tests and 88.6% for the TAO tests. Please see http://www.dre.v...

[ace-users] Announcing the release of the new beta (ACE-5.4.8, TAO-1.4.8 and CIAO-0.4.8)
[The following is on behalf of the PrismTech build-czars!] Hi, We are pleased to announce a new beta of ACE-5.4.8, TAO-1.4.8, and CIAO-0.4.8. We are currently working hard on the long-awaited x.5 release, which is slated to appear in early 2006. We therefore wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate as always. We've added a number of sub-setting improvements that reduce the static/dynamic footprint of ACE+TAO significantly (www.dre.vanderbilt.edu/Stats has all the details). We've also finally added support for Real-time CCM to CIAO and DAnCE. This beta is contains the results of our major footprint reduction effort that started in the summer of 2004. Between August 1st 2004 and October 14th 2005 the footprint reduction for the ORB_Init application has been 20%. Dependent on the parts of TAO you use the reduction can even be more. This reduction is inclusive all the extensions that have been made to TAO the last year. Interested users should check out http://www.dre.vanderbilt.edu/Stats/ for more details. Note that the footprint has increased slightly again due to emulated exceptions having been disabled in favour of native C++ exceptions in all stats builds. We have deprecated support for emulated exceptions since there are no sponsors for this configuration. If you require emulated exceptions please contact one of the companies listed in http://w...

[ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi,all I rebuild the ACE package according the instruction above,but get the same result. my platform_macros.GNU file has the following lines: templates = implicit include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU When i rebuild the ACE library,get the following compile errors: $ make inline=0 -j 2 -k -f GNUmakefile.ACE .... .... CC -mt -g -DSUN_CC_HAS_PVFC_BUG -I/export/home/hua/DevTools/ACE_wrappers -DACE_HAS_EXCEPTIONS -DACE_NO_INLINE -I.. -DACE_HAS_ACE_TOKEN -DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -c -KPIC -o .shobj/OS_NS_sys_stat.o OS_NS_sys_...

[ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, ACE VERSION: 5.4.3 HOST MACHINE and OPERATING SYSTEM: Solaris 10 x86 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): Sun Studio 9 (Sun CC 5.6) CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a platform- specific file, simply state which one]: #define ACE_HAS_STANDARD_CPP_LIBRARY 1 #define ACE_USES_STD_NAMESPACE_FOR_STDCPP_LIB 1 #include "ace/config-sunos5.9.h" CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless ...

TRSDOS II, version 4.2.0, 4.2.2, 4.2.4, 4.2.6 (or 4.3.x or 4.4)
Hi, Group I require a copy of the above DOS, but I need it _on disk_ as I do not have an emulator for the Model II that must be tested. Is there any possible sources of the OS on disk, or can you advise if the original 8" drive can be hooked to another device so that I can transfer an electronic copy to the disk to boot the machine? What other options do I have? Thanks L replying to my own post :-) I found an article here (http://www.tim-mann.org/trs80resources.html) where Tim describes a trick to rescue a disk's contents. This should be a workable solution...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi > > ACE VERSION: 5.4.3 > > > > HOST MACHINE and OPERATING SYSTEM: > > Solaris10 X86 > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > > Compiler: SUN CC 5.6 ^^^^^^^^^^^^^^^^^^^^^^^^ I don't think the DOC group supports this compiler anymore.. More particularly this compiler is buggy and you may land up with unresolved symbols even if you get past this part. My $0.02. Thanks Bala > > Make: ...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Johnny- > Ok, the problem is in platform_sunos5_sunc++.GNU, when a not known forte > version is found, it defaults to explicit. I am updating right now, for 4.2 > and 5.3 we default to explicit, for all others to implicit Is this necessary? I mean make it implicit by default. The explicit is not even supported, and has no chance to work cleanly. Why should we patch broken stuff. Just a thought? > Qinghuajin and other Forte 9 users, you can work around this by added the > following line to your platform_macros.GNU file. > templates = implicit This is until w...

Web resources about - [ciao-users] Utility library not being found on ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2 - comp.soft-sys.ace

Resources last updated: 3/5/2016 5:55:53 PM