Comment 2 for bug 490785

When running a command using sudo the environment is completely different than what it is when running as a regular user. Therefore it is quite understandable that a locally installed SWIG is not found. I guess a possible solution is to add an option for setting the path to the SWIG executable, e.g. withSwig=/path/to/local/swig.