From: Z. V. <kar...@gm...> - 2008-02-07 21:28:50
Attachments:
build-fix.patch
|
Hello, I have reproduced this error message on my build system, and it's a bug in the makefiles generated by KDevelop - for which I've already took a workaround in CVS half a year ago. The cvs.sh script didn't recognize automake-1.10. Probably Dom had unsermake installed on his system while preparing the release, so the script used unsermake as a fallback option. I'm attaching a quick fix for the script file, which will let you recreate the makefiles, and build KBarcode, hopefully. Here's the commands I used, for example: # cp ~/Desktop/build-fix.patch ~/test/kbarcode-2.0.6 # cd ~/test/kbarcode-2.0.6 # patch -p1 < build-fix.patch # make -f admin/Makefile.common # ./configure # make # sudo make install Hope this helps, Zsolt On 2/7/08, Adrian Klaver <ak...@co...> wrote: > I downloaded 2.0.6 ran configure and then got: > aklaver@ford:~/test/kbarcode-2.0.6$ make > WARNING: use unsermake instead of make or use a wrapper script, e.g. > makeobj!!! > unsermake all > /bin/bash: unsermake: command not found > make: *** [all] Error 127 > What is unsermake and is this a change in requirements? > > -- > Adrian Klaver > ak...@co... > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Kbarcode-users mailing list > Kba...@li... > https://lists.sourceforge.net/lists/listinfo/kbarcode-users > |