Got the above error. But I have Perl-5.38.2 and GD 2.80 with State Reomote Installer. My project is karliseppl/Perl-5.38.2-Windows-5. Can anyone help me?
If you are trying to do all of this from the remote command line, it is helpful to check in with the UI to get full info on what happened. Your history tab shows that your current project commit doesn’t have GD in it. It was pinned to 2.80 in a previous commit, which failed to build, and was then removed by the next commit. The last build which had GD in it was with GD set to Auto a few days ago, and at that time it picked a newer version than 2.80 as the best fit.
Hello,
I have reinstalled GD. Error messages are attached. It looks like Perl can’t handle WIN 10 (latest version).
Regards Karliseppl
(Attachment __Fehler_1.txt is missing)
(Attachment __Fehler_3.txt is missing)
We will try to reproduce this issue.
I was unable to reproduce this failure →
I ran
state checkout karliseppl/Perl-5.38.2-Windows-5 .
state use
And to test I ran:
perl -e 'use GD;'
I ran procmon in the background to see that libgd was loading, and it did. So I can offer you this as troubleshooting:
- As a simple test try adding the
binandusr/binfolders to your PATH. This will ensure that GD.dll can locate the needed dlls. This might look something like this:
SET PATH=%PATH%;C:\Users\build\AppData\Local\ActiveState\cache\dfa88d81\bin;C:\Users\build\AppData\Local\ActiveState\cache\dfa88d81\usr\bin;
-
I recommend running procmon while trying to load GD, to see what’s going wrong. You would want to filter for process-ids begining with
perl. -
Check if any system libraries are missing - I ran an ldd to see what GD needed, this is the complete list of libraries that we ship, and the libraries that were selected on my system. It is possible you are missing a system library that is needed in the dynamic chain.
C:\Users\build\AppData\Local\ActiveState\cache\dfa88d81\site\lib\auto\GD>ldd GD.dll
Shipped Libraries:
libgcc_s_seh-1.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/bin/libgcc_s_seh-1.dll
libstdc++-6.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/bin/libstdc++-6.dll
libwinpthread-1.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/bin/libwinpthread-1.dll
perl538.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/bin/perl538.dll
iconv.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/iconv.dll
libbz2-1.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/libbz2-1.dll
libfreetype-6.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/libfreetype-6.dll
libgd.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/libgd.dll
libjpeg-62.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/libjpeg-62.dll
libpng16.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/libpng16.dll
zlib1.dll /c/Users/build/AppData/Local/ActiveState/cache/dfa88d81/usr/bin/zlib1.dll
System Libraries:
ntdll.dll /c/Windows/SYSTEM32/ntdll.dll
ADVAPI32.dll /c/Windows/System32/ADVAPI32.dll
GDI32.dll /c/Windows/System32/GDI32.dll
IMM32.DLL /c/Windows/System32/IMM32.DLL
KERNEL32.DLL /c/Windows/System32/KERNEL32.DLL
KERNELBASE.dll /c/Windows/System32/KERNELBASE.dll
RPCRT4.dll /c/Windows/System32/RPCRT4.dll
USER32.dll /c/Windows/System32/USER32.dll
WS2_32.dll /c/Windows/System32/WS2_32.dll
gdi32full.dll /c/Windows/System32/gdi32full.dll
msvcp_win.dll /c/Windows/System32/msvcp_win.dll
msvcrt.dll /c/Windows/System32/msvcrt.dll
sechost.dll /c/Windows/System32/sechost.dll
ucrtbase.dll /c/Windows/System32/ucrtbase.dll
win32u.dll /c/Windows/System32/win32u.dll
COMCTL32.dll /c/Windows/WinSxS/amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.17763.2061_none_6d037e3459fc48d8/COMCTL32.dll
Hope that helps,
Best,
Marc
Tanks for your mail,
I’ve checked the files and the last one "/c/Windows/WinSxS/amd64_microsoft.windows.common-controls_...." is missing.There are many "COMCTL32.dll" files in the "``/c/Windows/WinSxS" directory but not the one I was looking for. Where can I get it?
greetings Karliseppl
Here is the prozess-monitor-file.
(Attachment Logfile.PML is missing)
The file did not attach.
What you are looking for in the process monitor log - are a series of failures to load → not followed by a SUCCESS. (You can have many failure lines for a DLL, this is your system searching for the correct path, as long as the dll has a SUCCESS it should be okay.) If you see libgd.dll loaded in the log, then the problem is likely a failure to load a dependency.
Here is the processmonitor-log as textfile. Please rename .txt in .pml
(Attachment Logfile.txt is missing)
Can you find references to libgd in the log?
This last part shows the system finding the perl538 dll, I don’t see anything in the last bit that is of concern.
There is no libgd to be found in the log! I can send the whole log with
extension .jpg instead of .pml.
(Attachment Logfile.jpg is missing)
What command did you run during the procmon capture?
Try:
where perl
To reality check what’s going on with your system installation. You may have multiple perl installations on your machine.
And then:
perl -e 'use GD;'
while running procmon to see what’s going on in your system - That will tell you whether GD is working for you. → If GD isn’t showing up at all in the procmon trace for midi_plot you may be accessing a different pathway or environment for the execution.
You could also look at what test is triggering the message "You don't seem to have GD installed." to see what call GD, and run that command directly.
