acc 6.29 is missing a header file that is required for c++ <atomic> support

[JEsker]

I am attempting to build icu (icu.unicode.org)  which requires C++ 11 support.  You can see that the options +std=c++11 and +stl=gnu are specified.

There are a fair number of warnings, but more importantly the reason for this post -- the header file <atomic> leads to an attempt to include a header file which is missing from the compiler installation altogether.

======== Rebuilding "brkeng.o" ========
aCC -DU_ATTRIBUTE_DEPRECATED= -DU_COMMON_IMPLEMENTATION -D_REENTRANT -D_THREAD_SAFE -DU_HAVE_ELF_H=1 -DU_HAVE_STRTOD_L=0 -DU_HAVE_LIB_SUFFIX=1 -DU_LIB_SU
FFIX_C_NAME=_ratl -I. "-DDEFAULT_ICU_PLUGINS=\"/opt/rational/common/shlib/icu\" " -O +DD64 +std=c++11 +stl=gnu -ext +W612 -DATRIA_CXX_11 -mt -Wc,-ansi_for_scope,on +W740 +W749 +W823 +W4232 -c +Z -o brkeng.o brkeng.cpp

"/opt/aCC6.29/opt/gnustl/include/bits/atomic_base.h", line 38: error #3696-D: cannot open source file "bits/atomic_lockfree_defines.h"

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

<atomic>  includes <bits/atomic_base.h>

in atomic_base.h we see that it unconditionally includes <bits/atomic_lockfree_defines.h>, which does not exist

#ifndef _GLIBCXX_ATOMIC_BASE_H
#define _GLIBCXX_ATOMIC_BASE_H 1

#pragma GCC system_header

#include <bits/c++config.h>
#include <stdbool.h>
#include <stdint.h>
#include <bits/atomic_lockfree_defines.h>

..... 

[jesker(hp11_ia64_64)@deimos 51] pwd
/opt/aCC-6.29
[jesker(hp11_ia64_64)@deimos 52] find . | grep atomic
find: cannot open ./var/adm/sw/products
./opt/aCC/share/man/man3.Z/std::__atomic_base.3g
./opt/aCC/share/man/man3.Z/std::__atomic_flag_base.3g
./opt/aCC/share/man/man3.Z/std::atomic.3g
./opt/aCC/share/man/man3.Z/std::atomic_bool.3g
./opt/aCC/share/man/man3.Z/std::atomic_flag.3g
./opt/gnustl/include/atomic
./opt/gnustl/include/bits/atomic_base.h
./opt/gnustl/include/bits/atomic_word.h
./opt/gnustl/include/ext/atomicity.h

[laurentmenase]

Only some of C++11 std had been implemented:

see https://support.hpe.com/hpesc/public/docDisplay?docId=c05054285&docLocale=en_US

"+std=c++11: This option turns on support for several core language features introduced
by the ISO C++11 language standard. It is available only in C++ compilation mode
and is binary compatible with the '+std=c++98' ('–AA') compilation mode."

"The -Ax option turns on support for several core language features introduced by the
recently published C++11 standard. The -Ax option is available only in C++ compilation
mode and is binary compatible with the -AA compilation mode. See the HP aC++/HP
ANSI C Release Notes for a description of extensions supported."

And
https://support.hpe.com/hpesc/public/docDisplay?docId=a00028054en_us&docLocale=en_US
Atomic support is not one of the C++11 standard added options unfortunately

For a full list synthetic list of supported C++11 features see:

https://en.cppreference.com/w/cpp/compiler_support/11

[JEsker]

Wow, that's not a great situation. The other Unix variants I need to build on do support atomic with their proprietary compilers. 

Is there a gcc any newer than 4.7.1 available?  Really do not want to be in the business of having to build and support gcc for this platform ourselves.

[laurentmenase]

You may look at  Merijn's HP-UX software Download Section for ITRC members  looks like to be a community released one - not HPE product

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

[JEsker]

I cannot honestly state that my issue is resolved.  We are left without a working compiler, and I would need to get approval to download from a third party.  The newest version there appears to be 4.7.2 which may or may not provide sufficient c++11 support for the project at hand.  

[laurentmenase]

You may contact your sales representative on this subject