On Saturday 26 Feb 2005 19:52, Guillaume Laurent wrote:
> It works now. All you need to do is :
>
> - install scons (http://scons.org)
> - from the top level dir, run ./scons_configure [...]
> - run scons

Not working for me:

- snip -

[EMAIL PROTECTED] ./scons_configure

This is bksys 1.1.0


Start 'scons' or 'make' now (and 'scons install' or 'make install' as root to 
install)
Make sure to read the output of ./configure --help if an error occurs
[EMAIL PROTECTED] scons
scons: Reading SConscript files ...
IndentationError: expected an indented block (config.py, line 9)

[EMAIL PROTECTED] cat config.py
#
# script generated by configure
# Sun Feb 27 09:58:50 2005
#

def exists():
        return True
def generate(env):
[EMAIL PROTECTED]

- snip -

As someone who has always despised Python's indentation-as-syntax thing, I am 
of course delighted to see that the reported error is an indentation one.  
(Even though in practice it's presumably caused by a premature EOF.)

One real irritation with scons is that it won't do anything -- not even parse 
its options -- if its config.py is busted.  So in this case I can't even type 
"scons --help" or something to try to work out whether I've done something 
wrong, because it just barfs immediately with the same error about config.py.

btw, the invocation of scons_configure returned so quickly that I suspected it 
probably hadn't done anything even before I subsequently ran scons.  I see 
scons_configure is looking for bk*.py -- I have bksys.py, but nothing else 
that matches.


Chris


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to