Hi Paul
On 7/31/22 14:36, Paul Smith wrote:
On Sun, 2022-07-31 at 11:45 +0200, Alejandro Colomar (man-pages) wrote:
If some new post-requisite "baz" was found while building either
"foo" or "bar", it would be built after those and be as if the user
had invoked &qu
Hi Paul
On 7/30/22 19:01, Paul Smith wrote:
On Mon, 2022-07-25 at 09:06 +, Edward Welbourne wrote:
On 7/22/22 16:20, Paul Smith wrote:
So, after all the "normal" goal targets were completed make would
proceed to run any "extra" goal targets that were added as part
of the processing of the
Hi Paul,
On 7/14/22 18:11, Paul Smith wrote:
On Thu, 2022-07-14 at 14:16 +0200, Alejandro Colomar wrote:
How can $localstatedir be $prefix/var and at the same time
$runstatedir be /var/run (notice no prefix) if it is defined as
$localstatedir/run.
This I don't know about: it might be a
Hello Sergei,
On 2/5/22 23:04, Sergei Trofimovich wrote:
> The idea of the change is to introduce non-deterministic ordering
> into goal and prerequisite traversal to imitate non-deterministic
> ordering of 'make -j' mode.
>
> The implementation is to reorder lists of goals to build and list
>
Hi Paul,
On 1/28/22 23:49, Paul Smith wrote:
> On Fri, 2022-01-28 at 01:09 +0100, Alejandro Colomar (man-pages) wrote:
>> I'd like make to warn about this. It took me a while to debug
>> a Makefile bug, which I thought was not happening, since make should
>> have warned me.
Hi Martin,
On 1/28/22 02:42, Martin Dorey wrote:
> That already seems to have been fixed:
Hmm, it seems that the bug is only triggered if the option is passed in
the Makefile itself with MAKEFLAGS+=...
I haven't tested make git HEAD, but I bet it's probably reproducible
there too. See below.
Hi,
Consider the following scenario:
$ ls
Makefile
$ cat Makefile
MAKEFLAGS += --warn-undefined-variables
a: $(foo)
touch $@
$ make
touch a
$ ls
a Makefile
I'd like make to warn about this. It took me a while to debug a
Makefile bug, which I thought was not happening, since make
Hi Paul,
On 1/8/22 21:43, Paul Smith wrote:
On Sat, 2022-01-08 at 21:37 +0100, Alejandro Colomar (man-pages) wrote:
Hi Dmitry,
On 1/7/22 17:48, Dmitry Goncharov wrote:
On Thu, Jan 6, 2022 at 2:13 PM Alejandro Colomar (man-pages)
wrote:
I could try to write a simpler Makefile
That would
On 1/8/22 21:40, Alejandro Colomar (man-pages) wrote:
On 1/8/22 21:37, Alejandro Colomar (man-pages) wrote:
Hi Dmitry,
On 1/7/22 17:48, Dmitry Goncharov wrote:
On Thu, Jan 6, 2022 at 2:13 PM Alejandro Colomar (man-pages)
wrote:
I could try to write a simpler Makefile
That would
On 1/8/22 21:37, Alejandro Colomar (man-pages) wrote:
Hi Dmitry,
On 1/7/22 17:48, Dmitry Goncharov wrote:
On Thu, Jan 6, 2022 at 2:13 PM Alejandro Colomar (man-pages)
wrote:
I could try to write a simpler Makefile
That would be good. We need to be able to reproduce the crash.
I
Hi Dmitry,
On 1/7/22 17:48, Dmitry Goncharov wrote:
On Thu, Jan 6, 2022 at 2:13 PM Alejandro Colomar (man-pages)
wrote:
I could try to write a simpler Makefile
That would be good. We need to be able to reproduce the crash.
I couldn't reproduce it with a simple Makefile with a few
Hi,
I wrote some script to use make(1) to run rc scripts in parallel.
When running make(1) without -j, it works fine. However, when I run it
in parallel (-j2, for the simplest thing), I run into a segfault (when
I'm lucky and the system doesn't simply black out forever).
I expected this
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) <
alx.ma
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,
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
Hi Paul!
On 10/25/21 10:32 PM, Paul Smith wrote:
On Mon, 2021-10-25 at 22:28 +0200, Alejandro Colomar (man-pages) wrote:
Since I use '--warn-undefined-variables', and also to help
readability to someone who may not know about this usage and may
wonder what does that $(V) mean, I used
Hello Paul, Dmitry, and David!
> On Sat, Oct 23, 2021 at 6:06 AM Paul Smith <mailto:psm...@gnu.org>> wrote:
>
> On Sat, 2021-10-23 at 03:01 +0200, Alejandro Colomar (man-pages)
wrote:
> > I'd like a project to use '--silent' by default, to have readable
>
Hi,
I'd like a project to use '--silent' by default, to have readable
output, and hide most of the full commands, which would be too noisy.
So, ideally, I'd like to have 'MAKEFLAGS += --silent' in the Makefile.
The output would be something like:
CC foo.o
CC bar.o
...
But then,
Hi Philip & David,
On 6/14/21 5:42 AM, Philip Guenther wrote:
On Sun, Jun 13, 2021 at 6:29 PM David A. Wheeler <mailto:dwhee...@dwheeler.com>> wrote:
> On Jun 13, 2021, at 5:44 PM, Alejandro Colomar (man-pages)
mailto:alx.manpa...@gmail.com>> wrote:
>
Let's say there's a project with a submake for each module.
If a module depends on a file of another module, it's the other module
that will have the recipe for it. For example, the shared library of a
module links to the shared library of another module. Each module will
have the rules for
20 matches
Mail list logo
