Re: Discrepancy in regards to program_name output

Sören Tempel wrote: > > tl;dr If argv[0] is a full path (e.g. because of qemu-user usage), > > many tests will fail because --help uses argv[0] while error messages > > use basename(argv[0]). Yes, that's the cause. Good analysis. > > Not sure how to resolve this, if getprogname is expected to ret

Re: m4 on native Windows

> > I'm still trying to figure out how the names differ. Can you confirm > > what is output by: > > src/m4 --help | head -n1 > > It is: > Usage: C:\cygwin64\home\bruno\m4-2021-05-13\build-mingw64\src\m4.exe > [OPTION]... [FILE]... In fact, it depends on the program that invokes src/m4. The an

Re: Discrepancy in regards to program_name output

On Wed, Jun 09, 2021 at 06:46:45PM +0200, Sören Tempel wrote: > Hello, > > I was debugging m4 test failures in an Alpine Linux Edge RISC-V RV64 > chroot emulated using qemu-user. The test failures looked as follows: > > checks$ ./check-them -I ../examples/ 021.macro_argu > -/usr/bin/m

Discrepancy in regards to program_name output

Hello, I was debugging m4 test failures in an Alpine Linux Edge RISC-V RV64 chroot emulated using qemu-user. The test failures looked as follows: checks$ ./check-them -I ../examples/ 021.macro_argu -/usr/bin/m4:stdin:1: Warning: too few arguments to builtin `index' -/usr/b