This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.5.17: chroot-ed make adds // to ${MAKE}
- From: Rolf Campbell <thats dot unpossible at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 14 Jun 2005 16:32:36 -0400
- Subject: Re: 1.5.17: chroot-ed make adds // to ${MAKE}
- References: <d8n8uu$1kt$1@sea.gmane.org>
Rolf Campbell wrote:
> I'm trying to do a chroot-ed make which uses the content of the ${MAKE}
> variable. What I'm finding is the value of ${MAKE} has two slashes '//'
> at the beginning, so any attempt to use it failes (looks like a network
> share).
>
> I've created a directory, expanded cygwin-1.5.17-1.tar.bz2 into it, then
> copied make.exe (from the cygwin package). And a few other dlls that
> were needed by cygwin1.dll (intl/conv). When I run:
>
> $ chroot . usr/bin/make.exe all
> echo //usr/bin/make
> make: echo: Command not found
> make: *** [all] Error 127
>
> I know that that error code has to do with echo.exe not existing, but
> I'm only concerned with the extra '/' added to ${MAKE}. My makefiles
> that run sub-makes use it and fail.
>
> --makefile--
>
> all:
> echo ${MAKE}
I tried to over-ride the MAKE (and MAKE_COMMAND) variable from the
command line, which fixed this specific problem, but I'm left with
another problem. Even if you override MAKE and MAKE_COMMAND, you still
get an error:
$ chroot . usr/bin/make.exe -Rr all MAKE=/usr/bin/make.exe
MAKE_COMMAND=/usr/bin/make.exe
makefile:4: m.mk: No such file or directory
echo t > m.mk
make: //usr/bin/make: Command not found
You can specify "chroot . /usr/bin/make.exe ..." and it will work, but
it should also work without that leading slash.
--makefile--
all:
echo ${MAKE}
include m.mk
m.mk:
echo t > m.mk
--
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/