b***@artifex.com
2017-11-11 06:46:41 UTC
http://bugs.ghostscript.com/show_bug.cgi?id=698734
Bug ID: 698734
Summary: Executable name in usage string is hardcoded to
"mupdf" (x11)
Product: MuPDF
Version: master
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P4
Component: mupdf
Assignee: mupdf-***@artifex.com
Reporter: ***@runbox.com
QA Contact: gs-***@ghostscript.com
Word Size: ---
Created attachment 14453
--> http://bugs.ghostscript.com/attachment.cgi?id=14453&action=edit
Patch to fix printed executable in usage string.
As the title says the usage string is hardcoded to "mupdf", so for example,
running `build/release/mupdf-x11` prints "usage: mupdf ..." instead of "usage:
build/release/mupdf-x11 ...".
Only the x11 version has this issue. I've attached a patch.
I also made changes to the Windows version though I haven't been able to test
this as I don't have cross compilation set up.
Bug ID: 698734
Summary: Executable name in usage string is hardcoded to
"mupdf" (x11)
Product: MuPDF
Version: master
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P4
Component: mupdf
Assignee: mupdf-***@artifex.com
Reporter: ***@runbox.com
QA Contact: gs-***@ghostscript.com
Word Size: ---
Created attachment 14453
--> http://bugs.ghostscript.com/attachment.cgi?id=14453&action=edit
Patch to fix printed executable in usage string.
As the title says the usage string is hardcoded to "mupdf", so for example,
running `build/release/mupdf-x11` prints "usage: mupdf ..." instead of "usage:
build/release/mupdf-x11 ...".
Only the x11 version has this issue. I've attached a patch.
I also made changes to the Windows version though I haven't been able to test
this as I don't have cross compilation set up.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are receiving this mail because:
You are the QA Contact for the bug.