You are not logged in.
Not sure what to do about the config.txt file though.
I've just commited $XDG_CONFIG_HOME support, so that should fix this problem.
Offline
fails to install using packer. here's the tail of the output:
==> Finished making: musagi 17-1 (Sun Feb 27 18:50:54 GMT 2011)
error: 'packer-*.pkg.tar.*': cannot open package file
rly looking forward to getting this on the go. ... in my 64bit arch.
fave quote of the mo': "Man's reach should exceed his grasp, else what's a heaven for." - Robert Browning
Offline
rly looking forward to getting this on the go. ... in my 64bit arch.
There's no 64 bit support yet... It requires many changes and due to the nature of the source code this isn't easy.
AFAIK you can run 32 bit applications on a 64 bit OS, but I wouldn't know how.
Offline
Hey.
Thought i'd give it a try but was stopped short sadly
right after startup:
musagi: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
Aborted
Offline
musagi: malloc.c:3096: sYSMALLOc: Assertion (...) failed.
Aborted
Hm. I got a similar assert once during development, but the exe built by the makefile works here... You used the PKGBUILD? On a 32 bit Arch?
If the config file has been created, you could enable logging and post the log somewhere (pastebin.org). To enable logging: edit ~/.config/musagi/config.txt and change "log: 0" to "log: 1".
If config.txt hasn't been created, then... at least it means it crashes early :]. Edit: in fact, it doesn't mean that, since config.txt is created at exit... Meh.
Edit: ouch, found my error thanks to Valgrind... The memory allocation for the path to config.txt is 1 byte short. I'll fix that ASAP.
Edit: done. Please grab latest version and try again .
Last edited by stqn (2011-02-28 02:06:35)
Offline
Hey, thanks for the quick fix
Now this is weird though. Using the AUR PKGBUILD I can run it when /opt/musagi is in my path. If I run it with /opt/musagi/musagi it Segfaults somehwere in fread. quite funny really.
Program received signal SIGSEGV, Segmentation fault.
0xb72ee68c in fread () from /lib/libc.so.6
(gdb) bt
#0 0xb72ee68c in fread () from /lib/libc.so.6
#1 0x080686a5 in ?? ()
#2 0x08061f27 in ?? ()
#3 0x08062e80 in ?? ()
#4 0xb72a8db6 in __libc_start_main () from /lib/libc.so.6
#5 0x0804a281 in ?? ()
(gdb)
Well anyhow it works thanks!
Offline
If I run it with /opt/musagi/musagi it Segfaults somehwere in fread.
Luckily, gdb gave me a better backtrace and I think I found were it crashes. The reason is that the program can't find the skin data in the current directory... I'll see what I can do with argv[0] and/or $XDG_DATA_DIRS...
As you discovered by yourself, the temporary solution is to cd /opt/musagi && ./musagi.
Well anyhow it works
thanks!
Glad to read that!
Offline