discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems building - faiiling due to autogsdoc


From: Adam Fedor
Subject: Re: problems building - faiiling due to autogsdoc
Date: Thu, 19 Jun 2003 20:35:12 -0600


On Thursday, June 19, 2003, at 05:31 PM, Alex Perez wrote:

On Thu, 19 Jun 2003 22:55:12 +0100
Richard Frith-Macdonald <richard@brainstorm.co.uk> wrote:
Please don't do that ... instead, track down the cause of the problem
and supply a fix, so other people don't have the problem in future.
However, if --disable-procfs gets rid of the symptom. it's probably a
good idea to look at what information the operating system is
providing to the procfs code in NSProcessInfo.
1. there could be a bug in GNUsteps handling of procfs, which could be
fixed.
2. there could be a bug in BSDs procfs, for which we could get
autoconf to enable a workaround (or disable procfs support if it is
horribly broken).

IIRC, I reported that /procfs problem a good 1 year a go (could be even
more). GNUstep tries to access a couple of entries which simply do not
exist, like /procfs/self/exe (or sth like that) on BSD.
*cough* This kind of crap is why GNUstep doesn't get the attention it
deserves. *puts on fireproof suit*


Well, you, of course, asked for it. So I went back and searched all the gnustep mailing list archives and I didn't find a mention of a bug report like this or anyone suggesting that this was the solution. I also searched the entire web and didn't find anything like this. Perhaps it was done privately - I don't know about that.

FYI, a good method of getting bugs fixed is to use the bug tracking database:

http://savannah.gnu.org/bugs/?group=gnustep

Then you can track the status of your bug.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]