Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments

2014-05-27 Thread Aurelien Jarno
reopen 746994 found 746994 3.9.4 thanks On Tue, May 27, 2014 at 01:09:50AM -0400, Nathan Scott wrote: Closing this bug, as it appears to be a problem specific to the bug reporters machine, and no further information has been forthcoming. Since /bin/systemd is the location of systemd from the

Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments

2014-05-27 Thread Nathan Scott
Hi Aurelien, - Original Message - The configure script tries to find systemd in /bin/systemd, while ps -ef show a different path: $ ps -ef | grep systemd root 1 0 0 avril30 ? 00:00:01 /lib/systemd/systemd --system --deserialize 22 Ah, there's that information I

Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments

2014-05-27 Thread Aurelien Jarno
On Tue, May 27, 2014 at 03:46:37AM -0400, Nathan Scott wrote: Hi Aurelien, - Original Message - The configure script tries to find systemd in /bin/systemd, while ps -ef show a different path: $ ps -ef | grep systemd root 1 0 0 avril30 ? 00:00:01

Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments

2014-05-04 Thread Aurelien Jarno
Source: pcp Version: 3.9.2 Severity: serious Justification: fails to build from source (but built successfully in the past) On a system using systemd as the init system, pcp fails to build with the following error: | ... | checking if echo uses -n or backslash-c to suppress newlines... -n |