[bug #23876] gnustep-base does not build in a chrooted environment
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: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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. ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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; from a Debian buildd log for 1.16.3: checking procfs.h usability... no checking procfs.h presence... no checking for procfs.h... no checking kernel support for /proc filesystem... yes checking support for /proc psinfo struct... no checking link to exe of process in /proc... /proc/self/exe checking /proc/10669/cmdline terminated by nul... yes ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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 run `autoreconf -vi'? (file #16321) ___ Additional Item Attachment: File name: procfs.diffSize:0 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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 sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
Update of bug #23876 (project gnustep): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #13: Thanks ... patch applied ... fixed in subversion now. ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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. Hope that helps in figuring out a solution Thanks ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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 /proc filesystem -configure:15770: result: no +configure:15770: result: yes configure:15794: checking support for /proc psinfo struct So, what should we do? ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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 Severity: 3 - Normal Item Group: Bug Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any ___ Details: I'm currently building gnustep-base 0.16.2 in a chrooted environment (Mandirva iurt). But it fails at: GSFFCallInvocation.m:1080: warning: value computed is not used GSFFCallInvocation.m:1080: warning: value computed is not used GSFFCallInvocation.m:1081: warning: value computed is not used GSFFCallInvocation.m:1081: warning: value computed is not used GSFFCallInvocation.m:1081: warning: value computed is not used GSFFCallInvocation.m:1081: warning: value computed is not used GSFFCallInvocation.m:1082: warning: value computed is not used GSFFCallInvocation.m:1082: warning: value computed is not used GSFFCallInvocation.m:1082: warning: value computed is not used GSFFCallInvocation.m:1082: warning: value computed is not used GSFFCallInvocation.m:1085: warning: value computed is not used GSFFCallInvocation.m:1097: warning: value computed is not used GSFFCallInvocation.m:1097: warning: value computed is not used GSFFCallInvocation.m:1101: warning: value computed is not used GSFFCallInvocation.m: At top level: GSFFCallInvocation.m:186: warning: 'gs_subtype' defined but not used Linking library libgnustep-base ... obj/NSProcessInfo.o: In function `main': /home/fwang/rpm/BUILD/gnustep-base-1.16.3/Source/NSProcessInfo.m:913: undefined reference to `gnustep_base_user_main' collect2: ld returned 1 exit status ___ File Attachments: --- Date: Friday 07/18/2008 at 02:23 Name: build.0.20080718021337.log Size: 46kB By: fundawang The buildlog and the build dependencies http://savannah.gnu.org/bugs/download.php?file_id=16133 --- Date: Friday 07/18/2008 at 02:23 Name: rpm_qa.0.20080718021337.log Size: 7kB By: fundawang The buildlog and the build dependencies http://savannah.gnu.org/bugs/download.php?file_id=16134 ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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). However, the error message does give some clue: Linking library libgnustep-base ... obj/NSProcessInfo.o: In function `main': /home/fwang/rpm/BUILD/gnustep-base-1.16.3/Source/NSProcessInfo.m:913: undefined reference to `gnustep_base_user_main' Now, this is linking the library itsself, and the gnustep_base_user_main function is *supposed* to be undefined at this point (since that function should be provided in programs using the library. This suggests that there is a problem with the linker (or the arguments supplied to it). However, on most systems I would not expect gnustep_base_user_main to be used at all, so something may be broken at the configuration stage. ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
[bug #23876] gnustep-base does not build in a chrooted environment
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 to do that is to look at the configure and build logs. You can compare logs of the build inside and outside the chrooted environment to see what the difference is. Then you can decide whether the issue is something that can be dealt with in the gnustep configure scripts or is something that has to be corrected in the environment. ___ Reply to this item at: http://savannah.gnu.org/bugs/?23876 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
