Follow-up Comment #8, bug #23876 (project gnustep):
AC_SYS_PROCFS is not a standard autoconf macro, just a macro polluting
autoconf's namespace (a common practice, unfortunately).
___
Reply to this item at:
Follow-up Comment #9, bug #23876 (project gnustep):
AC_SYS_PROCFS is not a standard autoconf macro
Thanks ... I guess it must be defined somewhere in GNUstep then ... so if the
macro is generating a poor test, we need to change it once we know of a better
test.
Follow-up Comment #10, bug #23876 (project gnustep):
The macro definition is in config/procfs.m4. I don't know where it came
from, but definitely not Autoconf.
The test being performed there is going to fail in chroots that do not mount
/proc.
FWIW, it doesn't fail on Debian autobuilders;
Follow-up Comment #11, bug #23876 (project gnustep):
I just tried in a pbuilder chroot (which mounts /proc) -- the `mount' command
outputs nothing.
The attached trivial patch should be equally reliable and should DTRT in such
chroots. Funda Wang, does it work for you if you apply it and then
Follow-up Comment #12, bug #23876 (project gnustep):
yes it builds correctly in a chrooted environment. Thanks.
___
Reply to this item at:
http://savannah.gnu.org/bugs/?23876
___
Message
Update of bug #23876 (project gnustep):
Status:None = Fixed
Open/Closed:Open = Closed
___
Follow-up Comment #13:
Thanks ... patch
Follow-up Comment #4, bug #23876 (project gnustep):
IIRC normally on Linux NSProcessInfo is using /proc
to get information on the process.
If you're running on a chroot environment, you probably
don't have /proc, which explains why it would then fall back
to the `gnustep_base_user_main' hack.
Follow-up Comment #6, bug #23876 (project gnustep):
OK, there must be something regarding /proc filesystem:
diff -u chrooted.config.log normal.config.log
@@ -5763,12 +5766,12 @@
configure:15714: checking for procfs.h
configure:15721: result: no
configure:15742: checking kernel support for
URL:
http://savannah.gnu.org/bugs/?23876
Summary: gnustep-base does not build in a chrooted
environment
Project: GNUstep
Submitted by: fundawang
Submitted on: Friday 07/18/2008 at 02:23
Category: Base/Foundation
Follow-up Comment #1, bug #23876 (project gnustep):
There's not much to do on here ... you would need to at least look at the
configuration log and full build output to see what's going on (building the
'startup' package might help here as that automatically collects the relevant
logs).
Follow-up Comment #3, bug #23876 (project gnustep):
If it builds correctly normally, but does not build in the chrooted
environment, then obviously the chrooted environment differs from the normal
environment ... so you need to find out what is wrong with the chrooted
environment. The best way
11 matches
Mail list logo
