Re: kvm problem with FreeBSD

[stefan]

Hi,

<snip>

>> 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'm not an BSD system programmer but i'll try to figure it out. Has
anyone an idea (cbv)?

>>> 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.

There was a change on 14th of juni that said:
configure.ac: Fix kvm test. Define HAVE_KVM_ENV
so i guess kvm simply was not detected and thus not used on
FreeBSD 5.2.1 before.

greets
Stefan