On Thu, Oct 20, 2011 at 10:38 AM, Rowan Sylvester-Bradley <[email protected]> wrote: > 3. Got a long list of log info containing many error messages > and warnings, the most interesting of which was probably > several Access Denied messages. I tried capturing the log into > a file at *snip* > Strangely it does _not_ include the Access Denied messages. You > can see as much of the text as was saved in the command window > at http://www.sylvester-bradley.org/rowan/docs/cmdwindow.txt > (sorry about the line wrapping - blame Windows, not me).
I suspect that you aren't redirecting STDERR. You can do something like this (in UNIX shells and Windows' cmd.exe) to capture both STDOUT (1) and STDERR (2) into one file: foobar 1>output.txt 2>&1 The order matters. If you do 2>&1 first then you'll be redirecting STDERR to the original STDOUT, which is your console window or terminal emulator. Instead, you want to first redirect STDOUT into a file (e.g., output.txt) and then redirect STDERR to STDOUT (which is now output.txt). I can't be too much more help than that unfortunately. I notice that there are "'nmake' not found" errors, which suggests that your environment isn't set up to be building modules. I'm not really familiar with nmake though. I prefer the UNIX world myself. I suppose you could begin by searching your file system for nmake.exe. If you find it (I do in Visual Studio), try adding the path to your PATH environment variable before running cpan: dir /b /s \nmake.exe set PATH=%PATH%;C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin (Assume the previous two lines are a single line separated by a space.) I suspect that won't really be enough though. Perhaps you should be doing it instead from either a Visual Studio or MSYS shell (one with the environment set up to find everything). I think that Strawberry Perl is supposed to come with all of the necessary build tools bundled so perhaps that would be easier to use. I rarely manage to get things working in Windows for long. Even if I do get them working they eventually stop working and it's just too much of a headache to be worthwhile. ^^ If you run the command prompt application as an administrator then you should have rights to write pretty much anywhere that you'd want to. That said, you might be able to use local::lib instead so you don't need to run as an administrator. Regards, -- Brandon McCaig <[email protected]> <[email protected]> Castopulence Software <https://www.castopulence.org/> Blog <http://www.bamccaig.com/> perl -E '$_=q{V zrna gur orfg jvgu jung V fnl. }. q{Vg qbrfa'\''g nyjnlf fbhaq gung jnl.}; tr/A-Ma-mN-Zn-z/N-Zn-zA-Ma-m/;say' -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] http://learn.perl.org/
