My windows is fresh, so I guess it's a missing perlglob in the PATH. I'll test it tomorrow. Ricardo SIGNES via RT <email@example.com> wrote: >I'm curious as to why this isn't affecting everyone building on Win32. I see a number of reports >from Win32 smokers that do not have problems building Encode. > >Do you suppose it's because they have another perl already built in their %PATH%?