Gadi Oron wrote on 20 May 2008 15:54:
> Whenever I am compiling something with "make" and there is somekind of
> nested make, it fails with the following error:
>
> cd fdlibm; make -f Makefile.ref all
> /bin/sh: line 0: cd: fdlibm: No such file or directory
> make[2]: *** [all] Error 1
>
> This error is not restricted to a single soft, but I've encountered it
> in many place.
>
> The workaround I have is to go into the corresponding makefile and add
>
> SHELL = bash
>
> This would resolve the issue, but needless to say, the change is
> annoying especially when the Makefile is created by a "configure"...
>
> Can someone help me with that?
Let's get some diagnostic info. Replace the command-line with
pwd ; ls -la ; cd fdlibm; make -f Makefile.ref all
and let's try and find out whether make (or to be precise, the shell
launched by make) is actually in the directory that it's supposed to be in
or not.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
