[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 Mike Kaganski changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #11 from Mike Kaganski --- (In reply to V Stuart Foote from comment #10) This does not test for OS platform; rather, it tests both executable names, because on Win64, either one (or both) can be present, and it would not be best to limit ourselves to gswin64c. Could you please test the patch below? https://gerrit.libreoffice.org/80748 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 V Stuart Foote changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #10 from V Stuart Foote --- @Mike, I know we test for 64-bit when building but can we test when running so these one off 32bit/64bit differing command names can be selected? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #9 from V Stuart Foote --- Issue remains, 64-bit build of gs 9.25 installs its executable of gswin64c.exe, while 32-bit is built as gswin32c.exe We call gswin32c.exe, for both 32-bit and 64-bit Windows builds, to handle EPS import in the ieps filter [1], but that is the only place. Making a hardlink for the gswin32c.exe gainst the 64-bit build still works for this corner case. =-ref-= [1] https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#393 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 V Stuart Foote changed: What|Removed |Added CC||noelgran...@gmail.com --- Comment #7 from V Stuart Foote --- Issue remains, and seems we need to test for _WIN64 here and use the '"gswin64c" EXESUFFIX,' for RenderAsBMPThroughHelper [1]. Things were complicated with a MS security change in handling of SYMLINKs [2][3] On 64-bit Windows we now have to make a hard link [4] creating gswin32c.exe link to the 64-bit gswin64c.exe to be able to use Ghostscript to render the EPS to canvas with RenderAsBMPThroughGS [5] =-ref-= [1]https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx?a=true&h=369#390 [2] https://social.technet.microsoft.com/Forums/en-US/0eefc57f-8c01-450a-a1cf-8e2894a951d9/symbolic-link-type-changed [3] https://technet.microsoft.com/library/security/ms15-020 [4] That is: 1. navigate to bin directory of the 64-bit gs install, e.g. C:\Program Files\gs\g9.21\bin 2. hard link with "mklink /h gswin32c.exe gswin64c.exe" before a simple symlink with mklink sufficed, now have to use the hardlink. [5] https://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#370 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #5 from V Stuart Foote --- Still an issue, 32 & 64-bit LO builds looking for the 32-bit command name, e.g. gswin32c for ghostscript, and without a symlink to the 64-bit command the LO function fails. http://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#384 But, I've not come across any other specific instances of naming commands different 32-bit vs 64-bit impacting LO, and work around continues to work. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 Robinson Tryon (qubit) changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||qu...@runcibility.com Ever confirmed|0 |1 --- Comment #3 from Robinson Tryon (qubit) --- (In reply to V Stuart Foote from comment #1) > So setting a Windows symlink with: > > mklink gswin32c.exe "C:\Program Files\gs\gs9.16\bin\gswin64c.exe" > > does provide a work around for this specific issue on Windows. Hmm... a longer-term solution would be ideal. Status -> NEW -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117
--- Comment #2 from MM ---
Would you prefer something like this ?
#ifdef WNT64 // or whatever win 64 bit is called in LO
OUString fileName("gswin64c" EXESUFFIX);
#elseif WNT
OUString fileName("gswin32c" EXESUFFIX);
#else
OUString fileName("gs" EXESUFFIX);
#endif
--
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94117] Windows 64-bit and executable name of 64-bit build of ghostscript -- gswin64c.exe
https://bugs.documentfoundation.org/show_bug.cgi?id=94117 --- Comment #1 from V Stuart Foote --- So setting a Windows symlink with: mklink gswin32c.exe "C:\Program Files\gs\gs9.16\bin\gswin64c.exe" does provide a work around for this specific issue on Windows. So one can use 64-bit builds of Ghostscript, Imagemagick, and pstoedit as needed with 64-bit Windows build of LibreOffice--with PATH tweaks. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
