On 10/26/21 3:20 PM, Alejandro Colomar (man-pages) wrote:
Hi Paul and Dmitry,
On 10/26/21 1:16 AM, Paul Smith wrote:
On Mon, 2021-10-25 at 17:51 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
On Monday, October 25, 2021, Alejandro Colomar (man-pages) <
Hi Paul and Dmitry,
On 10/26/21 1:16 AM, Paul Smith wrote:
On Mon, 2021-10-25 at 17:51 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
On Monday, October 25, 2021, Alejandro Colomar (man-pages) <
alx.manpa...@gmail.com> wrote:
Why do I do this? Because, if you
On Mon, 2021-10-25 at 17:51 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
> On Monday, October 25, 2021, Alejandro Colomar (man-pages) <
> alx.manpa...@gmail.com> wrote:
> > Why do I do this? Because, if you remove a file from your tree, an
> > old .d file will
On Monday, October 25, 2021, Alejandro Colomar (man-pages) <
alx.manpa...@gmail.com> wrote:
> However, there's a downside to this: The payment for this robustness is a
> non-negligible time cost. The single-process time for a no-op make is
> around 10 s
>
> 10s is about 100 to 1000 times
On Monday, October 25, 2021, Alejandro Colomar (man-pages) <
alx.manpa...@gmail.com> wrote:
>
>
> Why do I do this? Because, if you remove a file from your tree, an old .d
> file will require that file and make your build fail, requiring you to
> clean before making again.
>
>
This has been
Hi all,
Regarding the generation of .d files, I may be a bit paranoid, but I
like to regenerate them unconditionally at the beginning of every make
invocation. I wouldn't trust on .d from my last build, since they may
be outdated.
Why do I do this? Because, if you remove a file from your
On Sun, Oct 17, 2021 at 11:17 PM Britton Kerin wrote:
> I got that but it sounds like the proposal is for it to do one thing
> if the file is a .d and otherwise something else?
The proposal is to see if the recipe is empty.
There is this statement in the manual
"If a rule has no prerequisites
On Mon, Oct 25, 2021 at 6:12 AM Edward Welbourne wrote:
> Surely that would solve your problem, without invasive surgery in GNU
> make, or special-case handling of .d files anywhere but your make file ?
Actually, my makefiles do not suffer from this. i use the technique
described here
On Mon, 2021-10-25 at 10:11 +, Edward Welbourne wrote:
> Dmitry Goncharov (17 October 2021 18:33) wrote:
> > i think, make should not print a warning when a .d file is missing.
> > make should proceed and create the missing file. However, when .d
> > is present, but make cannot include it,
Dmitry Goncharov (17 October 2021 18:33) wrote:
> i think, make should not print a warning when a .d file is missing. make
> should proceed and create the missing file. However, when .d is present, but
> make cannot include it, then make should print an error and stop.
Given that I always
On Sun, Oct 17, 2021 at 4:44 PM Dmitry Goncharov
wrote:
>
> On Sun, Oct 17, 2021 at 3:05 PM Britton Kerin wrote:
>
> > If I understand right that the idea is a special case for .d files
>
> The question being discussed is what to do when make cannot include a
> makefile.
I got that but it
On Sun, Oct 17, 2021 at 3:05 PM Britton Kerin wrote:
> If I understand right that the idea is a special case for .d files
The question being discussed is what to do when make cannot include a makefile.
regards, Dmitry
On Sun, Oct 17, 2021 at 8:33 AM Dmitry Goncharov
wrote:
>
> Follow-up Comment #8, bug #61226 (project make):
>
> > > Switching to -include robs the user of a useful message, should there be a
> real issue.
>
> > I'm not sure what this means: in what situation do we lose a useful
> message?
>
>
13 matches
Mail list logo
