Bug 15576

Summary: e2fsprogs calls not fully capable makeinfo
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Adrian <adrian.freihofer>
Component: coreAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: minor    
Priority: Low CC: meta.mr.watcher, meta.watcher, randy.macleod, ross.burton
Version: unspecified   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Adrian 2024-08-11 20:40:51 UTC
When building e2fsprogs or e2fsprogs-native the following message is found in the log.do_install file:

Traceback (most recent call last):
  File "...poky/build/tmp/work/x86_64-linux/e2fsprogs-native/1.47.0/recipe-sysroot-native/bin/makeinfo", line 98, in <module>
    assert this_binary in simple_binaries, \
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: Don't know how to get default output file name from input file!
This stand-in version of makeinfo is not yet fully capable of emulating
the real version from the GNU texinfo suite. If you see this message, file a
bug report with details on the recipe that failed.


The assertion is thrown by: https://git.yoctoproject.org/poky/tree/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy/template.py#n98
Comment 1 Randy MacLeod 2024-08-15 14:38:36 UTC
This looks like an error but can you confirm that e2fsprogs actually builds properly.  If so, we might add a comment in the log generation to explain that the log can be safely ignored or somehow eliminate the log in this case.
Comment 2 Randy MacLeod 2024-09-26 15:02:16 UTC
There's a bug here but it's a low priority.
Comment 3 Randy MacLeod 2024-09-26 15:05:18 UTC
...
Comment 4 Ross Burton 2024-09-26 15:51:23 UTC
So the problem is that our texinfo stub is very dumb.  e2fsprogs invokes "makeinfo ../../git/doc/libext2fs.texinfo" without telling it where a file will be written: proper makeinfo can parse the file and find the @setfilename command but our stub does not, this is what the error is trying to say.

We could just assume ${basename}.info and hope for the best?