[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug #62706] Restrict second expansion to targets which are being bu
From: |
Edward Welbourne |
Subject: |
Re: [bug #62706] Restrict second expansion to targets which are being built. |
Date: |
Tue, 5 Jul 2022 09:18:02 +0000 |
Dmitry Goncharov (5 July 2022 01:42) wrote (inter alia):
> 2. Causes all prerequisites to be second expanded in the same order
> they are being built.
Really ? I would have expected the order to be the exact reverse of the
order of building:
src = main.c
hdr = lib.h
prog: $$(src); $(CC) -o $@ $<
main.c: $$(hdr)
surely has to evaluate $$(src) to discover that prog depends on main.c,
and only after it's discovered that will it evaluate $$(hdr); but if
there were a rule to make main.c from lib.h that rule would be evaluated
before the rule for prog.
> This fixes byte order dependent order of second expanding
> prerequisites. See sv 62175.
That, at least, should be the case either way.
Eddy.
- [bug #62706] Restrict second expansion to targets which are being built., Dmitry Goncharov, 2022/07/04
- [bug #62706] Restrict second expansion to targets which are being built., Dmitry Goncharov, 2022/07/05
- [bug #62706] Restrict second expansion to targets which are being built., Dmitry Goncharov, 2022/07/09
- [bug #62706] Restrict second expansion to targets which are being built., Paul D. Smith, 2022/07/09
- [bug #62706] Restrict second expansion to targets which are being built., Dmitry Goncharov, 2022/07/23
- [bug #62706] Restrict second expansion to targets which are being built., Dmitry Goncharov, 2022/07/23
- [bug #62706] Restrict second expansion to targets which are being built., Paul D. Smith, 2022/07/30