Re: Is parallel programing hard...

Re: Is parallel programing hard...

[Paul E. McKenney]

[ Adding the perfbook email list on CC. ]

On Sun, Jun 26, 2022 at 02:00:40AM +0000, Snir, Marc wrote:
> Hi:
> I got a fatal latex error trying to create the pdf on my own. I append
> below the last lines of the log and the full log. Latex seems to fail
> soon after \maketitle

This is a new one on me!

One workaround is to us int Dockerfile template under the docker/
subdirectory.  This is described in question 13 in FAQ-BUILD.txt
in the top-level directory.

What environment are you running in?  There are quirks for a few
of them.

> I send this FYI, in case it might help you; I loaded the pdf file,
> and this works for me.

Glad the PDF file worked!

Which reminds me, it is past time for me to do another release.

> Thanks for putting all this material on the web.

Glad you like it, and I hope that it proves helpful!

							Thanx, Paul

> Marc
> 
> 
> 
> 
> 
> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
> )
> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
> (Font)              scaled to size 12.0pt on input line 605.
> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
> (Font)              scaled to size 8.8pt on input line 605.
> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
> (Font)              scaled to size 6.6pt on input line 605.
> 
> 
> ! LaTeX Error: There's no line here to end.
> 
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H <return>  for immediate help.
>  ...
> 
> l.605 \IfTwoColumn
>                   {
> ?
> ! Emergency stop.
>  ...
> 
> l.605 \IfTwoColumn
>                   {
> Your command was ignored.
> Type  I <command> <return>  to replace it with another command,
> or  <return>  to continue without it.
> 
> 
> 
> 
> 

Re: Is parallel programing hard...

[Akira Yokosawa]

On Sat, 25 Jun 2022 20:03:51 -0700, Paul E. McKenney wrote:
> [ Adding the perfbook email list on CC. ]
> 

> On Sun, Jun 26, 2022 at 02:00:40AM +0000, Snir, Marc wrote:
>> Hi:
>> I got a fatal latex error trying to create the pdf on my own. I append
>> below the last lines of the log and the full log. Latex seems to fail
>> soon after \maketitle
> 
> This is a new one on me!
> 
> One workaround is to us int Dockerfile template under the docker/
> subdirectory.  This is described in question 13 in FAQ-BUILD.txt
> in the top-level directory.
> 
> What environment are you running in?  There are quirks for a few
> of them.
> 
>> I send this FYI, in case it might help you; I loaded the pdf file,
>> and this works for me.
> 
> Glad the PDF file worked!
> 
> Which reminds me, it is past time for me to do another release.
> 
>> Thanks for putting all this material on the web.
> 
> Glad you like it, and I hope that it proves helpful!
> 
> 							Thanx, Paul
> 
>> Marc

Hi Marc,

I see in your log, you are using vanilla TeX Live 2022.

I'm regularly building with vanilla TeX Live, and have not seen
such an error.

>>
>>
>>
>>
>>
>> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
>> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
>> )
>> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
>> (Font)              scaled to size 12.0pt on input line 605.
>> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
>> (Font)              scaled to size 8.8pt on input line 605.
>> LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
>> (Font)              scaled to size 6.6pt on input line 605.
>>
>>
>> ! LaTeX Error: There's no line here to end.

In my build, messages in the log around here proceeds as follows:

(/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
)
LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
(Font)              scaled to size 12.0pt on input line 607.
LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
(Font)              scaled to size 8.8pt on input line 607.
LaTeX Font Info:    Font shape `TS1/ntxtlf/m/n' will be
(Font)              scaled to size 6.6pt on input line 607.
LaTeX Font Info:    Trying to load font information for T1+lmtt on input line 6
07.

(/usr/local/texlive/2022/texmf-dist/tex/latex/lm/t1lmtt.fd
File: t1lmtt.fd 2015/05/01 v1.6.1 Font defs for Latin Modern
)

I think "Latin Modern" font is one of essential font packages on TeX Live
these days, but do you have the "lm" font package installed on your system?

        Thanks, Akira

>>
>>
>> See the LaTeX manual or LaTeX Companion for explanation.
>> Type  H <return>  for immediate help.
>>  ...
>>
>> l.605 \IfTwoColumn
>>                   {
>> ?
>> ! Emergency stop.
>>  ...
>>
>> l.605 \IfTwoColumn
>>                   {
>> Your command was ignored.
>> Type  I <command> <return>  to replace it with another command,
>> or  <return>  to continue without it.
>>
>>
>>
>>
>>
> 
> 

Re: Is parallel programing hard...

[Snir, Marc]

[-- Attachment #1: Type: text/plain, Size: 2896 bytes --]

lm is installed

On Jun 25, 2022, at 11:12 PM, Akira Yokosawa <akiyks@gmail.com<mailto:akiyks@gmail.com>> wrote:

On Sat, 25 Jun 2022 20:03:51 -0700, Paul E. McKenney wrote:
[ Adding the perfbook email list on CC. ]


On Sun, Jun 26, 2022 at 02:00:40AM +0000, Snir, Marc wrote:
Hi:
I got a fatal latex error trying to create the pdf on my own. I append
below the last lines of the log and the full log. Latex seems to fail
soon after \maketitle

This is a new one on me!

One workaround is to us int Dockerfile template under the docker/
subdirectory. This is described in question 13 in FAQ-BUILD.txt
in the top-level directory.

What environment are you running in? There are quirks for a few
of them.

I send this FYI, in case it might help you; I loaded the pdf file,
and this works for me.

Glad the PDF file worked!

Which reminds me, it is past time for me to do another release.

Thanks for putting all this material on the web.

Glad you like it, and I hope that it proves helpful!

Thanx, Paul

Marc

Hi Marc,

I see in your log, you are using vanilla TeX Live 2022.

I'm regularly building with vanilla TeX Live, and have not seen
such an error.






(/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
)
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 12.0pt on input line 605.
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 8.8pt on input line 605.
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 6.6pt on input line 605.


! LaTeX Error: There's no line here to end.

In my build, messages in the log around here proceeds as follows:

(/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
)
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 12.0pt on input line 607.
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 8.8pt on input line 607.
LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
(Font) scaled to size 6.6pt on input line 607.
LaTeX Font Info: Trying to load font information for T1+lmtt on input line 6
07.

(/usr/local/texlive/2022/texmf-dist/tex/latex/lm/t1lmtt.fd
File: t1lmtt.fd 2015/05/01 v1.6.1 Font defs for Latin Modern
)

I think "Latin Modern" font is one of essential font packages on TeX Live
these days, but do you have the "lm" font package installed on your system?

Thanks, Akira



See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...

l.605 \IfTwoColumn
{
?
! Emergency stop.
...

l.605 \IfTwoColumn
{
Your command was ignored.
Type I <command> <return> to replace it with another command,
or <return> to continue without it.


[-- Attachment #2: Type: text/html, Size: 26646 bytes --]

Re: Is parallel programing hard...

[Akira Yokosawa]

On Sun, 26 Jun 2022 18:52:26 +0000, Snir, Marc wrote:
> lm is installed
> 
>> On Jun 25, 2022, at 11:12 PM, Akira Yokosawa <akiyks@gmail.com <mailto:akiyks@gmail.com>> wrote:
>>
>> On Sat, 25 Jun 2022 20:03:51 -0700, Paul E. McKenney wrote:
>>> [ Adding the perfbook email list on CC. ]
>>>
>>
>>> On Sun, Jun 26, 2022 at 02:00:40AM +0000, Snir, Marc wrote:
>>>> Hi:
>>>> I got a fatal latex error trying to create the pdf on my own. I append
>>>> below the last lines of the log and the full log. Latex seems to fail
>>>> soon after \maketitle
>>>
>>> This is a new one on me!
>>>
>>> One workaround is to us int Dockerfile template under the docker/
>>> subdirectory. This is described in question 13 in FAQ-BUILD.txt
>>> in the top-level directory.
>>>
>>> What environment are you running in? There are quirks for a few
>>> of them.
>>>
>>>> I send this FYI, in case it might help you; I loaded the pdf file,
>>>> and this works for me.
>>>
>>> Glad the PDF file worked!
>>>
>>> Which reminds me, it is past time for me to do another release.
>>>
>>>> Thanks for putting all this material on the web.
>>>
>>> Glad you like it, and I hope that it proves helpful!
>>>
>>> Thanx, Paul
>>>
>>>> Marc
>>
>> Hi Marc,
>>
>> I see in your log, you are using vanilla TeX Live 2022.
>>
>> I'm regularly building with vanilla TeX Live, and have not seen
>> such an error.
>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
>>>> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
>>>> )
>>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>>>> (Font) scaled to size 12.0pt on input line 605.
>>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>>>> (Font) scaled to size 8.8pt on input line 605.
>>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>>>> (Font) scaled to size 6.6pt on input line 605.
>>>>
>>>>
>>>> ! LaTeX Error: There's no line here to end.
>>
>> In my build, messages in the log around here proceeds as follows:
>>
>> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
>> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
>> )
>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>> (Font) scaled to size 12.0pt on input line 607.
>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>> (Font) scaled to size 8.8pt on input line 607.
>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
>> (Font) scaled to size 6.6pt on input line 607.
>> LaTeX Font Info: Trying to load font information for T1+lmtt on input line 6
>> 07.
>>
>> (/usr/local/texlive/2022/texmf-dist/tex/latex/lm/t1lmtt.fd
>> File: t1lmtt.fd 2015/05/01 v1.6.1 Font defs for Latin Modern
>> )
>>
>> I think "Latin Modern" font is one of essential font packages on TeX Live
>> these days, but do you have the "lm" font package installed on your system?
>>
>> Thanks, Akira

For the record:

It turns out that Marc attempted the build under macOS 12.4, which
resulted in a corrupted autodate.tex.
It means utilities/autodate.sh doesn't work as expected under macOS.

The cause might be the difference of primitive tools such as "date",
"sed", and "grep".  We assume those from GNU, while macOS has those
of BSD origin.

As I don't have a macOS system at my disposal, I can't help further.

(I was surprised to know that the build scripts worked without a fatal
error until the first run of pdflatex.)

        Thanks, Akira

>>
>>>>
>>>>
>>>> See the LaTeX manual or LaTeX Companion for explanation.
>>>> Type H <return> for immediate help.
>>>> ...
>>>>
>>>> l.605 \IfTwoColumn
>>>> {
>>>> ?
>>>> ! Emergency stop.
>>>> ...
>>>>
>>>> l.605 \IfTwoColumn
>>>> {
>>>> Your command was ignored.
>>>> Type I <command> <return> to replace it with another command,
>>>> or <return> to continue without it.
> 

Re: Is parallel programing hard...

[Paul E. McKenney]

On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
> On Sun, 26 Jun 2022 18:52:26 +0000, Snir, Marc wrote:
> > lm is installed
> > 
> >> On Jun 25, 2022, at 11:12 PM, Akira Yokosawa <akiyks@gmail.com <mailto:akiyks@gmail.com>> wrote:
> >>
> >> On Sat, 25 Jun 2022 20:03:51 -0700, Paul E. McKenney wrote:
> >>> [ Adding the perfbook email list on CC. ]
> >>>
> >>
> >>> On Sun, Jun 26, 2022 at 02:00:40AM +0000, Snir, Marc wrote:
> >>>> Hi:
> >>>> I got a fatal latex error trying to create the pdf on my own. I append
> >>>> below the last lines of the log and the full log. Latex seems to fail
> >>>> soon after \maketitle
> >>>
> >>> This is a new one on me!
> >>>
> >>> One workaround is to us int Dockerfile template under the docker/
> >>> subdirectory. This is described in question 13 in FAQ-BUILD.txt
> >>> in the top-level directory.
> >>>
> >>> What environment are you running in? There are quirks for a few
> >>> of them.
> >>>
> >>>> I send this FYI, in case it might help you; I loaded the pdf file,
> >>>> and this works for me.
> >>>
> >>> Glad the PDF file worked!
> >>>
> >>> Which reminds me, it is past time for me to do another release.
> >>>
> >>>> Thanks for putting all this material on the web.
> >>>
> >>> Glad you like it, and I hope that it proves helpful!
> >>>
> >>> Thanx, Paul
> >>>
> >>>> Marc
> >>
> >> Hi Marc,
> >>
> >> I see in your log, you are using vanilla TeX Live 2022.
> >>
> >> I'm regularly building with vanilla TeX Live, and have not seen
> >> such an error.
> >>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
> >>>> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
> >>>> )
> >>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >>>> (Font) scaled to size 12.0pt on input line 605.
> >>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >>>> (Font) scaled to size 8.8pt on input line 605.
> >>>> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >>>> (Font) scaled to size 6.6pt on input line 605.
> >>>>
> >>>>
> >>>> ! LaTeX Error: There's no line here to end.
> >>
> >> In my build, messages in the log around here proceeds as follows:
> >>
> >> (/usr/local/texlive/2022/texmf-dist/tex/latex/newtx/ts1ntxtlf.fd
> >> File: ts1ntxtlf.fd 2015/01/18 v1.0 fd file for TS1/ntxtlf
> >> )
> >> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >> (Font) scaled to size 12.0pt on input line 607.
> >> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >> (Font) scaled to size 8.8pt on input line 607.
> >> LaTeX Font Info: Font shape `TS1/ntxtlf/m/n' will be
> >> (Font) scaled to size 6.6pt on input line 607.
> >> LaTeX Font Info: Trying to load font information for T1+lmtt on input line 6
> >> 07.
> >>
> >> (/usr/local/texlive/2022/texmf-dist/tex/latex/lm/t1lmtt.fd
> >> File: t1lmtt.fd 2015/05/01 v1.6.1 Font defs for Latin Modern
> >> )
> >>
> >> I think "Latin Modern" font is one of essential font packages on TeX Live
> >> these days, but do you have the "lm" font package installed on your system?
> >>
> >> Thanks, Akira
> 
> For the record:
> 
> It turns out that Marc attempted the build under macOS 12.4, which
> resulted in a corrupted autodate.tex.
> It means utilities/autodate.sh doesn't work as expected under macOS.
> 
> The cause might be the difference of primitive tools such as "date",
> "sed", and "grep".  We assume those from GNU, while macOS has those
> of BSD origin.
> 
> As I don't have a macOS system at my disposal, I can't help further.
> 
> (I was surprised to know that the build scripts worked without a fatal
> error until the first run of pdflatex.)

In theory, it is possible to use the "findutils" and "brew" commands to
set up gnu utilities on MacOS, and to do so such that your PATH variable
can be used to choose whether the default is the MacOS versions or the
gnu versions.  Or so it says here:

https://www.google.com/search?q=latex+on+macos&oq=latex+on+macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8

I do have an old MacOS system, but it is at home and I am on travel.
I would need to install LaTeX on it (last time I tried, the installation
hung), but Marc proved that it is possible to actually install it.  ;-) If
I can pass that hurdle, I will try making perfbook use the gnu utilities.

