Hi Mark, > > I feel the original issue is just a broken compiler environment rather than > an Alien issue - though it's just an opinion. >
I will install a fresh Windows XP SP2 VM and report back if the Alien::wxWidgets / ActivePerl / gcc issue arises. > For info: > > Your original issue arose because you have multiple compilers installed. > For the mingw install to work correctly if you have other compliers, it > needs to come first on your path. The ActivePerl mingw PPM is, I would > guess, prepared for users without other compilers installed. > I tried it on my machine which had VC++ Pro (CL.exe) + ActivePerl and on a Windows XP VM which i had an uninstalled copy of strawberry on it but no CL.exe. > There is a second issue that would have been encountered which is caused by > the PPM mingw install not putting mingwm10.dll on the PATH - which is the > right general thing to do - but it ought to be there when you're actually > building in the mingw environment. That's the only reason for needing > C:\aperltest\site\lib\auto\MinGW\bin on the path in the example. > > Anyhow, I'll add a default fallback to Alien to look for > <site_arch>auto\MinGW\bin\mingwm10.dll if it isn't found on the path as a > specific workaround for ActivePerl mingw PPM. > This alone won't have made your own original install work, (mingw not first > on path - other compilers installed) but it would fix it for anyone without > other compilers already installed. > Thanks for the tip, I will check it now. Best regards, Ahmad M. Zawawi
