On 21 Mar 2018, at 19:33, Josh Freeman <[email protected]> wrote: > > The reason for installing gnustep-make twice is that libobjc2's install > path depends on whether gnustep-config is present (at least on > Debian/Ubuntu): If gnustep-config is present, libobjc2 installs to > /usr/GNUstep/Local/Library/ - if not, it installs to /usr/local/lib/. > > GNUstep-make's configure won't find libobjc2 in /usr/local/lib/; It'll still > successfully configure ("checking for custom shared objc library... NONE"), > build, & install, but then GNUstep-base will fail to build - its configure > will fail the "checking whether objc really works..." test because no runtime > was found. > > So, GNUstep make's first (pre-libobjc2) install puts gnustep-config in place > so that libobjc2 will install in a location where GNUstep make's second, > post-libobjc2 install can find & use it as the runtime.
If you are installing on a platform that prefers /usr/lib, then the correct fix for this is to just set the prefix to /usr/ instead of /usr/local. You don’t need to install GNUstep Make to do that. David _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