Or is this where someone tells me that  LaTeX on MacOS make use of
scripts that rely on the MacOS variants of these commands?  ;-)

Thoughts?

							Thanx, Paul

> >>>> See the LaTeX manual or LaTeX Companion for explanation.
> >>>> Type H <return> for immediate help.
> >>>> ...
> >>>>
> >>>> l.605 \IfTwoColumn
> >>>> {
> >>>> ?
> >>>> ! Emergency stop.
> >>>> ...
> >>>>
> >>>> l.605 \IfTwoColumn
> >>>> {
> >>>> Your command was ignored.
> >>>> Type I <command> <return> to replace it with another command,
> >>>> or <return> to continue without it.
> > 

Re: Is parallel programing hard...

[Akira Yokosawa]

On Mon, 27 Jun 2022 07:11:06 -0700, Paul E. McKenney wrote:
> On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
[...]
>>
>> For the record:
>>
>> It turns out that Marc attempted the build under macOS 12.4, which
>> resulted in a corrupted autodate.tex.
>> It means utilities/autodate.sh doesn't work as expected under macOS.
>>
>> The cause might be the difference of primitive tools such as "date",
>> "sed", and "grep".  We assume those from GNU, while macOS has those
>> of BSD origin.
>>
>> As I don't have a macOS system at my disposal, I can't help further.
>>
>> (I was surprised to know that the build scripts worked without a fatal
>> error until the first run of pdflatex.)
> 
> In theory, it is possible to use the "findutils" and "brew" commands to
> set up gnu utilities on MacOS, and to do so such that your PATH variable
> can be used to choose whether the default is the MacOS versions or the
> gnu versions.  Or so it says here:
> 
> https://www.google.com/search?q=latex+on+macos&oq=latex+on+macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8
> 
> I do have an old MacOS system, but it is at home and I am on travel.

How old is it?  :-)

> I would need to install LaTeX on it (last time I tried, the installation
> hung), but Marc proved that it is possible to actually install it.  ;-) If
> I can pass that hurdle, I will try making perfbook use the gnu utilities.
> 
> Or is this where someone tells me that  LaTeX on MacOS make use of
> scripts that rely on the MacOS variants of these commands?  ;-)

