#include <math.h>
#include <iostream>
int main(){
std::cout << "pi in the sky ... " << M_PI << std::endl;
return 0;
}
… with pgc++ 17.10 on Ubuntu 17.10 (which has glibc 2.26), I get:
"/usr/include/x86_64-linux-gnu/bits/floatn.h", line 62: error: invalid argument
to attribute "__mode__"
typedef _Complex float __cfloat128 __attribute__ ((__mode__ (__TC__)));
^
"/usr/include/x86_64-linux-gnu/bits/iscanonical.h", line 51: error: function
"iscanonical(long double)" has already been defined
inline int iscanonical (_Float128 __val) { return __iscanonicalf128 (__val); }
^
"/usr/include/math.h", line 505: error: function "issignaling(long double)" has
already been defined
inline int issignaling (_Float128 __val) { return __issignalingf128 (__val); }
^
On Ubuntu 16.04 (glibc 2.23) everything works well. Does that mean that pgc++ is incompatible with glibc 2.26? In particular it seems that the new quad-precision functions (_float128) make trouble. Any known workarounds?
/* Defined to 1 if the current compiler invocation provides a
floating-point type with the IEEE 754 binary128 format, and this
glibc includes corresponding *f128 interfaces for it. The required
libgcc support was added some time after the basic compiler
support, for x86_64 and x86. */
#if (defined __x86_64__ \
? __GNUC_PREREQ (4, 3) \
: (defined __GNU__ ? __GNUC_PREREQ (4, 5) : __GNUC_PREREQ (4, 4))) \
&& !defined(__CUDACC__)
# define __HAVE_FLOAT128 1
#else
# define __HAVE_FLOAT128 0
#endif
According to the PGI 17.10 release notes, under “Supported Platforms”, note that Ubuntu 16.10 is the newest Ubuntu we support, and gcc 6.3 is the newest gcc.
We will probably get 7.2 working with 18.1, and so the Community Edition will support it in 18.4.
So wait for 2 to 6 months, or install a Linux version we support.
I read that 16.10 works, but no warning that later versions do not work. It would be great if you could make this more explicit, otherwise I’m sure you will keep getting tons of error reports.
I’m using ubuntu 18.04 and PGI Community Edition 18.4, and I have the same problem described in the opening post.
I tried the suggested solution from janus (define + include), but unfortunately it is not working for me.
Also, I tried to switch to g++ versions 5, 6 and 7, but none of them compiles the source code for me (as far as I know the pgc++ uses the g++ provided by the OS, but correct me if I’m wrong).
I searched the PGI website to find something about the limitation mentioned by jtull, but I didn’t find anything about it (I mean whether it has been resolved already or not).
Do we have any information/update regarding this problem?
Unfortunately, Ubuntu 18.04 is too new for us to support it. It looks like both actually came out on the same day (April 26th, 2018) and it usually takes a us a few releases to get a new OS supported.
Though, I did just try installing 18.4 on a Ubuntu 18.04 system and it seemed to work fine. Did you install GNU 8? If so, then this would be the cause of the error.
Also, I tried to switch to g++ versions 5, 6 and 7, but none of them compiles the source code for me (as far as I know the pgc++ uses the g++ provided by the OS, but correct me if I’m wrong).
What do mean by switching version? It’s not enough to switch what version of GNU is in your PATH environment. Instead you need to generate a PGI config file (called “localrc”) to a compatible GNU version (like 7.2 or 7.3)
To create a localrc file, run the following command but change the GNU paths for your system:
This will create a “localrc” file in your local directory. Copy this file to your PGI install’s bin directory to override the current configuration. Alternately, you can copy it under a different name, such as “localrc.720”, and then set the environment variable “PGI_LOCALRC=/path/to/pgi/bin/localrc.720” so the compilers will use this configuration.
By switching to different g++ versions I mean using the “sudo update-alternatives --config g++” bash command then selecting one from the list. I guess this is an “official” way to choose a particular g++ version if you have more than one installed.
Nevertheless, I tried your “makelocalrc” suggestion. Unfortunately, it gives a permission denied error:
I tried with sudo, but since I intalled the PGI only for my account the command makelocalrc is obviously not found in the root shell.
I will try to install the PGI into my $HOME directory, maybe in that case it’ll work. If it won’t then I will install an earlier version of ubuntu which has already been tested with PGI 18.4.
sorry for the late reply.
I made the PGI dir writable, but I still got the same error.
So, I decided to install the 16.04 ubuntu, then the CUDA toolkit and
driver from the nvidia website.
It didn’t work either, so I tried the toolkit and driver from the
official ubuntu reporsitories and it works fine now.
Anyway, thank you for the help!
[…]/boost/type_t
raits/is_floating_point.hpp", line 25: error: class
“boost::is_floating_point” has already been defined
template<> struct is_floating_point<__float128> : public true_type{};
“/usr/lib/gcc/x86_64-linux-gnu/6/include/quadmath.h”, line 32: error: 128-bit
floating-point types are not supported in this configuration
typedef _Complex float attribute((mode(TC))) __complex128;
This error appears on a Debian-9 system with gcc 6.3.0, pgi 18.4 and glibc 2.24 and boost 1.63.0.
Do you have any idea which might be the critical tool that causes the incompatibility?
We don’t support quad precision. I’m not sure how you have Boost configured but don’t define “BOOST_HAS_FLOAT128” and then you should be able to work around this issue.
I came across this same problem with my Linux Mint 19 install (which uses Ubuntu 18.04 underneath).
The compiler (18.7) was working but when I tried to compile HDF5 it crashed with the redundant math.h errors.
After reading this thread, I simply edited the rclocal file and replaced all the “5s” with “7s” (my machine uses GNU 7 by default). I also updated the GNU version number in that file.
After that, HDF5 compiled! (I did have to use the “export CPP=cpp” trick as mentioned in another thread).
I tested it on our code that links to HDF5 and it works!