[bug #23876] gnustep-base does not build in a chrooted environment

[Richard Frith-Macdonald]

Follow-up Comment #7, bug #23876 (project gnustep):

Now you know which test in configure/configure.ac failed ... so you can look
at the actual test in configure.ac and figure out why it gave a different
result in your chrooted environment to your live environment.

Obviously something in the chrooted environment is different ... looking at
configure and configure.ac I see that, 'checking kernel support for /proc
filesystem' clearly comes from AC_SYS_PROCFS, a standard autoconf macro.
Looking at the expansion of the macro in configure, it seems it is using the
'mount' command, so presumably there is a problem with the mount command in
your chrooted environment and you need to get that fixed.

Actually, there are four possibilities for where this should be fixed:

1. you consider the problem to be an error in the chrooted environment
1a. due to some error in your system setup if you changed things in your
distrib ... this seems unlikely, but if it's the case then it's your own
responsibility to fix it.
1b. due to an error in your distrib ... you should get the maintainers of the
distrib to fix it.

2. a fault in the test (AC_SYS_PROCFS macro)
2a. should be reported to the maintainers of the autoconf package so that
they can fix it
2b. you could contribute an additional test to GNUstep, so that we could use
it after the AC_SYS_PROCFS macro, rather than waiting for a fix to be applied
to autoconf

NB. If 2a has already been done, it might be that GNUstep could move to using
a more recent version of autoconf, but having 2b woiuld still be worthwhile.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?23876>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/