I don't think so.
If you can make scripts under utilities/ behave as expected,
"make" should work.

Except:

Some of perl scripts have shebang lines of:

    #!/usr/bin/perl

, and are invoked directly from recipes in Makefile.
You need to change them to:

    #!/usr/bin/env perl

, so that your PATH setting is respected.  You might need similar
tweaks for scripts of other languages.

Good luck!

        Thanks, Akira

> 
> Thoughts?
> 
> 							Thanx, Paul
> 
[...]

Re: Is parallel programing hard...

[Paul E. McKenney]

On Mon, Jun 27, 2022 at 11:52:18PM +0900, Akira Yokosawa wrote:
> On Mon, 27 Jun 2022 07:11:06 -0700, Paul E. McKenney wrote:
> > On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
> [...]
> >>
> >> For the record:
> >>
> >> It turns out that Marc attempted the build under macOS 12.4, which
> >> resulted in a corrupted autodate.tex.
> >> It means utilities/autodate.sh doesn't work as expected under macOS.
> >>
> >> The cause might be the difference of primitive tools such as "date",
> >> "sed", and "grep".  We assume those from GNU, while macOS has those
> >> of BSD origin.
> >>
> >> As I don't have a macOS system at my disposal, I can't help further.
> >>
> >> (I was surprised to know that the build scripts worked without a fatal
> >> error until the first run of pdflatex.)
> > 
> > In theory, it is possible to use the "findutils" and "brew" commands to
> > set up gnu utilities on MacOS, and to do so such that your PATH variable
> > can be used to choose whether the default is the MacOS versions or the
> > gnu versions.  Or so it says here:
> > 
> > https://www.google.com/search?q=latex+on+macos&oq=latex+on+macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8
> > 
> > I do have an old MacOS system, but it is at home and I am on travel.
> 
> How old is it?  :-)

