|
From: | Richard Frith-Macdonald |
Subject: | Re: kvm problem with FreeBSD |
Date: | Fri, 6 Aug 2004 10:39:54 +0100 |
On 6 Aug 2004, at 10:27, Chris B. Vetter wrote:
stefan@wms-network.de wrote: [...]That's the real problem. I've no proc support on my system.Granted, using /proc is a convenient way of accessing system information, without bothering to learn how to use the proper interfaces provided by your system.I've the /proc directory and it's empty. I think i can remember that i disabled proc support when installing my system because has been said that it's deprected or something like this.That's one of the changes to the 5.x tree of FreeBSD, yes. You do not really *need* /proc to access the information, as there are more than enough ways to retrieve those using standard library calls.
IIRC the only thing /proc is used for is to obtain the list of arguments to the current process, thus avoiding the kludge of having to redefine the function main() in a macro so that GNUstep can get them from argv before the real main() is called. What is the appropriate standard library call to obtain the process arguments under BSD? If we know that, and can get the configure script to recognize when this call is available, we can alter NSProcessInfo.m to use this call instead of /proc
I wonder why it worked with previous versions of GNUstep.I haven't used GNUstep since end of March (because I'm currently stuck on bloody XP) so I do not know what may have changed. You might want to take a look at the source to NSProcessInfo.
I don't know, but my guess would be the configure script is as likely a culprit as NSProcessInfo.m itsself.
[Prev in Thread] | Current Thread | [Next in Thread] |