f



Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2 #2

Hi Alex,

> What are OCI's plan's for a supported TAO 1.4 release and developer 
> guide?  Will this effect the release of the 1.3 guide?

This is an excellent question - I'm sure Malcolm Spence will pitch in
when he has a chance and I suspect that OCI will be supporting TAO 1.4
in due time.  None of the changes in TAO 1.4 should affect the
relevance of the info in the TAO 1.3 developer's guide - there's just
more new stuff to document as time permits.

Take care,

        Doug
0
schmidt7304 (285)
10/27/2003 9:15:53 PM
comp.soft-sys.ace 20326 articles. 1 followers. marlow.andrew (167) is leader. Post Follow

0 Replies
1465 Views

Similar Articles

[PageSpeed] 53

Reply:

Similar Artilces:

Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2
Hi Tom, > We are currently arm-wrestling with TAO-1.3.3 on VxWorks-5.5/Tornado-2.2 > built with non-native exceptions and with implicit templates. Implicit > templates are desirable since we are now using STL and those nested > templates make explicit instantiation almost impossible. Non-native > exceptions are important since native exceptions lead to a factor of 4.5 > increase in code size (!!). > > Implicit templates cause trouble with singletons, since the VxWorks-2.x > loader does not respect weakly-defined symbols, so one can not load > multiple modules which reference the same templated singleton. Our > workaround involves using RTTI and implementing a "singleton registry" > to enable proper singleton behavior. This strategy works for our > production code based on TAO-1.2.1, and hopefully we'll finish off our > move to TAO-1.3.3 sometime soon. > > I've mentioned this on-list once or twice, and had positive feedback on > incorporating fixes or changes to move working code into the TAO tree. > We haven't until recently had time to consider moving away from > TAO-1.2.1, so patches would not have helped. I'd like to post (working) > patches to the list for feedback, and I'd like to do this in time for > consideration to move this code into the next TAO release if deemed > appropriate. Either way we should have something to contribute to our > VxWorks br...

Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi Folks, It's been about a year since we released ACE 5.3 and TAO 1.3. We are therefore planning to release ACE 5.4 and TAO 1.4 by mid-December. The ACE+TAO x.3.5 beta that Venkita just announced will be the penultimate beta towards that goal. In addition to all the enhancements that he mentioned in the release notes, we also plan to add the following enhancements before the x.4 release: ---------------------------------------- .. ACE subsetting enhancements .. ORB footprint and compilation-time enhancements .. CORBA Security Service capabilities .. Load Balancing Service enhancements and bug fixes .. CIDL enhancements .. CIAO enhancements .. SCIOP fixes and enhancements .. Additional FT CORBA integration .. New Autoconf support .. Various fixes to parse-magic-bytes problems and problems with receiving GIOP message fragments. .. Impl Repo fixes ---------------------------------------- If there's something really important that you'd like to see go into the ACE+TAO x.4 release *and* you're willing to commit the time/resources necessary to ensure that this happens please let us know. Thanks, Doug A related question for OCI (and other companies supporting TAO I suppose): What are OCI's plan's for a supported TAO 1.4 release and developer guide? Will this effect the release of the 1.3 guide? Cheers, Alex. Douglas C. Schmidt wrote: >Hi Folks, > > It's been about a year since we rel...

[tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi We are happy to announce a new beta of ACE-5.3.5, TAO-1.3.5 and CIAO-0.3.5. This beta comes with new ORB level services that were developed over the past few months by folks at Washington University and University of Rhode Island. Please see the release notes attached with this email for more information. 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/releasenote.html for the status of various ongoing projects at the doc groups of WashU, UCI and Vanderbilt to move ACE+TAO+CIAO forward. 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. --------------------------------------------------------------- IMPORTANT INFORMATION FOR UNIX and LINUX USERS ============================================== Please note that $ACE_ROOT/lib directory also has to be added to the LD_LIBRARY_PATH environment variab...

Re: [ace-users] g++ 3.4.3 and ACE 5.5 & TAO 1.5
Hi, Please upgrade to ACE/TAO 1.5.3 which you can obtain from http://download.dre.vanderbilt.edu. Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl "M@uro!!" <mauro.gaddo@gmail.com> wrote in message news:<1161692263.239945.111960@m7g2000cwm.googlegroups.com>... > During compiling on HP-UX 11.11 with g++ i have the following error: > > g++ -DHAVE_CONFIG_H -I../.. -I.. -DACE_HAS_ACE_TOKEN > -DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -DHPUX_VERS=1111 -w -W -Wall > -Wpointer-arith -g -O2 -pthread -pipe -I. -I.. -MT > libACE_la-OS_NS_stdio.lo -MD -MP -MF .deps/libACE_la-OS_NS_stdio.Tpo -c > ../../ace/OS_NS_stdio.cpp -fPIC -DPIC -o .libs/libACE_la-OS_NS_stdio.o > ../../ace/OS_NS_stdio.cpp: In function `int ACE_OS::fprintf(FILE*, > const wchar_t*, ...)': > ../../ace/OS_NS_stdio.cpp:242: error: `::vfwprintf' has not been > declared > > Can someone helps me? > > Thanks!! > M. > ...

if time = 3 seconds, how do i set the values of the time steps 0,0.1,0.2,0.3,0.5,1.0,1.5,2.0,3.0,5.0 to -9999 from time =3 seconds
Hi &nbsp; I have 18 inputs (arrays) which contain certain statistics and if time&nbsp;&nbsp;= 3 seconds, set the values of time step 5.0 to -9999.0. &nbsp; I was wondering if there is an efficient way to do this without using a lot of case statements? &nbsp; Thank you. Hello AdrianT, it's not really clear to me what you want to do... I suspect: you have an array containing values and you want to output them with a fixed timing of 3 seconds: you should use a for loop autoindexing trough your array and sending the value to your indicator/output/whatever. Put a "wait for next multiple" into your for loop. Or do you want to have a minimum time delay of 3 seconds? Again use a for loop, get the time value and use a InRange&amp;Coerce with minimum set to 3 seconds... Or you should explain more precisely what you need... Hi Thanks for that. Let me explain. &nbsp; The time may vary. Let me give an example. if time&nbsp; = 2.1, I want to set the time step's &nbsp;3.0 and 5.0's values to -9999.0. if the time =0.1 seconds then I want to set 0.2,0.3, 0.5 etc values to -9999.0 etc .................................................................... &nbsp; Can you please help? Thank you. Hello TUDS, do you use different accounts/nicknames ? Well, that's easy, at least for a sorted array: Search for your time-value in the array (Threshold 1D array). Fill all elements from that index till the end with your "error...

[ace-users] ACE+TAO+CIAO
Hi all, We are pleased to announce the latest ACE+TAO+CIAO beta. This beta has been tagged ACE+TAO+CIAO-5_5_6. The main difference between this release and x.5.5 is that the ACE exception macros (except for ACE_THROW_RETURN and ACE_THROW_SPEC) have been removed from all TAO and CIAO code. It is available from the same download location as per the previous release. http://download.dre.vanderbilt.edu/ The doxygen documentation for the beta is also available. Included with this beta, besides the packages combined of sources and generate makefiles, we also provide source only packages for the group of users which use MPC to generate their own makefiles. 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 proper 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 96% for the ACE tests and 92% for the TAO tests. Please see: http://ww...

[ace-users] Tests failed : ACE 5.5.2 - AIX 5.3
Hi, My first mail before my message in the group failed (my subscription was not activated). The PRF below describes my problems. I can compile and link but several ACE's tests fail. I only use ACE library and only compile it by cd'ing in the ace directory before running make. I already made some fixes described below to compile and to link the library. I'm not abble to interpret the faild tests to identify the problem source or area. I didn't find the scoreboard before my mail. I see that several tests fails for all compilations on AIX. I try to reassure myself by looking these results, it's not only for my configuration. But it's a daily build with last development version. For the 5.5.2 stable version they should probably not fail ? Regards, PO Houot. ACE VERSION: 5.5.2 HOST MACHINE and OPERATING SYSTEM: bash-3.00$ uname -a AIX localhost 3 5 0040983B4C00 unknown unknown AIX bash-3.00$ oslevel -r 5300-05 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: Same as host COMPILER NAME AND VERSION (AND PATCHLEVEL): bash-3.00$ g++ -v Using built-in specs. Target: powerpc-ibm-aix5.3.0.0 Configured with: ../gcc-4.1.1/configure --disable-nls Thread model: aix gcc version 4.1.1 This compiler is installed from packages provided by UCLA AIX Software library THE $ACE_ROOT/ace/config.h FILE : bash-3.00$ more $ACE_ROOT/ace/config.h #include "ace/config-aix-5.x.h" T...

Re: [ace-users] compiling issue on Sun 5.8 with ACE 5.3 #2 #3
Hi, Are we still talking about ACE problems, looks now that you have a problem in your application code. What for code is in Global.h on line 43? Johnny "Manish Jain" <mjain@itangel.com> wrote in message news:<00a101c34b71$cbf5b110$5ec809c0@angels.com>... > Can you please also lookint to the following error as well: > > > Compiling /v/sbansal/out/temp/playground/ExecAgent.o > /opt/SUNWspro/bin/CC -temp=/v/sbansal/out/temp -g -c -Bdynamic -ldl > -mt -libr > ary=iostream,rwtools7 -DACE_HAS_EXCEPTIONS -o > /v/sbansal/out/temp/playground/Ex > ecAgent.o -I/v/sbansal/out/include/playground > -I/exe/tibco/tibrv5/include -I/v/s > bansal/out/include/common -I/v/sbansal/out/include/utils > -I/v/sbansal/out/includ > e/transport -I/usr/ACE_wrappers src/ExecAgent.cc > "/v/sbansal/out/include/playground/Global.h", line 43: Warning: String > literal c > onverted to char* in initialization. > "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 316: Error: A > typedef name > cannot be used in an elaborated type specifier.. > "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 317: Error: A > typedef name > cannot be used in an elaborated type specifier.. > "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 318: Error: A > typedef name > cannot be used in an elaborated type specifier.. > "/opt/SUNWspro/WS6U2/include/CCios/rlocks.h"...

[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,...

g++ 3.4.3 and ACE 5.5 & TAO 1.5
During compiling on HP-UX 11.11 with g++ i have the following error: g++ -DHAVE_CONFIG_H -I../.. -I.. -DACE_HAS_ACE_TOKEN -DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -DHPUX_VERS=1111 -w -W -Wall -Wpointer-arith -g -O2 -pthread -pipe -I. -I.. -MT libACE_la-OS_NS_stdio.lo -MD -MP -MF .deps/libACE_la-OS_NS_stdio.Tpo -c .../../ace/OS_NS_stdio.cpp -fPIC -DPIC -o .libs/libACE_la-OS_NS_stdio.o .../../ace/OS_NS_stdio.cpp: In function `int ACE_OS::fprintf(FILE*, const wchar_t*, ...)': .../../ace/OS_NS_stdio.cpp:242: error: `::vfwprintf' has not been declared Can someone helps me? Thanks!! M. Hi Mauro, >During compiling on HP-UX 11.11 with g++ i have the following error: > > g++ -DHAVE_CONFIG_H -I../.. -I.. -DACE_HAS_ACE_TOKEN >-DACE_HAS_ACE_SVCCONF -DACE_BUILD_DLL -DHPUX_VERS=1111 -w -W -Wall >-Wpointer-arith -g -O2 -pthread -pipe -I. -I.. -MT >libACE_la-OS_NS_stdio.lo -MD -MP -MF .deps/libACE_la-OS_NS_stdio.Tpo -c >../../ace/OS_NS_stdio.cpp -fPIC -DPIC -o .libs/libACE_la-OS_NS_stdio.o >../../ace/OS_NS_stdio.cpp: In function `int ACE_OS::fprintf(FILE*, >const wchar_t*, ...)': >../../ace/OS_NS_stdio.cpp:242: error: `::vfwprintf' has not been >declared > >Can someone helps me? I took a look at http://www.dre.vanderbilt.edu/scoreboard/integrated.html and I don't see any HPUX builds that use G++, so you may need to either figure this out yourself (probably a missing header file so...

[ace-users] Re: How can I use ACE(Latest Beta Kit) for AIX version 5.3/5.2 and VisualAge C++ 7.0/6.0 for AIX on machine IBM P690? \
Hi Oliana, Thanks very much for your email. Please make sure to send all questions related to TAO or ACE to the ACE mailing list or ACE+TAO newsgroup, rather than to me directly since I travel frequently and often don't have ready access to email. See http://www.cs.wustl.edu/~schmidt/ACE-mail.html for more info on how to access these resources. > I want to use ACE.tar.bz2(Latest Beta Kit) on AIX version 5.3,Now > I'm writing application program base on ACE.tar.bz2 (Latest Beta > Kit) and testing ACE.tar.bz2(Latest Beta Kit) on AIX version 5.2 for > IBM P690 and using VisualAge C++ 6.0 and VisualAge C++ 7.0,It?s very > strange ,the ACE.tar.bz2 was compiled successful,But the application > program can?t be compiled success,There are a lot of problems.It has > reported a lot of mistakes of STL head file in VisualAge ,and then > It told me there are something wrong in VisualAge C++ 6.0/7.0's head > file.I don't know why,Then ,I written testing code ,only have tested > VisualAge C++ 6.0 and VisualAge C++ 7.0 for AIX version 5.2's head > file already,the compiler was compiling and running up to snuff,no > mistake in head file.And you know ,When I put the same application > program and ACE.tar.bz2(Latest Beta Kit) in Redhatlinux for PC and > Turbo linux for IBM eServe BladeCenter, there are no mistakes,and > It?s normally compiling and running so fast.So,I don?t know why,what > happ...

RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 #2
Hi, Sorry, we are using DevStudio 7.1 (2003) ~ Ishay Software Architect Onigma Ltd. Tel: +972-3-6877315 Fax: +972-3-6877128 Mobile: +972-54-2325090 Email: ishay@onigma.com -----Original Message----- From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] Sent: Tuesday, March 07, 2006 2:42 PM To: 'Ishay Green'; ace-users@cs.wustl.edu Subject: RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 Hi, > ACE VERSION: 5.5 Thanks for using the PRF form. > HOST MACHINE and OPERATING SYSTEM: > > Intel, WindowsXp, Windows 2003 An important bit information is missing, which compiler did you use. > AREA/CLASS/EXAMPLE AFFECTED: > The only problem we encountered was a compilation error > when construction ACE_Time_Value. > > The ACE_Time_Value cannot be constructed anymore from an integer. > > For example: ACE_Time_Value( 5 ) --> Compile error Great to hear things work without problems. This errors sounds strange, we do have test cases like this in tests/Time_Value_Test.cpp. We do have made all constructors of ACE_Time_Value explicit. As a result if you have a method that expects a ACE_Time_Value&, you just can't pass for example 5, you have to pass an ACE_Time_Value(5). Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl ...

Re: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 #2
Hi Ishay, >> Sorry, we are using DevStudio 7.1 (2003) We use this too. Please see ACE_ROOT/tests/Time_Value_Test.cpp for lots of examples that use ACE_Time_Value with integers. Please see if this works on your OS/compiler platform. Thanks, Doug >> ~ Ishay >> >> Software Architect >> Onigma Ltd. >> Tel: +972-3-6877315 >> Fax: +972-3-6877128 >> Mobile: +972-54-2325090 >> Email: ishay@onigma.com >> >> -----Original Message----- >> From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] >> Sent: Tuesday, March 07, 2006 2:42 PM >> To: 'Ishay Green'; ace-users@cs.wustl.edu >> Subject: RE: [ace-users] [ACE 5.5] Upgrade from ACE 5.4.7 to ACE 5.5 >> >> Hi, >> >> > ACE VERSION: 5.5 >> >> Thanks for using the PRF form. >> >> > HOST MACHINE and OPERATING SYSTEM: >> > >> > Intel, WindowsXp, Windows 2003 >> >> An important bit information is missing, which compiler did you use. >> >> > AREA/CLASS/EXAMPLE AFFECTED: >> > The only problem we encountered was a compilation error >> > when construction ACE_Time_Value. >> > >> > The ACE_Time_Value cannot be constructed anymore from an integer. >> > >> > For example: ACE_Time_Value( 5 ) --> Compile error >>...

RE: [ace-users] compiling issue on Sun 5.8 with ACE 5.3 #2 #2
This is a multi-part message in MIME format. ------=_NextPart_000_00A2_01C34B9F.E5ADED10 Content-Type: multipart/alternative; boundary="----=_NextPart_001_00A3_01C34B9F.E5ADED10" ------=_NextPart_001_00A3_01C34B9F.E5ADED10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Can you please also lookint to the following error as well: Compiling /v/sbansal/out/temp/playground/ExecAgent.o /opt/SUNWspro/bin/CC -temp=/v/sbansal/out/temp -g -c -Bdynamic -ldl -mt -libr ary=iostream,rwtools7 -DACE_HAS_EXCEPTIONS -o /v/sbansal/out/temp/playground/Ex ecAgent.o -I/v/sbansal/out/include/playground -I/exe/tibco/tibrv5/include -I/v/s bansal/out/include/common -I/v/sbansal/out/include/utils -I/v/sbansal/out/includ e/transport -I/usr/ACE_wrappers src/ExecAgent.cc "/v/sbansal/out/include/playground/Global.h", line 43: Warning: String literal c onverted to char* in initialization. "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier.. "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier.. "/opt/SUNWspro/WS6U2/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier.. "/opt/SUNWspro/WS6U2/include/CCios/rlocks.h", line 50: Error: A typedef name can not be used in an elaborated type specifier.. &q...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Johnny- > > > > 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. > > I missed the compiler version. But, Forte 8 gives output of SUN C++ 5.5. Hmm.. Then I could be wrong. Then we need to fix the config files for SUN CC to use implicit templates for anything including and above FORTE 8. > Maybe we should add a check to one of the Sun config file to check the SUN > CC version? Something like: > > // Forte 6 is the oldest Forte version we sopport > #if __SUNPRO_CC < 0x530 > # error Your SUN CC compiler is too old, upgrade to a newer version > #endif Much better. Thanks Bala ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > >> It's almost up. There are some issues with installing software as > >> we don't have the media in a compatible form yet. We also don't > >> have Sun CC, and we need to purchase a licence if we need to > >> support Sun CC. > > Ok, that's fine - thanks for the update. I think some other folks > (e.g., LMCO ATL and Remedy) have Solaris 9/10 and Sun CC, so we may > not need to worry about running Sun CC on our machine. Johnny/Gautam, > can you folks please confirm/deny whether you've got Sun CC on Solaris > 9/10? We are running SunCC (Forte 8) on Solaris 8. We have Solaris 9 available, but have had no time to install it on our build system. Johnny ...

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: GNU make 3.80 > > > > CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a > > platform- > > specific file, simply state which one]: > > #include "ace/config-sunos5.9.h" > > > > CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU > > (unless > > this isn't used in this case, e.g., with Microsoft Visual C++): > > include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU > > > > > > CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features > > (used by MPC when you generate your own makefiles): > > > > AREA/CLASS/EXAMPLE AFFECTED: > > [What example failed? What module failed to compile?] > > "ace/OS_NS_sys_stat.cpp" > > > > DOES THE ...

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. I missed the compiler version. But, Forte 8 gives output of SUN C++ 5.5. Maybe we should add a check to one of the Sun config file to check the SUN CC version? Something like: // Forte 6 is the oldest Forte version we sopport #if __SUNPRO_CC < 0x530 # error Your SUN CC compiler is too old, upgrade to a newer version #endif Johnny ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
> Ok. Steve, could you maybe make clear with the build names > which builds use explicit templates? I'll try to get this clarified. > Explicit templates in TAO are known to be broken at this > moment. None of the tests at Riverace try to build TAO. -Steve ...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi, > > > 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. > > > > I missed the compiler version. But, Forte 8 gives output of > SUN C++ 5.5. 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 Qinghuajin and other Forte 9 users, you can work around this by added the following line to your platform_macros.GNU file. templates = implicit Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl ...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Jin, Thanks for using the PRF. >> 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) As we've mentioned several times now, we don't have this compiler installed yet on this hardware platform, so if you want things to be fixed soon I recommend you figure out what's going wrong and send us the patches. Otherwise, please contact one of the companies that provides commercial support for ACE at http://www.cs.wustl.edu/~schmidt/commercial-support.html Thanks, Doug >> 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 >> this isn't used in this case, e.g., with Microsoft Visual C++): >> >> templates = implicit >> include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU >> >> >> CONTENTS OF $ACE_ROOT/bin/MakeP...

[ace-bug] Compile ACE 5.4 on AIX 5.2 with gcc 3.3.2
Failed to build ACE 5.4 on AIX 5.2 with gcc3.3.2 Used config-aix5.1.h and platform_aix_g++.GNU I failed with ACE5.1, 5.3 too, so I tried 5.4. Does anybody know IF it works ? Could it help to build my own AIX5.2 gcc ? (my gcc 3.3.2 is binary AIX 5.1 but it worked fine for Non-ACE- applications) Do I have to use IBM Visual C++ Compiler ? Any suggestions would be helpful. ACE VERSION: 5.4 HOST MACHINE and OPERATING SYSTEM: RS/6000, 32-bit-kernel mode, AIX5.2 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc 3.3.2 (binary distribution) CONTENTS OF $ACE_ROOT/ace/config.h: // config-aix5.1.h,v 1.5 2003/12/16 17:49:48 elliott_c Exp // // Config file for AIX 5.1 // This define is needed for building with Visual Age C++ 5 in incremental // mode. In the batch mode build, platform_aix_ibm.GNU sets it. The incremental // mode compiler won't be supported after ACE 5.3, so this will also go away // in that timeframe, so don't worry about future AIX versions. #if !defined (ACE_AIX_VERS) # define ACE_AIX_VERS 501 #endif #include "ace/config-aix-4.x.h" // AIX 5.1 has AIO, but it doesn't have the same API as other POSIX // systems, and the semantics of operations are a bit different. Will take // some real work to get this going. //#define ACE_HAS_AIO_CALLS // I think this is correct, but needs to be verified... -Steve Huston #define ACE_HAS_SIGTIMEDWAIT // AIX 5....

RE: KRB5 1.5 or 1.6 compiled on AIX 5.2/5.3 #3
Thanks. The problem also exist using GNU ld on AIX too. See below: make[2]: Entering directory `/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src/lib/rpc' making all in lib/rpc/unit-test... make[3]: Entering directory `/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src/lib/rpc/unit-test' cc -L../../../lib -blibpath:/usr/local/kerberos/lib::/usr/lib:/lib -g -qhalt=e -O -D_THREAD_SAFE -o client client. o rpc_test_clnt.o \ -lgssrpc -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lkrb5support -lpthreads ld: 0706-006 Cannot find or open library file: -l k5crypto ld:open(): No such file or directory ld: 0706-006 Cannot find or open library file: -l com_err ld:open(): No such file or directory ld: 0706-006 Cannot find or open library file: -l krb5support ld:open(): No such file or directory make[3]: *** [client] Error 255 make[3]: Leaving directory `/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src/lib/rpc/unit-test' make[2]: *** [all-recurse] Error 1 make[2]: Leaving directory `/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src/lib/rpc' make[1]: *** [all-recurse] Error 1 make[1]: Leaving directory `/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src/lib' make: *** [all-recurse] Error 1 root@aoctoolbox:/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src:> whence ld /usr/local/bin/ld root@aoctoolbox:/usr/sys/inst.images/MIT-Kerberos/krb5-1.6/5.3/src:> ld -v GNU ld version 2.16 Lamar -----Original Message----- From: Russ Al...

RE: [ace-users] Re: ACE 5.4.0 won't compile after GCC upgrade (3.3.3 -> 3.4.3)
Hi Tom, > > > The "resolution" was to upgrade to ACE-5.4.3 or later, which has > > > code fixes to help with the newer compiler. Not sure how > much would > > > need to change, but you may be able to inspect the differences in > > > that part of the code wrt the newer ACE release to backport the > > > fixes. > > Thanks, I've downloaded and am building. Is ACE-5.4.3 the latest > > production release ? > > Well, the definition of "production release" for ACE is a bit murky > imho. Production release is one with 2 numbers. E.g., 5.4 > The developers on this list (almost) always recommend using the > latest package, which is typically labeled a "beta release". > The latest > would be 5.4.4. The developers always recommend *not* using the > "production release", since the next release labeled "beta" > is always a bug-fix-only release. I believe I qualify as a "developer", but have a different take. Production releases are tested well, and often better than the BFO beta. There may be fixes in BFO, but there may be additional bugs also - it happened at 5.4.1. For those wishing to adopt a version of ACE and stick with it, you'll need a version you can get support (fixes and advice) for. For example, Riverace supports releases (e.g., 5.4) and fix kits that Riverace releases for those (i...

Web resources about - Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2 #2 - comp.soft-sys.ace

Resources last updated: 3/22/2016 10:54:26 PM