About three years, but running a current MacOS.

> > I would need to install LaTeX on it (last time I tried, the installation
> > hung), but Marc proved that it is possible to actually install it.  ;-) If
> > I can pass that hurdle, I will try making perfbook use the gnu utilities.
> > 
> > Or is this where someone tells me that  LaTeX on MacOS make use of
> > scripts that rely on the MacOS variants of these commands?  ;-)
> 
> I don't think so.
> If you can make scripts under utilities/ behave as expected,
> "make" should work.
> 
> Except:
> 
> Some of perl scripts have shebang lines of:
> 
>     #!/usr/bin/perl
> 
> , and are invoked directly from recipes in Makefile.
> You need to change them to:
> 
>     #!/usr/bin/env perl
> 
> , so that your PATH setting is respected.  You might need similar
> tweaks for scripts of other languages.
> 
> Good luck!

I will need it.  ;-)

							Thanx, Paul

>         Thanks, Akira
> 
> > 
> > Thoughts?
> > 
> > 							Thanx, Paul
> > 
> [...]

Re: Is parallel programing hard...

[Akira Yokosawa]

On Mon, 27 Jun 2022 07:56:28 -0700, Paul E. McKenney wrote:
> On Mon, Jun 27, 2022 at 11:52:18PM +0900, Akira Yokosawa wrote:
>> On Mon, 27 Jun 2022 07:11:06 -0700, Paul E. McKenney wrote:
>>> On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
>> [...]
>>>>
>>>> For the record:
>>>>
>>>> It turns out that Marc attempted the build under macOS 12.4, which
>>>> resulted in a corrupted autodate.tex.
>>>> It means utilities/autodate.sh doesn't work as expected under macOS.
>>>>
>>>> The cause might be the difference of primitive tools such as "date",
>>>> "sed", and "grep".  We assume those from GNU, while macOS has those
>>>> of BSD origin.
>>>>
>>>> As I don't have a macOS system at my disposal, I can't help further.
>>>>
>>>> (I was surprised to know that the build scripts worked without a fatal
>>>> error until the first run of pdflatex.)
>>>
>>> In theory, it is possible to use the "findutils" and "brew" commands to
>>> set up gnu utilities on MacOS, and to do so such that your PATH variable
>>> can be used to choose whether the default is the MacOS versions or the
>>> gnu versions.  Or so it says here:
>>>
>>> https://www.google.com/search?q=latex+on+macos&oq=latex+on+macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8
>>>
>>> I do have an old MacOS system, but it is at home and I am on travel.
>>
>> How old is it?  :-)
> 
> About three years, but running a current MacOS.
> 
>>> I would need to install LaTeX on it (last time I tried, the installation
>>> hung), but Marc proved that it is possible to actually install it.  ;-) If
>>> I can pass that hurdle, I will try making perfbook use the gnu utilities.
>>>
>>> Or is this where someone tells me that  LaTeX on MacOS make use of
>>> scripts that rely on the MacOS variants of these commands?  ;-)
>>
>> I don't think so.
>> If you can make scripts under utilities/ behave as expected,
>> "make" should work.
>>
>> Except:
>>
>> Some of perl scripts have shebang lines of:
>>
>>     #!/usr/bin/perl
>>
>> , and are invoked directly from recipes in Makefile.
>> You need to change them to:
>>
>>     #!/usr/bin/env perl
>>
>> , so that your PATH setting is respected.  You might need similar
>> tweaks for scripts of other languages.
I was confused.  perl is perl.  There is no GNU or BSD flavor...

        Thanks, Akira

