Martin Brecher <[EMAIL PROTECTED]> writes:
> After doing make install in gnustep-make, I end up with
>
> /C/GNUstep/System/Libraries
> /C/GNUstep/System/Libraries/Resources
> /C/GNUstep/System/Libraries/Java
>
> no other folders in Libraries/
The same goes for me
> Doing make install in ffcall:
>
> $ make install
> cd avcall; make install
> make[1]: Entering directory `/D/home/Administrator/cvs/ffcall-1.8d/avcall'
> if [ ! -d /C/GNUstep/System ] ; then mkdir /C/GNUstep/System ; fi
> if [ ! -d /C/GNUstep/System ] ; then mkdir /C/GNUstep/System ; fi
> if [ ! -d /C/GNUstep/System/Libraries/ix86/mingw32 ] ; then mkdir
> /C/GNUstep/System/Libraries/ix86/mingw32 ; fi
> mkdir: cannot create directory
> `/C/GNUstep/System/Libraries/ix86/mingw32': No such file or directory
> make[1]: *** [install] Error 1
> make[1]: Leaving directory `/D/home/Administrator/cvs/ffcall-1.8d/avcall'
> make: *** [install] Error 2
This, I can't reproduce. Also, I am not sure what you did. The README
says you have to do
-----
./configure --prefix=$GNUSTEP_SYSTEM_ROOT \
--libdir=$GNUSTEP_SYSTEM_ROOT/Libraries/ix86/mingw32 \
--includedir=$GNUSTEP_SYSTEM_ROOT/Headers
make
make install
-----
and if I do that, I don't get your error. Just doing "make install",
without configure and make first, doesn work at all ("No rule to make
target `install'.") and ./configure followed by "make install" leaves
me with a different error than yours. Which scenario did you follow?
> It should be sufficient to replace the mkdir calls in the Makefiles with
> mkdir -p (or use mkinstalldirs?). Or to force the creation of the
> os/arch folders by gnustep-make.
This is probably a good idea anyway.
Tom Koelman
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep
