Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
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 systemd deb, the bug report appears self-contradictory... not alot to work with here I'm afraid. Please reopen if additional information comes to hand - thanks! This is not a problem with my machine, this is something fully reproducible, even with version 3.9.4. 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 root 155 1 0 avril30 ? 00:00:02 /lib/systemd/systemd-journald root 167 1 0 avril30 ? 00:00:00 /lib/systemd/systemd-udevd root 634 1 0 avril30 ? 00:00:00 /lib/systemd/systemd-logind I am therefore reopening the bug. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
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 was looking for - thanks! I don't run systemd on my primary machine yet, so had been looking here as a poor source of second-hand information: https://packages.debian.org/sid/amd64/systemd/filelist ... which fooled me into thinking we're doing the same thing as Fedora with the /bin/systemd listed there. I am therefore reopening the bug. Thanks! Will address this in pcp-3.9.5 shortly - sorry about closing prematurely, I thought you'd lost interest / found the source of that incorrectly-suspected-misconfiguration when I didn't hear back before. cheers. -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
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 /lib/systemd/systemd --system --deserialize 22 Ah, there's that information I was looking for - thanks! I don't run systemd on my primary machine yet, so had been looking here as a poor source of second-hand information: https://packages.debian.org/sid/amd64/systemd/filelist ... which fooled me into thinking we're doing the same thing as Fedora with the /bin/systemd listed there. I am therefore reopening the bug. Thanks! Will address this in pcp-3.9.5 shortly - sorry about closing prematurely, I thought you'd lost interest / found the source of that incorrectly-suspected-misconfiguration when I didn't hear back before. The problem is that you answered the bug only to the BTS, without putting me in Cc:. Thus I never received your email. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746994: pcp: FTBFS with systemd: FATAL ERROR: could not determine how to get the all processes with arguments
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 | checking for ps style... unknown | FATAL ERROR: could not determine how to get the all processes with arguments | format output from your ps(1). | debian/rules:123: recipe for target '.census' failed | make: *** [.census] Error 1 | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 | debuild: fatal error at line 1364: | dpkg-buildpackage -rfakeroot -D -us -uc -B failed | ... A quick look at the configure script shows that it expect systemd to be installed at another location than the one in Debian. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
