[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: diagnose target clashes (for PR/344)
From: |
Akim Demaille |
Subject: |
Re: RFC: diagnose target clashes (for PR/344) |
Date: |
13 Sep 2002 09:47:34 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
| >>> "adl" == Alexandre Duret-Lutz <address@hidden> writes:
| [...]
|
| adl> I've not run the full test suite yet (only the first half of it
| adl> plus specflag{7,8}.test); it's too late now.
|
| I've done a full `make check' now. Everything passes except
| `subpkg.test'. This one aborts with:
|
| automake: `LDADD' is a target; expected a variable
|
| (`LDADD' is the name of the binary in this test case.)
|
| Apparently, with this patch I've fixed something that prevented
| this diagnostic from occuring. (I'm not sure what.)
|
| Now I'm wondering if this error still makes any sense today.
| I guess it was because targets and variables used to share
| the same namespace in older versions of Automake?
As far as I remember, I kept this message in one case only: when we
were expecting one defined variable, but it turned out only a target
of the same name was defined, in which case, rather than saying
`undefined variable', a message like `you gave a target name where a
var name was wanted' seemed more helping.
- RFC: diagnose target clashes (for PR/344), Alexandre Duret-Lutz, 2002/09/10
- Re: RFC: diagnose target clashes (for PR/344), Richard Boulton, 2002/09/11
- Re: RFC: diagnose target clashes (for PR/344), Alexandre Duret-Lutz, 2002/09/11
- Re: RFC: diagnose target clashes (for PR/344),
Akim Demaille <=
- Re: RFC: diagnose target clashes (for PR/344), Tom Tromey, 2002/09/11
- Re: RFC: diagnose target clashes (for PR/344), Akim Demaille, 2002/09/13
- FYI: diagnose target clashes (for PR/344), Alexandre Duret-Lutz, 2002/09/13