Follow-up Comment #3, bug #26437 (project gnustep): > 2. Removing the ability to use the GNUSTEP_MAKEFILES > environment variable by hard-coding its value into a > makefile would not be acceptable to most people.
So can I assume something like ifeq ($(GNUSTEP_MAKEFILES),) GNUSTEP_MAKEFILES=/hardcoded/path/to/Makefiles endif would be better? Currently, if GNUSTEP_MAKEFILES isn't set it's as well unlikely gnustep-config is found. > it's not completely clear that this really is a gnustep > issue at all. Perhaps it's an Ubuntu package issue? Did > gnustep-make come with Ubuntu? Ubuntu comes with a gnustep-make package, but here both, gnustep-make and gnustep-base, were installed from svn. The standard procedure for installations from source is still to use sudo without -E. See http://ubuntuguide.org/wiki/Ubuntu:Jaunty#Installing_a_package_from_source _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?26437> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnustep
