Em sex., 13 de mar. de 2026 às 04:35, Patrice Dumas <[email protected]> escreveu: > > > 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 Thank you for your reply.
I followed your instructions. The log is at <https://pastebin.com/1szpN9Vp>. The Perl 5.42.0 module 'Locale::Po4a::Sgml' was not found on the system. However, at least, I have the man page of that module installed on the system. Is it possible to have the man page installed, but not the module of that man page itself? How can I exactly identify what path is being searched? How can I output what path (of Perl 5.42.0) is in effect in my system right now? I imagine I should confrontate the two pieces of information (the real Perl 5.42.0 modules path and the 'po4a' git version search path) and I should figure out what the difference (if any). Thank you once again. Jamenson Espindula
