[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Is -C @ magical?
From: |
Doug Konrad |
Subject: |
RE: Is -C @ magical? |
Date: |
Tue, 21 Jan 2014 21:12:58 +0000 |
Paul,
I changed the path to ``/.../some/other/path`` to obscure details I shouldn't
publicize.
I did make one change - I removed a $(TOP). Here is a more accurate
representation:
MAKETARGET = $(MAKE) --no-print-directory -C $(TOP)/.../some/other/path -f
$(CURDIR)/Makefile \
SRCDIR=$(CURDIR) $(MAKECMDGOALS)
I placed an echo of $(TOP)/.../some/other/path immediately prior to the
invocation of MAKETARGET and that path matched the path in the error message
exactly. $(TOP) contains only ``/home/vmuser/Work/software-internal`` .
Doug
-----Original Message-----
From: Paul Smith [mailto:address@hidden
Sent: January-21-14 12:27 PM
To: Doug Konrad
Cc: address@hidden
Subject: Re: Is -C @ magical?
On Tue, 2014-01-21 at 20:08 +0000, Doug Konrad wrote:
> Paul,
>
> If I use the MAKETARGET line as I entered it in my email, everything works as
> it should. However, if I edit the line to be:
>
> MAKETARGET = $(MAKE) --no-print-directory -C /.../some/other/path -f
> $(CURDIR)/Makefile \
> SRCDIR=$(CURDIR) $(MAKECMDGOALS)
>
> Then I get
>
> make[3]: *** No rule to make target `/.../some/other/path /Makefile'. Stop.
>
> It seems that $(CURDIR)/Makefile is pointing somewhere else.
Is the error message above verbatim, including the embedded space in the
pathname after "path" and before "/Makefile"?
That's ultra-bizarre. Can you provide a reproducible case (cut down)?
You're really just replacing the $@ with a simple explicit path exactly as you
show above? No quoting, make variables, etc.?
Can you also paste the recursive make command that make is invoking?
You might have to remove the "@" so it will be printed. That should definitely
be illuminating.