And, yes, we should probably make sure that it produces something a littler nicer :-)

On Sun, Oct 23, 2011 at 8:31 AM, Daniel Russel <drussel@gmail.com> wrote:
That error tends to mean you are doing an out of source build, but forgot a "repository='something'" line in your config.py (or don't have a config.py at all).


On Fri, Oct 21, 2011 at 3:31 PM, Ben Webb <ben@salilab.org> wrote:
On 10/20/11 10:15 AM, João Rodrigues wrote:
> Thanks for the quick answer. I'm indeed running into some problems
> compiling/building IMP. The 1.0 version fails because of some library
> dependencies I can't solve, but that's not IMP, it's our cluster
> setup.... The SVN version fails because of a KeyError:
>
>     Building tools/imppy.sh
>     scons: *** [tools/imppy.sh] KeyError : 'kernel'
>     Traceback (most recent call last):
>        File
>     "/home/software/software/scons/scons-2.1.0/..//lib/scons-2.1.0/SCons/Action.py",
>     line 1062, in execute
>        File "/home/software/software/IMP/src/scons_tools/imppy.py", line
>     61, in builder_script_file
>          if data.get(env).modules['kernel'].external:
>     KeyError: 'kernel'
>     scons: building terminated because of errors.

That's odd - is this a fresh checkout? Did the kernel module configure
correctly (you should see that further up in the scons output) ? If not,
that would be a concern, since pretty much everything requires the
kernel module, so you won't get far without it.

       Ben
--
ben@salilab.org                      http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
       - Sir Arthur Conan Doyle
_______________________________________________
IMP-users mailing list
IMP-users@salilab.org
https://salilab.org/mailman/listinfo/imp-users