From: Dave S. <da...@sm...> - 2005-07-10 17:31:05
|
Dick Davies wrote: > * Jeremy Grosser <je...@ru...> [0726 17:26]: > >>That was the problem alright... I was using the OpenBSD make utility. Gotta love how they manage to >>break compatibility half the time. Thanks for the help. > > > As a nitpick, that's BSD make, which is a lot older than GNU make. > A *lot* of open source stuff only works with gmake. > > The gumstix build system expects you to be on linux. > > I tried the other day on freebsd and was pulling my hair out after > half an hour - wierd flags to cp, and other quirks which I suspect are > down to /bin/sh being /bin/bash in 'compatiblity mode' rather than a real > Bourne shell on linux, etc. > Also the make system has a feature that somehow wallops any handmade > tweaks you make next time you configure the buildroot. > > NB: I'm not slagging off gumstix here, it's just a fact of life and has > hit me with many other projects (mostly recently Xen). > > I got bored and switched my laptop to ubuntu. > Be prepared for more hassles if you stick on a BSD. > I had a lot of issues getting it to build on OSX (which is *BSD under the hood). A lot of the build system assumes GNU tools with extensions over the UNIX, so you will find extra parameters on simple things like cp or tar trip you up. Scripts can fall over as although they say #! /bin/sh , bash in sh compat mode will let you get away with bashisms that sh will (quite rightly) throw out. The galling thing is, that the majority of the GNUisms are unecessary as the original commands do the correct thing, just with less verbose command line options. <rant>If *nix command line is all about brevity i.e. cp instead of copy, why have command line parameters like --deep-dereference!</rant> My branch (scudderfish) may be more likely to work for you, but it's a bit out of date (at about r480ish level). I must merge in the more recent changes.... Regards, Dave |