Using a macro makes pdfetex quits and exits with bad status

Don't expect this list to support you in that adventure ????
How very convenient!

I want get the regular development snapshot to test the work in progress,
building it separately, from source, at another location.

The problem with PATH occurred after texi2pdf called texi2dvi

I used

cd /home/hagbard/Admir/build/texinfo
../../source/texinfo/configure --prefix=/home/hagbard/Admir/bin/texinfo
make
sudo make install
make TEXMF=/home/hagbard/Admir/bin/texinfo/bin install-tex

Have only been doing what I have been instructed to do.  But I have
observed some maintainers who consistently ridicule users for deviating
from the mainstream use of the software.  Why can't I have multiple versions
of the program and run the ones I want?  Perhaps texinfo is a pain and you
are unable to handle a solution that is straightforward.  At least Gavin
tries his best to understand the difficulties users face, unlike some others.

Can you give we a scheme that works so I can test the development version
independently of any other texinfo setup I have?

> Sent: Friday, June 25, 2021 at 4:16 AM
> From: "Eli Zaretskii" <[email protected]>
> To: "Christopher Dimech" <[email protected]>
> Cc: [email protected], [email protected]
> Subject: Re: Using a macro makes pdfetex quits and exits with bad status
>
> > From: Christopher Dimech <[email protected]>
> > Date: Thu, 24 Jun 2021 17:53:02 +0200
> > Sensitivity: Normal
> > Cc: [email protected]
> >
> > Ok,  I added the texinfo development directory to PATH.
> >
> > Now getting again to the old problem of texinfo.tex
>
> Why did you need to add some directory to PATH?  Did you install
> Texinfo with "make install", as expected?  Assuming you used some sane
> vale of the --prefix configure option, "make install" should have made
> sure every executable is on PATH from the get-go.  Since you say you
> need to add some directory to PATH, I suspect that instead of a normal
> install you did something "by hand", and now the thing crumbles under
> you feet because of that.
>
> Texinfo is not guaranteed to work correctly unless you install it
> after building using the provided "make install" procedure (followed
> by a manual install of texinfo.tex, if needed).  If you didn't do
> that, things will fall apart, and please don't expect this list to
> support you in that adventure.
>