f



Re: [ace-bugs] Many compiler warnings when compiling 5.4.4 with gcc 3.4.1

Hi Peter,

        Thanks for using the PRF.

>>     ACE VERSION: 5.4.4
>> 
>>     HOST MACHINE and OPERATING SYSTEM: 
>>         If on Windows based OS's, which version of WINSOCK do you
>>         use?:
>> 
>> 	Solaris 2.8
>> 
>>     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>>     COMPILER NAME AND VERSION (AND PATCHLEVEL):
>> 
>>     CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a platform-
>>     specific file, simply state which one]:
>> 
>> // The following configuration file is designed to work for SunOS 5.8
>> // (Solaris 8) platforms using the SunC++ 4.x, 5.x, 6.x, or g++ compilers.
>> 
>> #ifndef ACE_CONFIG_H
>> 
>> #define ACE_HAS_NONSTATIC_OBJECT_MANAGER 1
>> 
>> // ACE_CONFIG_H is defined by one of the following #included headers.
>> 
>> // #include the SunOS 5.8 config, then add any local updates below.
>> #include "ace/config-sunos5.8.h"
>> 
>> #define ACE_LACKS_ACE_IOSTREAM		1
>> #define ACE_LACKS_IOSTREAM_TOTALLY	1
>> #define ACE_NTRACE			0
>> 
>> // gcc doesn't define the following types 
>> 
>> typedef long          t_scalar_t;  /* historical versions */
>> typedef unsigned long t_uscalar_t;
>> typedef void          *timeout_id_t;
>> typedef	long	      blksize_t;	/* used for block sizes */
>> 
>> #endif /* ACE_CONFIG_H */
>> 
>> 	
>>     CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless
>>     this isn't used in this case, e.g., with Microsoft Visual C++):
>> 
>> 	linked to platform_sunos5_g++.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?]
>> 
>> 	Many many identical warnings when compiling ace classes
>> 
>>     DOES THE PROBLEM AFFECT:
>>         COMPILATION?
>> 	   Warnings during compilation
>>         LINKING?
>>             On Unix systems, did you run make realclean first?
>>         EXECUTION?
>>         OTHER (please specify)?
>> [Please indicate whether ACE, your application, or both are affected.]
>> 
>>     SYNOPSIS:
>> [Brief description of the problem]
>> 
>> 	when compiling ace, the compiler produces many warnings about the
>> fact that ACE_Time_Value::set( const timeval& t ) is used before it is
>> declared inline
>> 
>>     DESCRIPTION:
>> [Detailed description of problem.  Don't just say "<blah>
>> doesn't work, here's a fix," explain what your program does
>> to get to the <blah> state. ]
>> 	
>> 	An example warning is:
>> In file included from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Time_Value.h:382,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/OS_NS_unistd.h:29,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/ACE.inl:4,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/ACE.h:821,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Memory_Pool.h:18,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Malloc.h:389,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Malloc_T.h:18,
>>                  from
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Local_Name_Space.h
>> :20,
>>                  from Local_Name_Space.cpp:1:
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Time_Value.inl:73:
>> warning: `void ACE_Time_Value::set(const timeval&)' was used before it was
>> declared inline
>> /vob/cnsar/thin/destiny/libext/ACE-5.4.4/ACE_wrappers/ace/Time_Value.h:132:
>> warning: previous non-inline declaration here
>> 
>> 	The problem is that one of the constructors of ACE_Time_Value
>> calls set(). The constructor appears before the inline definition of
>> set() in the file. At the point where the constructor is defined, the
>> compiler doesn't know that set() will be defined as inline later.
>> 
>>     REPEAT BY:
>> [What you did to get the error; include test program or session
>> transcript if at all possible.  ]
>> 
>>     SAMPLE FIX/WORKAROUND:
>> [If available ]
>> 
>> 	I believe that moving the inline definition of
>> ACE_Time_Value::set( const timeval& t )
>> from its current location in Time_Value.inl to a location
>> before the ACE_Time_Value constructor that uses it
>> will fix the problem.

Fixed, 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

0
Douglas
3/10/2005 5:02:53 AM
comp.soft-sys.ace 20326 articles. 1 followers. marlow.andrew (167) is leader. Post Follow

0 Replies
543 Views

Similar Articles

[PageSpeed] 13

Reply:

Similar Artilces:

[ace-bugs] Many compiler warnings when compiling 5.4.4 with gcc 3.4.1
ACE VERSION: 5.4.4 HOST MACHINE and OPERATING SYSTEM: If on Windows based OS's, which version of WINSOCK do you use?: Solaris 2.8 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a platform- specific file, simply state which one]: // The following configuration file is designed to work for SunOS 5.8 // (Solaris 8) platforms using the SunC++ 4.x, 5.x, 6.x, or g++ compilers. #ifndef ACE_CONFIG_H #define ACE_HAS_NONSTATIC_OBJECT_MANAGER 1 // ACE_CONFIG_H is defined by one of the following #included headers. // #include the SunOS 5.8 config, then add any local updates below. #include "ace/config-sunos5.8.h" #define ACE_LACKS_ACE_IOSTREAM 1 #define ACE_LACKS_IOSTREAM_TOTALLY 1 #define ACE_NTRACE 0 // gcc doesn't define the following types typedef long t_scalar_t; /* historical versions */ typedef unsigned long t_uscalar_t; typedef void *timeout_id_t; typedef long blksize_t; /* used for block sizes */ #endif /* ACE_CONFIG_H */ CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless this isn't used in this case, e.g., with Microsoft Visual C++): linked to platform_sunos5_g++.GNU CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features (used by MPC when you generate your own...

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

[ace-bugs] Error during compilation ACE-5.4.4 + TAO-1.4.4
--001485f99caa0c8d8c0475c7d5ee Content-Type: text/plain; charset=UTF-8 Hello,I'm trying to compile ACE-5.4.4+TAO-1.4.4 and I got an error while I trying to compile it: /home/mchacon/nextgen/extra/ACE_wrappers/ace/os_include/os_stropts.h:64:28: error: stropts.h: No such file or directory I use Fedora 11 with gcc 4.4.1 and I was searching in google and I found that there are some is issue about strems buffer in Linux, please take a look these links: http://www.archivum.info/comp.soft-sys.ace/2008-04/00069/Re:_[tao-users]_PRF:_Autobuild_on_Fedora_Rawhide_(GCC_4.3.0)_is_a_no-go https://bugzilla.redhat.com/show_bug.cgi?id=439403 Is there any workaround to fix it? I have the header in Fedora Core 3, but I trying to make it work in Fedora 11, Is it possible? Thanks and Regards! Salu2... masch... --001485f99caa0c8d8c0475c7d5ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello,<div>I&#39;m trying to compile ACE-5.4.4+TAO-1.4.4 and I got an error= while I trying to compile it:</div><div><br></div><div>/home/mchacon/nextg= en/extra/ACE_wrappers/ace/os_include/os_stropts.h:64:28: error: stropts.h: = No such file or directory</div> <div><br></div><div>I use Fedora 11 with gcc 4.4.1 and=C2=A0I was searching= in google and I found that there are some is issue about strems buffer in = Linux, please take a look these links:</div&g...

RE: [ace-users] Re: ACE 5.4.0 won't compile after GCC upgrade (3.3.3 -> 3.4.3) #2
Hi J.T., Right... The issue is a bit odd... Here's the check I added for ACE: dnl This check was added to work around a system-supplied header dnl (/usr/include/netinet/ip.h) that won't compile with Visual Age C++ dnl unless the _NO_BITFIELDS preprocessor macro is defined. The comments dnl there recommend use of _NO_BITFIELDS (and recode where needed to allow dnl that), but we won't just turn it on. Check to see if it's needed. Note dnl that this check is related to headers but done before we really know if dnl the header is present. Thus, if the bare compile fails, but succeeds dnl with _NO_BITFIELDS, set the flag, else leave things alone. -Steve -- Steve Huston, Riverace Corporation Adding Service to Open Source Software ACE book info at http://www.riverace.com/acebooks/ > -----Original Message----- > From: J.T. Conklin [mailto:jtc@acorntoolworks.com] > Sent: Wednesday, April 13, 2005 2:21 PM > To: Colm McHugh > Cc: Steve Huston; ace-users@cs.wustl.edu > Subject: Re: [ace-users] Re: ACE 5.4.0 won't compile after > GCC upgrade (3.3.3 -> 3.4.3) > > > Colm McHugh <cmchugh@callixa.com> writes: > >>Sure... Why do you say <sys/machine.h> is a prerequisite for > >><netinet/tcp.h>? I addressed a problem related to this in > the autoconf > >>support for AIX that'll go in the next beta, but it doesn't involve...

RE: [ace-users] Re: ACE 5.4.0 won't compile after GCC upgrade (3.3.3 -> 3.4.3) #2
Hi Colm, Ok, thanks for that explanation. I solved this a different way for a similar problem that showed up with Visual Age C++ on AIX 5.2... When the 5.4.5 beta comes out, please try this again and hopefully no further workarounds will be needed. Thanks, -Steve -- Steve Huston, Riverace Corporation Adding Service to Open Source Software ACE book info at http://www.riverace.com/acebooks/ > -----Original Message----- > From: Colm McHugh [mailto:cmchugh@callixa.com] > Sent: Wednesday, April 13, 2005 1:05 PM > To: Steve Huston > Cc: ace-users@cs.wustl.edu > Subject: Re: [ace-users] Re: ACE 5.4.0 won't compile after > GCC upgrade (3.3.3 -> 3.4.3) > > > > >Sure... Why do you say <sys/machine.h> is a prerequisite for > ><netinet/tcp.h>? I addressed a problem related to this in > the autoconf > >support for AIX that'll go in the next beta, but it doesn't involve > >machine.h. > > > Hi Steve, > > that statement is based on the compilation sequence shown > below (done on > an AIX 5.2): > > $ cat t2.cpp > #include <sys/machine.h> > #include <netinet/tcp.h> > int main() > {} > $ g++ t2.cpp > $ cat t1.cpp > #include <netinet/tcp.h> > int main() > {} > $ g++ t1.cpp > In file incl...

[ace-users] Re: ACE 5.4.0 won't compile after GCC upgrade (3.3.3 -> 3.4.3)
Hi Tom, > Well, the definition of "production release" for ACE is a bit murky > imho. Please see http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/ACE-development-process.html for the canonical definition of terms. If there's something unclear there please let me know and I'll fixit. > The developers on this list (almost) always recommend using the > latest package, which is typically labeled a "beta release". Right, the reason we do that is because the "latest release" (which is most commonly a beta release) is the only thing the DOC group developers "support". > 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. So I usually use the x.x.1 > release (the BFO release) but would probably recommend using 5.4.4 > on any platform, as do the developers. I think you probably know this already, but for the benefit of others on the mailing list the DOC grou doesn't actually support *anything* officially for non-sponsors, i.e., our work is all on a "best effort or no effort at all" basis, as per the explanation in http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/ACE-bug-process.html However, some companies like Riverace, OCI, PrismTech, etc. use our "official" (i.e., non-beta) releases as the basis f...

[ace-users] Re: Error while ACE 5.3.1 or 5.4.1 compiling and installing by MinGW 3.3.3
Hi Vitaly, Please upgrade to ACE 5.4.4, which you can download from http://deuce.doc.wustl.edu/Download.html since I think that is more likely to work with MinGW 3.3.3. Johnny, can you confirm/deny this please? Thanks, Doug >> Hi, >> I have installed MinGW packages: >> >> binutils-2.13.90-20030111-1.tar.gz >> gcc-core-3.3.3-20040217-1.tar.gz >> gcc-g++-3.3.3-20040217-1.tar.gz >> mingw-runtime-3.3.tar.gz >> w32api-2.5.tar.gz >> >> Also I've configured environment due to ACE-INSTALL.html according >> MinGW compiler. OS: WinXP SP2. >> >> $ACE_ROOT=F:\ACE531 >> >> I get next compiling error: >> F:\ACE531\ace>gmake >> gmake.EXE[1]: Entering directory `F:/ACE531/ace' >> d:\Utils\Unix\diff.EXE: -: Invalid argument >> gmake.EXE[1]: Leaving directory `F:/ACE531/ace' >> gmake.EXE[1]: Entering directory `F:/ACE531/ace' >> d:/Utils/Unix/gmake.EXE -f Makefile.dirs SUBDIR_TARGET=all >> RMCast.subdir >> gmake.EXE[2]: Entering directory `F:/ACE531/ace' >> d:/Utils/Unix/gmake.EXE -f Makefile -C RMCast all >> gmake.EXE[3]: Entering directory `F:/ACE531/ace/RMCast' >> Installing libACE_RMCast.dll -> F:\ACE531/ace >> d:\Utils\Unix\cp.EXE: F:ACE531aceRMCast/libACE_RMCast.dll: No such >> file or directory >> Installing libACE_RMCa...

