Hi zoran,

The default is not compiling.

The following changes are missed in ImmModel.cc for protocol47 to protoco46 for the following functions:

ImmModel.cc: In member function ‘SaAisErrorT ImmModel::ccbObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T*, unsigned int*, SaUint32T*, SaUint32T*, unsigned int*, std::string&, bool*)’: ImmModel.cc:6736:31: error: ‘protocol47Allowed’ was not declared in this scope
         if(!protocol47Allowed()) {
                               ^
ImmModel.cc: In member function ‘SaAisErrorT ImmModel::rtObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T, unsigned int, SaUint32T*, SaUint32T*, unsigned int*, SaUint32T*, SaUint32T*)’: ImmModel.cc:13996:31: error: ‘protocol47Allowed’ was not declared in this scope
         if(!protocol47Allowed()) {

/Neel.

On Friday 27 February 2015 07:03 PM, Zoran Milinkovic wrote:

  * *status*: assigned --> fixed
  * *Comment*:

default(4.6):

changeset: 6289:cf6044a98dfb
tag: tip
user: Zoran Milinkovic zoran.milinko...@ericsson.com <mailto:zoran.milinko...@ericsson.com>
date: Wed Feb 25 13:41:32 2015 +0100
summary: imm: change protocol 47 to protocol 46 [#969] <http://sourceforge.net/p/opensaf/tickets/969>

------------------------------------------------------------------------

*[tickets:#969] <http://sourceforge.net/p/opensaf/tickets/969> IMM: remove all use of SaNameT from IMM server side and messages*

*Status:* fixed
*Milestone:* 4.6.FC
*Created:* Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
*Last Updated:* Tue Feb 24, 2015 09:59 AM UTC
*Owner:* Zoran Milinkovic

All usage of SaNameT should be purged from the IMM server side code.

For message types we need backwards compatibility.
But new versions should be defined for all messages that currently use
SaNameT and the new message version should be used in the release where this
ticket is fixed, subject to the protocolXXAllowed bit in noStdFlags.
The message packing unpacking code should on the server side transform
to the new message type as part of unpacking.

On the IMMA client side, usage of SaNameT should be confined to only the
very top layer of the old API, when enhancement #643 is fixed.

http://sourceforge.net/p/opensaf/tickets/643/ <http://sourceforge.net/p/opensaf/tickets/643>

------------------------------------------------------------------------

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ <https://sourceforge.net/p/opensaf/tickets>

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to