>>
>> Good luck!
> 
> I will need it.  ;-)
> 
> 							Thanx, Paul
> 
>>         Thanks, Akira
>>
>>>
>>> Thoughts?
>>>
>>> 							Thanx, Paul
>>>
>> [...]

Re: Is parallel programing hard...

[Snir, Marc]

[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]

I used MacTex to install Latex and mostly used Brew to install Linux tools

On Jun 27, 2022, at 10:19 AM, Akira Yokosawa <akiyks@gmail.com<mailto:akiyks@gmail.com>> wrote:

On Mon, 27 Jun 2022 07:56:28 -0700, Paul E. McKenney wrote:
On Mon, Jun 27, 2022 at 11:52:18PM +0900, Akira Yokosawa wrote:
On Mon, 27 Jun 2022 07:11:06 -0700, Paul E. McKenney wrote:
On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
[...]

For the record:

It turns out that Marc attempted the build under macOS 12.4, which
resulted in a corrupted autodate.tex.
It means utilities/autodate.sh doesn't work as expected under macOS.

The cause might be the difference of primitive tools such as "date",
"sed", and "grep". We assume those from GNU, while macOS has those
of BSD origin.

As I don't have a macOS system at my disposal, I can't help further.

(I was surprised to know that the build scripts worked without a fatal
error until the first run of pdflatex.)