Re: [ace-users] Re: ACE 5.4 compiling problems with g++ 3.4.3
Hi > First, please use the problem-report-form when asking questions. ACE 5.4 is > not supported with newer GCC versions. All these issues are resolved in the > upcoming x.4.3 release. > > For the time being, try to add the following to your config.h > > # if (__GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 4)) > # define ACE_EXPLICIT_TEMPLATE_DESTRUCTOR_TAKES_ARGS > # endif /* __GNUC__ >= 3.4 */ > > You are correct, the download link doesn't work. Bala, do you have an idea > what is happening with the downlo...

[ace-users] Re: Compiling ACE 5.4 with gcc 3.4.2 (fc3)
Hi, Thanks for using the PRF. >> ACE VERSION: 5.4 Please upgrade to ACE 5.4.4, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "Latest beta version". This should fix all the problems you've run into with GCC 3.4.2. If not, please let us know what else remains. Thanks, Doug >> HOST MACHINE and OPERATING SYSTEM: >> Linux 2.6.9-1.667 (Fedora Core 3) >> >> COMPILER NAME AND VERSION (AND PATCHLEVEL): g++ (GCC) 3.4.2 (Red Hat >> 3=2E4.2-6.fc3) >> >> CONTENTS OF $ACE_ROOT/ace/config.h: symbolic link to >> $ACE_ROOT/ace/config-linux.h >> I have not edited the file. >> >> CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU : >> symbolic link to $ACE_ROOT/include/makeinclude/platform_linux.GNU >> I have not edited the file. >> >> DOES THE PROBLEM AFFECT: >> COMPILATION? YES >> >> DESCRIPTION : >> I am a very neewbie and if my problem isn't a real one, I apologize by >> advance. But I spent a lot a time to find the solution in this forum >> but I can't find it :( >> >> So, here is the decription, in a first step I applied modification in >> the file $ACE_ROOT/ace/Global_Macros.h as descibed here : >> url=3D<http://groups-beta.google.com/group/comp.soft-sys.ace/browse_frm/thr= >> e...

