Summary: build: Use the C11 standard for C and the C++11 standard for C++
[#1374]
Review request for Trac Ticket(s): 1374
Peer Reviewer(s): Mathi
Pull request to:
Affected branch(es): default(4.7)
Development branch: default
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system y
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services n
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
changeset 628e30d32d1f9fa5c48021f62b6fa0d5ebd8f157
Author: Anders Widell <anders.wid...@ericsson.com>
Date: Thu, 21 May 2015 13:28:44 +0200
build: Use the C11 standard for C and the C++11 standard for C++ [#1374]
Use the C11 standard when compiling C code, and the C++11 standard when
compiling C++ code. For GCC, this means that we also bump the
recommended
minimum version to 4.8.1, which is the first version where all major
features of C++11 were fully implemented (though most C++11 features
were
implemented already in earlier versions).
Complete diffstat:
------------------
Makefile.common | 4 ++--
README | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
Testing Commands:
-----------------
Build and start OpenSAF.
Testing, Expected Results:
--------------------------
OpenSAF should successfully build and start.
Conditions of Submission:
-------------------------
Ack from Mathi
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 y y
powerpc n n
powerpc64 n n
Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]
Your checkin has not passed review because (see checked entries):
___ Your RR template is generally incomplete; it has too many blank entries
that need proper data filled in.
___ You have failed to nominate the proper persons for review and push.
___ Your patches do not have proper short+long header
___ You have grammar/spelling in your header that is unacceptable.
___ You have exceeded a sensible line length in your headers/comments/text.
___ You have failed to put in a proper Trac Ticket # into your commits.
___ You have incorrectly put/left internal data in your comments/files
(i.e. internal bug tracking tool IDs, product names etc)
___ You have not given any evidence of testing beyond basic build tests.
Demonstrate some level of runtime or other sanity testing.
___ You have ^M present in some of your files. These have to be removed.
___ You have needlessly changed whitespace or added whitespace crimes
like trailing spaces, or spaces before tabs.
___ You have mixed real technical changes with whitespace and other
cosmetic code cleanup changes. These have to be separate commits.
___ You need to refactor your submission into logical chunks; there is
too much content into a single commit.
___ You have extraneous garbage in your review (merge commits etc)
___ You have giant attachments which should never have been sent;
Instead you should place your content in a public tree to be pulled.
___ You have too many commits attached to an e-mail; resend as threaded
commits, or place in a public tree for a pull.
___ You have resent this content multiple times without a clear indication
of what has changed between each re-send.
___ You have failed to adequately and individually address all of the
comments and change requests that were proposed in the initial review.
___ You have a misconfigured ~/.hgrc file (i.e. username, email etc)
___ Your computer have a badly configured date and time; confusing the
the threaded patch review.
___ Your changes affect IPC mechanism, and you don't present any results
for in-service upgradability test.
___ Your changes affect user manual and documentation, your patch series
do not contain the patch that updates the Doxygen manual.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
