[perfmon2] PAPI build fails with gcc/8

2018-10-18 Thread Frank Winkler
Hi all, As I did not get a reply from Stephane I would like to turn this to the perfmon2-devel mailing list. Please see the text below: Hi Stephane, I would like to ask for your help. There is a build problem of PAPI when using gcc/8. See open issue here: https://bitbucket.org/icl/papi/issues/

Re: [perfmon2] PAPI build fails with gcc/8

2018-10-18 Thread William Cohen
On 10/18/18 10:43 AM, Frank Winkler wrote: > Hi all, > > As I did not get a reply from Stephane I would like to turn this to the > perfmon2-devel mailing list. > Please see the text below: > > Hi Stephane, > > I would like to ask for your help. > There is a build problem of PAPI when using gcc/

Re: [perfmon2] PAPI build fails with gcc/8

2018-10-18 Thread Frank Winkler
Thanks Will, I have just seen that it has also been fixed in our master branch. :-) Frank > On 18. Oct 2018, at 17:40, William Cohen wrote: > > On 10/18/18 10:43 AM, Frank Winkler wrote: >> Hi all, >> >> As I did not get a reply from Stephane I would like to turn this to the >> perfmon2-deve

[perfmon2] PAPI pfmlib.h:29 compile Error 1540-0081, #pragma GCC visibility push(default)

2018-10-18 Thread Anthony Castaldo
This problem comes from our PAPI list, but is a pfmlib problem when compiling with IBM XL C/C++. I investigated it. First, this is a real problem that prevents creating libpfm.so. Second, I found no clean workaround (other than using gcc instead of xlC), but there is a way to create a functional l

Re: [perfmon2] PAPI pfmlib.h:29 compile Error 1540-0081, #pragma GCC visibility push(default)

2018-10-18 Thread William Cohen
On 10/18/18 3:10 PM, Anthony Castaldo wrote: > This problem comes from our PAPI list, but is a pfmlib problem when compiling > with > IBM XL C/C++. I investigated it. > > First, this is a real problem that prevents creating libpfm.so. > Second, I found no clean workaround (other than using gcc in

Re: [perfmon2] PAPI pfmlib.h:29 compile Error 1540-0081, #pragma GCC visibility push(default)

2018-10-18 Thread Anthony Castaldo
Hi Will. I saw that page. I was using xlC 6.1.1-beta6, the most recent version I could find, and it still exhibited the error. It seems to recognize and process the #pragma, but claims *default* is not a valid attribute. It absolutely is, and the line and syntax are taken from IBM's example code.