I can't run the programs that I've made because the libraries that are located in places other than /mingw64, are not found.
The rest of the mails are my efforts at diagnosing what is going on. "msysC" was a mount point for C:/msys64 that I thought might have been the issue, fstab being written over. But it didn't matter, including it in fstab again still results in missing library path. I show "echo $PATH" to show that /opt64/bin is in the path, where the libgraphicsmagick libraries are to be drawn from. The ldd shows that the whole list of libraries are not found in the updated system, and another ldd shows what should be seen from an "ldd" command. In fact, the path issue does not happen in the mingw64 window, when PATH is modified: > $ echo $PATH > > /mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl > $ export PATH=/opt64/bin:$PATH > greg@i7Wx MINGW64 /d/bld/gdl/mingw64-git > $ src/gdl > <NORMAL OPERATION> But the problem occurs when I try to use my usual CMD icon which invokes bash, starting in /bin: Icon properties: Target: C:\msys64\usr\bin\bash.exe -login -i Start in: C:\msys64\usr\bin I use bash.exe directly because otherwise I get terminal behavior issues. After this I run a shell program to modify the path so that my program can run. Thanks, Greg On Mon, Jun 1, 2020 at 1:05 PM David Macek <david.mace...@gmail.com> wrote: > Hi. I read your messages 3 times already and I'm still confused > regarding what's wrong. > > 1) What is `/msysC`? Is there a extra mount? > > 2) Putting Ldd output aside, are there any other issues? > > -- > David Macek >
_______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