In theory, it is possible to use the "findutils" and "brew" commands to
set up gnu utilities on MacOS, and to do so such that your PATH variable
can be used to choose whether the default is the MacOS versions or the
gnu versions. Or so it says here:

https://urldefense.com/v3/__https://www.google.com/search?q=latex*on*macos&oq=latex*on*macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8__;KysrKw!!DZ3fjg!4_j5YLKDbzfq9B7h6-F8zxtMnksVmYkZGrTI8UNScPy0Hqxl4_ieTdmHu_WSoG9aMUBWzuwNnob4gw$

I do have an old MacOS system, but it is at home and I am on travel.

How old is it? :-)

About three years, but running a current MacOS.

I would need to install LaTeX on it (last time I tried, the installation
hung), but Marc proved that it is possible to actually install it. ;-) If
I can pass that hurdle, I will try making perfbook use the gnu utilities.

Or is this where someone tells me that LaTeX on MacOS make use of
scripts that rely on the MacOS variants of these commands? ;-)

I don't think so.
If you can make scripts under utilities/ behave as expected,
"make" should work.

Except:

Some of perl scripts have shebang lines of:

#!/usr/bin/perl

, and are invoked directly from recipes in Makefile.
You need to change them to:

#!/usr/bin/env perl

, so that your PATH setting is respected. You might need similar
tweaks for scripts of other languages.
I was confused. perl is perl. There is no GNU or BSD flavor...

Thanks, Akira


Good luck!

I will need it. ;-)

Thanx, Paul

Thanks, Akira


Thoughts?

Thanx, Paul

[...]


[-- Attachment #2: Type: text/html, Size: 9311 bytes --]

Re: Is parallel programing hard...

[Paul E. McKenney]

OK, MacTex worked much better for me, meaning that this time it did
not hang when I attempted to install it.  However, once installed,
it complains that it is missing xcrun, whatever that might be.

My thought is to get a release out, then see what can be done about
making this build on MacOS.  Seem reasonable?

Hey, I said I had access to MacOS, not that I was at all competent at
installing software on it.  ;-)

							Thanx, Paul

