Kilian Krause wrote: > Hi Thomas, > > >>>well, put an strace then. "strace -eopen -f -o command_not_found.log >>>make" should do the trick. try to see which command it's trying to run >>>with :.. >> >>done. no -1 in any fopen. > > > hrmpf. Sounds like a bashism then.
no sign found so far. bash versions and makefiles are identical on both machines. maybe something in bashs config? > > >>>Actually this could be a bashism for echo. You aren't by chance running >>>this on a dash or something? >>> >> >>pardon? pls no old unix slang english, im too young to understand that ;) >>kde terminal. > > > well, "dash" as in /bin/dash is a very plain shell used as a plain POSIX > shell replacement to /bin/sh. It might be that the Makefile contains > code where : is mapped to the "echo" binary (similar to printf) which > may not work in "dash". Better now? yes, thx. > > >>BTW it compiles on the laptop. thx anyway :) > > > Congrats! thx for your help. > > >>??? just got a new error after make update: >> >>make[5]: *** No rule to make target `toolbox-common.c', needed by >>`toolbox-common.lo'. Stop. > > > yep. that one is "normal" right now. CVS HEAD is broken. > just crosscompiled clean again on the laptop :) now where to enable localisation? libintl does this, not? inspecting... _______________________________________________ Gnomemeeting-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
