Re: Installing from Git repository failed and problems with documentation formats

2022-04-09 Thread Jose A. Ortega Ruiz


Hi Laurence,

On Tue, Apr 05 2022, Laurence Finston wrote:

> I thought to try `libtoolize' first and that eliminated the Automake errors 
> regarding the Autoconf macros.
> However, the missing file errors remained:
>
> configure.ac:52: error: required file './config.rpath' not found
> configure.ac:159: error: required file 'intl/Makefile.in' not found
> configure.ac:52: error: required file './ABOUT-NLS' not found

I think the piece you're missing is running autopoint for the i18n
stuff... but you don't need to run all this steps separately:
./autogen.sh should do it for you: have you tried simply running that
script?


> There's no explanation of building the package from scratch with the
> build tools Libtool, Autoconf, etc., in INSTALL or elsewhere in the
> top directory.

Sorry about that: running autogen.sh, if present, is (or was, at least)
such a common practice that nobody had asked in 20 years :)

Please let me know if it helps!

Cheers,
jao



Aw: Re: Installing from Git repository failed and problems with documentation formats

2022-04-08 Thread Laurence Finston
> Please let me know if it helps!

Yes it did, thanks.

> Gesendet: Samstag, 09. April 2022 um 02:56 Uhr
> Von: "Jose A. Ortega Ruiz" 
> An: "Laurence Finston" 
> Cc: bug-mdk@gnu.org
> Betreff: Re: Installing from Git repository failed and problems with 
> documentation formats
>
>
> Hi Laurence,
>
> On Tue, Apr 05 2022, Laurence Finston wrote:
>
> > I thought to try `libtoolize' first and that eliminated the Automake errors 
> > regarding the Autoconf macros.
> > However, the missing file errors remained:
> >
> > configure.ac:52: error: required file './config.rpath' not found
> > configure.ac:159: error: required file 'intl/Makefile.in' not found
> > configure.ac:52: error: required file './ABOUT-NLS' not found
>
> I think the piece you're missing is running autopoint for the i18n
> stuff... but you don't need to run all this steps separately:
> ./autogen.sh should do it for you: have you tried simply running that
> script?
>
>
> > There's no explanation of building the package from scratch with the
> > build tools Libtool, Autoconf, etc., in INSTALL or elsewhere in the
> > top directory.
>
> Sorry about that: running autogen.sh, if present, is (or was, at least)
> such a common practice that nobody had asked in 20 years :)
>
> Please let me know if it helps!
>
> Cheers,
> jao
>



Re: Installing from Git repository failed and problems with documentation formats

2022-04-05 Thread Laurence Finston
I thought to try `libtoolize' first and that eliminated the Automake errors 
regarding the Autoconf macros.
However, the missing file errors remained:

configure.ac:52: error: required file './config.rpath' not found
configure.ac:159: error: required file 'intl/Makefile.in' not found
configure.ac:52: error: required file './ABOUT-NLS' not found

There's no explanation of building the package from scratch with the build 
tools Libtool, Autoconf, etc., in INSTALL or
elsewhere in the top directory.

Laurence

> Gesendet: Dienstag, 05. April 2022 um 07:26 Uhr
> Von: "Laurence Finston" 
> An: bug-mdk@gnu.org
> Betreff: Installing from Git repository failed and problems with 
> documentation formats
>
> Hello,
>
> I was able to install mdk 1.3.0 from the tarball.  I was not able to install 
> MDK from the current version in the Git repository.  This is the protocol:
>
> $ git clone git://git.sv.gnu.org/mdk.git
>
> $ cd mdk/
>
> $ aclocal
>
> $ autoconf
>
> $ autoheader
>
> Successful up to here.
>
> $ automake --add-missing --copy
>
> configure.ac:52: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> configure.ac:52: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> configure.ac:52: error: required file './config.rpath' not found
> configure.ac:159: error: required file 'intl/Makefile.in' not found
> configure.ac:52: error: required file './ABOUT-NLS' not found
>
> The only file in [...]/mdk/intl is `.gitignore' (i.e., no `Makefile.am').
>
> I wanted to generate the manual in PDF format.  Using the dist. from the 
> tarball, I got this error:
>
> $ make gendocs
> (cd ../doc && \
>  ./gendocs.sh --email bug-mdk@gnu.org mdk 'GNU MDK Users Manual')
> /bin/bash: line 1: ./gendocs.sh: No such file or directory
> make: *** [Makefile:989: gendocs] Error 127
>
> Using the installation from the Git repository, I was able to generate 
> `gendocs' but then I got this error:
>
> $ gendocs
> ./gendocs: cannot find .texinfo or .texi or .txi for  in 
> /home/laurence/mdk_local/git_repos/mdk/doc.
>
> I just used `texi2dvi mdk.tex' and `dvipdfmx mdk.dvi' to generate the PDF 
> file.  The following aren't bugs, but I then had to print to a file to get it 
> into DIN A4 format and had to look for the page numbers to eliminate the 
> blank page at the end and the COPYING section.  Obviously, the COPYING 
> section is needed but I think it would be a convenience to indicate how to 
> eliminate it for printing purposes.  I don't do this yet for my manuals, but 
> I plan to.
>
> I do think it's important, however, to provide documentation in PDF format 
> from the point of view of accessibility for people who, like me, have 
> problems reading on computer screens.  If you don't want to do that, it would 
> be nice if you would consider at least providing rules for this in 
> `[...]/doc/Makefile.am', because not everybody knows how to use Texinfo.
>
> Thanks.
>
> Laurence Finston