On Mon, Jun 27, 2022 at 03:36:20PM +0000, Snir, Marc wrote:
> I used MacTex to install Latex and mostly used Brew to install Linux tools
> 
> On Jun 27, 2022, at 10:19 AM, Akira Yokosawa <akiyks@gmail.com<mailto:akiyks@gmail.com>> wrote:
> 
> On Mon, 27 Jun 2022 07:56:28 -0700, Paul E. McKenney wrote:
> On Mon, Jun 27, 2022 at 11:52:18PM +0900, Akira Yokosawa wrote:
> On Mon, 27 Jun 2022 07:11:06 -0700, Paul E. McKenney wrote:
> On Mon, Jun 27, 2022 at 07:32:29PM +0900, Akira Yokosawa wrote:
> [...]
> 
> For the record:
> 
> It turns out that Marc attempted the build under macOS 12.4, which
> resulted in a corrupted autodate.tex.
> It means utilities/autodate.sh doesn't work as expected under macOS.
> 
> The cause might be the difference of primitive tools such as "date",
> "sed", and "grep". We assume those from GNU, while macOS has those
> of BSD origin.
> 
> As I don't have a macOS system at my disposal, I can't help further.
> 
> (I was surprised to know that the build scripts worked without a fatal
> error until the first run of pdflatex.)
> 
> In theory, it is possible to use the "findutils" and "brew" commands to
> set up gnu utilities on MacOS, and to do so such that your PATH variable
> can be used to choose whether the default is the MacOS versions or the
> gnu versions. Or so it says here:
> 
> https://urldefense.com/v3/__https://www.google.com/search?q=latex*on*macos&oq=latex*on*macos&aqs=chrome..69i57j0i22i30l9.3869j1j7&client=ubuntu&sourceid=chrome&ie=UTF-8__;KysrKw!!DZ3fjg!4_j5YLKDbzfq9B7h6-F8zxtMnksVmYkZGrTI8UNScPy0Hqxl4_ieTdmHu_WSoG9aMUBWzuwNnob4gw$
> 
> I do have an old MacOS system, but it is at home and I am on travel.
> 
> How old is it? :-)
> 
> About three years, but running a current MacOS.
> 
> I would need to install LaTeX on it (last time I tried, the installation
> hung), but Marc proved that it is possible to actually install it. ;-) If
> I can pass that hurdle, I will try making perfbook use the gnu utilities.
> 
> Or is this where someone tells me that LaTeX on MacOS make use of
> scripts that rely on the MacOS variants of these commands? ;-)
> 
> I don't think so.
> If you can make scripts under utilities/ behave as expected,
> "make" should work.
> 
> Except:
> 
> Some of perl scripts have shebang lines of:
> 
> #!/usr/bin/perl
> 
> , and are invoked directly from recipes in Makefile.
> You need to change them to:
> 
> #!/usr/bin/env perl
> 
> , so that your PATH setting is respected. You might need similar
> tweaks for scripts of other languages.
> I was confused. perl is perl. There is no GNU or BSD flavor...
> 
> Thanks, Akira
> 
> 
> Good luck!
> 
> I will need it. ;-)
> 
> Thanx, Paul
> 
> Thanks, Akira
> 
> 
> Thoughts?
> 
> Thanx, Paul
> 
> [...]
> 

Re: Is parallel programing hard...

[Akira Yokosawa]

On Wed, 29 Jun 2022 17:27:20 -0700, Paul E. McKenney wrote:
> OK, MacTex worked much better for me, meaning that this time it did
> not hang when I attempted to install it.  However, once installed,
> it complains that it is missing xcrun, whatever that might be.

In search of "macOS 12 xcrun error", I got the following:

https://osxdaily.com/2021/07/19/fix-xcrun-error-invalid-active-developer-path-error-terminal-mac/

Is your issue similar to this one?

(I have no experience with macOS, so take this as just a hint.)

> 
> My thought is to get a release out, then see what can be done about
> making this build on MacOS.  Seem reasonable?

Sounds reasonable to me!

        Thanks, Akira

> 
> Hey, I said I had access to MacOS, not that I was at all competent at
> installing software on it.  ;-)
> 
> 							Thanx, Paul
> 
[...]

Re: Is parallel programing hard...

[Paul E. McKenney]

On Thu, Jun 30, 2022 at 11:18:46PM +0900, Akira Yokosawa wrote:
> On Wed, 29 Jun 2022 17:27:20 -0700, Paul E. McKenney wrote:
> > OK, MacTex worked much better for me, meaning that this time it did
> > not hang when I attempted to install it.  However, once installed,
> > it complains that it is missing xcrun, whatever that might be.
> 
> In search of "macOS 12 xcrun error", I got the following:
> 
> https://osxdaily.com/2021/07/19/fix-xcrun-error-invalid-active-developer-path-error-terminal-mac/
> 
> Is your issue similar to this one?
> 
> (I have no experience with macOS, so take this as just a hint.)

