php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #4633 Compile fails with RUSAGE errors
Submitted: 2000-05-27 03:12 UTC Modified: 2000-07-31 18:35 UTC
From: jim dot dabell at graffiti dot net Assigned:
Status: Closed Package: Compile Failure
PHP Version: 4.0 Latest CVS (27/05/2000) OS: Slackware Linux 7.0; Kernel 2.4.
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jim dot dabell at graffiti dot net
New email:
PHP Version: OS:

 

 [2000-05-27 03:12 UTC] jim dot dabell at graffiti dot net
I've seen two bugs in the database regarding this issue, but couldn't find any obvious way of appending to them, so I'm submitting this as a new bug report.

On later 2.3.x and 2.4.x Linux kernels, the build fails, complaining about GETRUSAGE.  The problem appears to lie inbetween autoconf and the kernel headers.  From /usr/src/linux/include/linux/resource.h:

/*
 * Definition of struct rusage taken from BSD 4.3 Reno
 *
 * We don't support all of these yet, but we might as well have them....
 * Otherwise, each time we add new items, programs which depend on this
 * structure will lose.  This reduces the chances of that happening.
 */                                                        
What seems to be happening is that autoconf checks the kernel headers, finds the rusage defines, and reports that the OS supports rusage, when in actual fact it doesn't.  I worked around this by configuring php, editing config.cache to indicate rusage wasn't supported, reconfiguring, and carrying on from there.  There's probably an easier way of doing it, but that worked for me.

Hope this helps,

Jim

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-06-12 18:26 UTC] rasmus at cvs dot php dot net
Do your header files match the kernel you are running?
 [2000-06-14 01:00 UTC] jim dot dabell at graffiti dot net
Yes, headers match ( /usr/include/linux is a symlink to /usr/src/linux/include/linux ).  glibc is 2.1.2.

Jim
 [2000-07-31 15:10 UTC] sas@php.net
This is not a PHP issue. Please refer to the last entry on the following page for possible reasons:

http://bugs.php.net/bugs-php3.php?id=4949
 [2000-07-31 18:20 UTC] jim dot dabell at graffiti dot net
Hate to keep pestering you, especially as I've got a workaround, but "This is not a PHP issue" is a bit vague.  None of the documentation for the kernel, compiler, PHP, or related tools state that glibc 2.1.3 is required as far as I can see.  Are you saying that there is an error in the documentation for the kernel or supporting tools, or are you saying that there is an omission in the PHP documentation?  If the former, which one, exactly?  If the latter, then I would consider this to be a PHP issue.
 [2000-07-31 18:35 UTC] stas@php.net
PHP documentation should not care about relations between glibc and Linux kernel. I'm sure when 2.4.0 is out, the relase note would state which libc you need with it. But since you are using development kernel, you are
mostly on your own with that.

Also, I've just checked and PHP builds successfully on 2.4-test with glibc 2.1.3. 
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved.
Last updated: Sat Oct 10 10:00:02 2026 UTC