Re: [ace-users] FYI: Compiler warnings with ACE 5.4.4 and g++ 4.0-20050213
Hi Lothar, Fixed, thanks! Doug >> in order to evaluate if we tapped onto a compiler problem I compiled our code >> with one of the g++ snapshots available (4.0-20050213). I noticed some >> compiler warnings that I wanted to share: >> >> As part of compiling our application we used the following warning switches >> for g++: >> -W -Wall -Wpointer-arith -Wno-uninitialized -Woverloaded-virtual -Wcast-align >> -Wwrite-strings -Wcomments >> >> /opt2/ACE_wrappers/TAO/tao/Collocation_Proxy_Broker.h:45: warning: 'class >> TAO::Collocation_Proxy_Broker' has virtual functions but non-virtual >> destructor >> /opt2/ACE_wrappers/ace/Signal.h:274: warning: 'class ACE_Sig_Handler' has >> virtual functions but non-virtual destructor >> /opt2/ACE_wrappers/ace/Signal.h:441: warning: 'class ACE_Sig_Handlers' has >> virtual functions but non-virtual destructor >> >> Lothar >> -- >> Lothar Werzinger Dipl.-Ing. Univ. >> framework & platform architect >> Xcerla Corporation >> 275 Tennant Avenue, Suite 202 >> Morgan Hill, Ca 95037 >> email: lothar@xcerla.com >> phone: +1-408-776-9018 >> -- Dr. Douglas C. Schmidt, Professor TEL: (615) 343-8197 Electrical Engineering and Computer Science FAX: (6...

[ace-users] Re: Compiling ACE 5.4 with gcc 3.4.2 (fc3) #2
Hi, Thanks for using the PRF form. ACE 5.4 doesn't work with GCC 3.4.2, you will end up with much more problems. We recommend you to upgrade to the x.4.4 version which you can obtain from http://deuce.doc.wustl.edu/Download.html Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl "Syn" <syn_net@noos.fr> wrote in message news:<1110289867.262543.50690@l41g2000cwc.googlegroups.com>... ACE VERSION: 5.4 HOST MACHINE and OPERATING SYSTEM: Linux 2.6.9-1.667 (Fedora Core 3) COMPILER NAME AND VERSION (AND PATCHLEVEL): g++ (GCC) 3.4.2 (Red Hat 3.4.2-6.fc3) CONTENTS OF $ACE_ROOT/ace/config.h: symbolic link to $ACE_ROOT/ace/config-linux.h I have not edited the file. CONTENTS OF $ACE_ROOT/include/makeinclude/platform_macros.GNU : symbolic link to $ACE_ROOT/include/makeinclude/platform_linux.GNU I have not edited the file. DOES THE PROBLEM AFFECT: COMPILATION? YES DESCRIPTION : I am a very neewbie and if my problem isn't a real one, I apologize by advance. But I spent a lot a time to find the solution in this forum but I can't find it :( So, here is the decription, in a first step I applied modification in the file $ACE_ROOT/ace/Global_Macros.h as descibed here : url=<http://groups-beta.google.com/group/comp.soft-sys.ace/browse_frm/thread /b1c8e54cfa298f4b?tvc=1&q=gcc+3.4> The compilation can go on and I obtained ...

[ace-users] ACE 5.4.0 won't compile after GCC upgrade (3.3.3 -> 3.4.3)
[Apologies if this shows up twice, there was a mailer error with my first attempt to post] Hi, I found the same problem reported recently on the mailing list ("compiling ACE under Fedora core 3", March 1st) but no resolution was reported there, so I thought I'd post a full description here. ACE VERSION: 5.4 HOST MACHINE and OPERATING SYSTEM: AIX 5.1 COMPILER: GNU GCC G++ 3.4.3 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_VE...

[ace-bugs] RE: test program failed on running Static library of ACE 5.4 / 5.4.1 / 5.3.1 on AMD 64 Windows platform
Hi, Thanks for using the PRF form. Do I understand correctly you are using Windows 64 bit and the 64bit Microsoft compiler? This is a platform that is not tested yet and it seems that there are still some problems. Because such a simple program doesn't work maybe compiler/linker options could be the problem. We have here AMD64 with SuSE 92 Linux without problems, AMD64 with a normal windows xp and the normale vc71 compiler also doesn't have problems. Maybe you can investigate this and supply patches, or else look at http://www.cs.wustl.edu/~schmidt/commercial-support.html for companies that deliver ACE/TAO support. We as Remedy IT can also solve this for you, see www.theaceorb.nl for our services. Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl > ACE VERSION: 5.4 / 5.4.1 / 5.3.1 > > HOST MACHINE and OPERATING SYSTEM: > Windows 2003 Server - AMD64 bit platform: > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > COMPILER NAME AND VERSION (AND PATCHLEVEL): > Compiler Version 14.00.40310.23 for AMD64 using Microsoft Platform SDK > Linker Version 8.00.40310.23 using Microsoft Platform SDK > > CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to > a platform- > specific file, simply state which one]: > config.h > > CONTENTS OF > $A...

[ace-bugs] RE: test program failed on running Static library of ACE 5.4 / 5. 4.1 / 5.3.1 on AMD 64 Windows platform
Hi Johnny, Thanks for your response. Actually Mr. Dougs response to check with ACE version 5.4.2 worked for me and I am not getting this corruption issues with this version of ACE. There were few minor compilation issues with this release of ACE but they were quite easy to resolve. Regards, Meenakshi -----Original Message----- From: Johnny Willemsen [mailto:jwillemsen@remedy.nl] Sent: Sunday, November 28, 2004 11:46 PM To: Meenakshi Vohra; ace-bugs@cs.wustl.edu Subject: RE: test program failed on running Static library of ACE 5.4 / 5.4.1 / 5.3.1 on AMD 64 Windows platform ...

[ace-users] Re: Compiling ACE 5.4 w/ GCC 3.4 problem & initial solution
Hi, The forthcoming ACE 5.4.2 beta should support GCC 3.4 "out-of-the-box." We're currently running auto-builds with what will become ACE 5.4.2 and GCC 3.4 at http://www.dre.vanderbilt.edu/scoreboard/ so please take a look and see if things are working properly there. Thanks, Doug >> Compiling ACE 5.4 w/ GCC 3.4 (Linux in my case) fails. >> The first failures are a result of the ACE_DES_FREE_TEMPLATE and >> ACE_DES_FREE_TEMPLATE2 macros in ace/Global_Macros.h. >> The syntax that is exceptionally specified for (__IBMC...

[ace-users] Re: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86
Hi Jin, >> The solaris 9/10 for sparc is not the same as solaris 9/10 for >> Intel X86,although it is almost free,and the SunStudio 9 (CC >> 5.6)for sparc is not the same as SunStudio 9(CC 5.6) for Intel X86. This is yet one more reason why you'll need to do the legwork on this. Please let us know what you find out. Thanks, Doug -- Dr. Douglas C. Schmidt, Professor TEL: (615) 343-8197 Electrical Engineering and Computer Science FAX: (615) 343-7440 Vanderbilt University WEB: www.cs.wustl.edu/~schmidt/ Nashvil...

Re: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86
Hi, >> ACE VERSION: 5.4.3 Thakns for using the PRF! >> HOST MACHINE and OPERATING SYSTEM: >> Solaris10 X86 We (i.e., the DOC groups at UCI/VU/WU) don't have Solaris running on an x86 box (yet). It would therefore be great if you could figure out what patches need to be applied so that ACE compiles properly on this platform. BTW, Kitty/Bala, weren't we planning on running Solaris on an AMD box at some point? Thanks, Doug >> TARGET MACHINE and OPERATING SYSTEM, if different from HOST: >> COMPIL...

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

[ace-users] Re: ACE 5.4 compiling problems with g++ 3.4.3
Hi Klaus, First, please use the problem-report-form when asking questions. ACE 5.4 is not supported with newer GCC versions. All these issues are resolved in the upcoming x.4.3 release. For the time being, try to add the following to your config.h # if (__GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 4)) # define ACE_EXPLICIT_TEMPLATE_DESTRUCTOR_TAKES_ARGS # endif /* __GNUC__ >= 3.4 */ You are correct, the download link doesn't work. Bala, do you have an idea what is happening with the download links. Regards, Johnny Willemsen Remedy IT ...

Re: [ace-users] Errors while compiling c++ 3.4.2
Hi Eyal, I believe we've fixed these problems in the latest version of ACE that's tucked inside our CVS repository. Can you please take a look at this version available in http://deuce.doc.wustl.edu/Download.html and see if things work better. If not, please let us know so we can fix them before we release ACE 5.4.3 in a week or so. Thanks, Doug >> I get the following while compiling: >> >> /usr/bin/c++ -D_POSIX_C_SOURCE=199506L -DNDEBUG -DUSING_GCC >> -D_POSIX_PTHREAD_SEMANTICS -DLINUX -I../inc >> -I../3rd_party...

RE: [ace-users] Re: ACE 5.4 compilation error on HP-UX 11.11/GNU g++ 3.4.3
The needed fix is, indeed, in ACE 5.5. If, for some reason, you need to stay on 5.4, the 5.4e Fix Kit from Riverace has this problem fixed as well. The fix is needed for g++ 3.4 on any platform. -Steve -- Steve Huston, Riverace Corporation Helping you succeed with ACE See http://www.riverace.com/support.htm > -----Original Message----- > From: owner-ace-users@cse.wustl.edu > [mailto:owner-ace-users@cse.wustl.edu] On Behalf Of Douglas C. Schmidt > Sent: Saturday, March 11, 2006 7:01 PM > To: ecoboja@yahoo.com; ace-users@cs.wustl.edu > Subject: [ace-users] Re: ACE 5.4 compilation error on HP-UX > 11.11/GNU g++ 3.4.3 > > > Hi, > > Thanks for using the PRF. > > >> ACE VERSION: 5.4 > > Please upgrade to ACE 5.5, which you can download from > > http://deuce.doc.wustl.edu/Download.html > > The DOC groups at Washington University, UC Irvine, and Vanderbilt > University only provide "best effort" support for non-sponsors for the > latest release, as described in > > http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/ACE-bug-pro > cess.html > > Thus, if you need more "predictable" help for ACE 5.4, I recommend > that you check out > >...

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
> > 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 This sounds good. > 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? At least for ACE 5.5, Riverace supports the Forte compiler that requires explicit. After that, we can drop it....

RE: [ace-users]: ACE 5.4.2 and ACE 5.4.3 compile failed on Solaris 9 x86 and Solaris 10 x86 #2
Hi Steve, > > 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? > > At least for ACE 5.5, Riverace supports the Forte compiler that > requires explicit. After that, we can drop it. Ok. Steve, could you maybe make clear with the build names which builds use explicit templates? Explicit templates in TAO are known to be broken at this moment. 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 ...

Web resources about - Re: [ace-bugs] Many compiler warnings when compiling 5.4.4 with gcc 3.4.1 - comp.soft-sys.ace

Resources last updated: 3/5/2016 5:52:03 PM