I have no idea, but I will give it a try later today, Pacific Time.
Either way, thank you for the hint!

> > My thought is to get a release out, then see what can be done about
> > making this build on MacOS.  Seem reasonable?
> 
> Sounds reasonable to me!

Very good, I believe I am a bit overdue for a release anyway.  After all,
we have 156 commits since the last release.  ;-)

							Thanx, Paul

>         Thanks, Akira
> 
> > 
> > Hey, I said I had access to MacOS, not that I was at all competent at
> > installing software on it.  ;-)
> > 
> > 							Thanx, Paul
> > 
> [...]

Re: Is parallel programing hard...

[Paul E. McKenney]

On Thu, Jun 30, 2022 at 07:26:16AM -0700, Paul E. McKenney wrote:
> On Thu, Jun 30, 2022 at 11:18:46PM +0900, Akira Yokosawa wrote:
> > On Wed, 29 Jun 2022 17:27:20 -0700, Paul E. McKenney wrote:
> > > OK, MacTex worked much better for me, meaning that this time it did
> > > not hang when I attempted to install it.  However, once installed,
> > > it complains that it is missing xcrun, whatever that might be.
> > 
> > In search of "macOS 12 xcrun error", I got the following:
> > 
> > https://osxdaily.com/2021/07/19/fix-xcrun-error-invalid-active-developer-path-error-terminal-mac/
> > 
> > Is your issue similar to this one?
> > 
> > (I have no experience with macOS, so take this as just a hint.)
> 
> I have no idea, but I will give it a try later today, Pacific Time.
> Either way, thank you for the hint!

OK, it does take some time to install.  But I at least started the
process today.  ;-)

							Thanx, Paul

> > > My thought is to get a release out, then see what can be done about
> > > making this build on MacOS.  Seem reasonable?
> > 
> > Sounds reasonable to me!
> 
> Very good, I believe I am a bit overdue for a release anyway.  After all,
> we have 156 commits since the last release.  ;-)
> 
> 							Thanx, Paul
> 
> >         Thanks, Akira
> > 
> > > 
> > > Hey, I said I had access to MacOS, not that I was at all competent at
> > > installing software on it.  ;-)
> > > 
> > > 							Thanx, Paul
> > > 
> > [...]

Re: Is parallel programing hard...

[Paul E. McKenney]

On Thu, Jun 30, 2022 at 05:19:09PM -0700, Paul E. McKenney wrote:
> On Thu, Jun 30, 2022 at 07:26:16AM -0700, Paul E. McKenney wrote:
> > On Thu, Jun 30, 2022 at 11:18:46PM +0900, Akira Yokosawa wrote:
> > > On Wed, 29 Jun 2022 17:27:20 -0700, Paul E. McKenney wrote:
> > > > OK, MacTex worked much better for me, meaning that this time it did
> > > > not hang when I attempted to install it.  However, once installed,
> > > > it complains that it is missing xcrun, whatever that might be.
> > > 
> > > In search of "macOS 12 xcrun error", I got the following:
> > > 
> > > https://osxdaily.com/2021/07/19/fix-xcrun-error-invalid-active-developer-path-error-terminal-mac/
> > > 
> > > Is your issue similar to this one?
> > > 
> > > (I have no experience with macOS, so take this as just a hint.)
> > 
> > I have no idea, but I will give it a try later today, Pacific Time.
> > Either way, thank you for the hint!
> 
> OK, it does take some time to install.  But I at least started the
> process today.  ;-)

And some colleagues who use MacBooks swear by something called Overleaf:

https://www.overleaf.com/

They use free accounts, which limit you to six projects.  No idea myself,
just passing this on.

							Thanx, Paul


> > > > My thought is to get a release out, then see what can be done about
> > > > making this build on MacOS.  Seem reasonable?
> > > 
> > > Sounds reasonable to me!
> > 
> > Very good, I believe I am a bit overdue for a release anyway.  After all,
> > we have 156 commits since the last release.  ;-)
> > 
> > 							Thanx, Paul
> > 
> > >         Thanks, Akira
> > > 
> > > > 
> > > > Hey, I said I had access to MacOS, not that I was at all competent at
> > > > installing software on it.  ;-)
> > > > 
> > > > 							Thanx, Paul
> > > > 
> > > [...]