You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While building the 6.1.0 Debian package, the debian linting tools point out a possible typo in the binary ("thast" should be "that"). Looking in the compiled binary, I see:
$ strings /usr/bin/nforenum |grep thast
Unknown data does not allow processesing past thast this point.
Looks like two typos, also in processing, so that should be an easy fix.
However, looking for thast in the source does not return any results. It looks like the above string comes from this source line:
$ grep -r processesing .
./src/lang/message_english.h:NFO_MESSAGE(UNKNOWN_ACT0_DATA,"Unknown data does not allow processesing past this point.\n",USE_PREFIX|HAS_OFFSET)
So somehow the "this" in that line is replaced by "thast"? I had a quick look at the macros that generate these messages, but could not find any issue quickly, but I also did not dig deep. I do not have time to dig further right now, but I wanted to record this somewhere.
Maybe someone with a local grfcodec build can check if they see the same weirdness in the compiled binary?
The text was updated successfully, but these errors were encountered:
While building the 6.1.0 Debian package, the debian linting tools point out a possible typo in the binary ("thast" should be "that"). Looking in the compiled binary, I see:
Looks like two typos, also in processing, so that should be an easy fix.
However, looking for
thast
in the source does not return any results. It looks like the above string comes from this source line:So somehow the "this" in that line is replaced by "thast"? I had a quick look at the macros that generate these messages, but could not find any issue quickly, but I also did not dig deep. I do not have time to dig further right now, but I wanted to record this somewhere.
Maybe someone with a local grfcodec build can check if they see the same weirdness in the compiled binary?
The text was updated successfully, but these errors were encountered: