On Wed, Mar 11, 2026 at 06:52:11AM -0300, Jamenson Espindula wrote: > > On the po4a side, you need to get the git source, then add the branch > > corresponding to the pull request I mentionned above, build and maybe > > install. > > > I cloned your repository (as it is an exact copy of the mquinson one). > > I tried the commands below: > > mkdir -v build > cd build/ > perl ../Build.PL > > The output os the last command was:
Doing perl Build.PL needs to be in the source directory. I think that it is the equivalent of ./autogen.sh in Texinfo. then you can run Build from the build directory. However, I do not think that it is useful, for two reasons: * if you run Build from the build directory, nothing is created in the build directory * even if you run ./Build from the main directory, the build is not done in source directories, and does not touch the source except for the po files. So you should better do: perl ./Build.PL ./Build ./Build test Regarding the tests, they are skiped if the Texinfo SWIG interface is not found, so to make sure that they are really run. If the Texinfo module is not found you will see something like ok 1 # skip cannot load Texinfo module 1..1 ok All tests successful. Files=1, Tests=1, ....... If the Texinfo module is found, it will be much more verbose. Even if not verbose, you can see if the tests are skipped by looking at the number of tests: ./Build test --test_files t/fmt-texinfoparser.t t/fmt-texinfoparser.t .. ok All tests successful. Files=1, Tests=17, ..... -- Pat
