Re: multi-threaded compiling

[alex xmb sw ratchev]

other output

~/2024031100 - gnu questions/one $ make
SECONDS=5; for (( i=0;i<32;i++ )); do { exit ${i}; } & pid[${i}]=${!};
done; sleep ${SECONDS}; for (( i=0;i<32;i++ )); do wait -n ${pid[${i}]};
e=${?}; echo "$(printf %3u ${i}) pid ${pid[${i}]} exit ${e}"; done;
/data/data/com.termux/files/usr/bin/sh: 1: Syntax error: Bad for loop
variable
make: *** [Makefile:3: all] Error 2
~/2024031100 - gnu questions/one $ cd ..
~/2024031100 - gnu questions $ cd two
~/2024031100 - gnu questions/two $ make
STRINGIZED: 0, STRING: one and two
STRINGIZED: 0, STRING: one and two
STRINGIZED: 1, STRING: one and two
STRINGIZED: 1, STRING: one and two
STRINGIZED: 0, STRING: one and two
STRINGIZED: 0, STRING: one and two
STRINGIZED: 1, STRING: one and two
STRINGIZED: 1, STRING: one and two
STRINGIZED: 0, STRING: one and two
STRINGIZED: 0, STRING: one and two
STRINGIZED: 1, STRING: one and two
STRINGIZED: 1, STRING: one and two

On Mon, Mar 11, 2024, 18:54 Mischa Baars <mjbaars1977.backup@gmail.com>
wrote:

> Oh, ok. I have executed the examples for you now.
>
> What I expected was also in the first mail:
>
> 1) The one.make.sh.log has the expected output. The same commands executed
> from a Makefile (one.make.log) do not behave as expected. This also holds
> for this command executed from the command line.
> 2) The two.make.log has the expected. The same commands executed from the
> bash script do not behave as expected. I'm having trouble obtaining the
> desired results with the bash script.
>
> Regards,
> Mischa Baars.
>
> On Mon, Mar 11, 2024 at 6:27 PM Paul Smith <psmith@gnu.org> wrote:
>
> > On Mon, 2024-03-11 at 18:14 +0100, Mischa Baars wrote:
> > > The actual command invocations (a Makefile, a make.sh script) can be
> > > found in the attachment, as indicated on the first line of the mail.
> > > In the attachment there are two directories, one and two, belonging
> > > to 1) and 2) respectively.
> >
> > That's not what I asked: I asked YOU to run the commands on YOUR system
> > and cut and paste the results of the run into your email message, with
> > an explicit explanation of exactly what is wrong with the results and
> > what you wanted to see instead.  What errors did you get?  Or what was
> > unexpected about the behavior?
> >
> > I'm not interested in running random scripts on my system that were
> > downloaded from an email, or examining their behavior to make sure
> > they're OK, or setting up a container to run them in, or guessing what
> > you wanted to happen, etc.
> >
>
> A container? These are no viri, these are scripts :)
>
>
> > Or maybe someone else will want to do that work instead.
> >
> > But before putting in more effort on the "misbehaving" makefile, read
> > this part of my response carefully:
> >
> > > But before you do that, be aware that make does NOT invoke /bin/bash
> > > as its shell.  It invokes /bin/sh.  On some systems /bin/sh is
> > > actually an alias for bash.  On other systems it isn't.
> > >
> > > If you want your makefile to always use bash as its shell, you should
> > > add an explicit:
> > >
> > >     SHELL := /bin/bash
> > >
> > > to your makefile to force it.  Maybe that will solve your problem.
> > > If not we'll need details such as I mention above.
> >
> > and verify in your response you added the suggested line to your
> > makefile and it didn't help (in the situation where the makefile was
> > behaving in an unexpected way).
> >
>
> No. Doesn't help the tiniest bit.
>