Paul D. Smith <[EMAIL PROTECTED]> writes:
> Anyway, the idea was certainly performance: if a directory doesn't exist
> and there are no rules in your makefile to create it (that is, there are
> no targets that allow make to create that directory), then in make's
> model it can never exist, so re
%% Boris Kolpackov <[EMAIL PROTECTED]> writes:
bk> If /tmp/out exists (/tmp/out/bin and /tmp/out/obj do not exist)
bk> then everything works file. When /tmp/out does not exist make
bk> fails. I have to idea about the logic behind this.
I assume you meant to say "no idea" :).
Anyway, the id
Juergen Schmidt <[EMAIL PROTECTED]> writes:
> has anybody an idea on this or can help me?
I am not sure this will actually help you but here it goes.
GNU make makes some strange guesses (see make.c around line 99) when it
comes to files in directories that do not exist. Consider for example
th
hi,
has anybody an idea on this or can help me? I would be glad to know if i
make something wrong or if it is maybe a make problem.
Thanks in advance
Juergen
Juergen Schmidt wrote:
Hi,
i have problem with make when i try to generate the output anywhere
and using an absolute path. Please see my s
Hi,
i have problem with make when i try to generate the output anywhere and
using an absolute path. Please see my simple test makefile (when i run
make i am in /local/test/maketest where the source "maketest.c" is located):
**
OUT=/local/te