Hi! You can generate the config file easily with ag++ --gen_config. Sorry for the inconvenience. The background is that when I wrote the first ac++ tests, I did not want the makefile to depend on ag++.
We should change that sooner or later, because it is obviously confusing. Cheers, Olaf On 08/23/2017 17:57, Reinhard Tartler wrote: > > > On 08/23/2017 04:29 AM, Olaf Spinczyk wrote: >> Hi Reinhard, >> >> when trying to compile the tests, ac++ seems to have no (or an invalid) >> puma.config file. It doesn't find the system header files, e.g. stdio.h >> and iostream. For 'make test' to succeed PUMA_CONFIG must point to a >> valid config file. Are you sure that there is one? Where do you set the >> environment variable? I haven't seen it in the log. > > > I think what confused me is that the build did succeed for release 2.2. > Here is the old buildlog: > https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2B&arch=amd64&ver=1%3A2.2-1&stamp=1490665251&raw=0 > > The difference is that in release 2.2, failures in the test suite were > ignored. Now they are causing the build to fail. > > I'm a bit surprised that invoking the testsuite doesn't handle > puma.config generation by itself and requires the caller to take care of > that. But I can certainly look into that. > > I'll try that out and report back. > > Thanks guys! > -rt >
