[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make target conflict
From: |
James |
Subject: |
Re: make target conflict |
Date: |
5 Feb 2007 15:19:35 -0800 |
User-agent: |
G2/1.0 |
On Feb 5, 11:43 am, Ralf Wildenhues <Ralf.Wildenh...@gmx.de> wrote:
> * James wrote on Mon, Feb 05, 2007 at 08:36:16PM CET:
>
>
>
> > all: T aa/../T
> > T:
> > @echo $@
> > aa/../T:
> > @echo $@
>
> > Should make complain about the duplicate targets?
>
> Hmm. Are you sure they are duplicate? Even if make executes the
> following in parallel? Conversely: how should make ever be able
> to know for certain?
>
> all: T symlink aa/../T
> T:
> @echo $@
> aa/../T:
> @echo $@
> symlink:
> -rmdir aa
> mkdir sub sub/sub
> ln -s sub/sub aa
>
> Cheers,
> Ralf
Re-phrasing the question:
Does "make" interpret what the target points to, or just consider it
as a string?
Seems like as long as the strings are different, they are considered
different.
The same can be said about relative path and absolute path.
aa/file:
$(CURDIR)/aa/file:
These 2 are considered as different targets.
Is there a "make" option to force make to consider these as the same
targets?
James