Re: Autoconf build targets
Robert Millan wrote:
On Mon, May 20, 2002 at 02:05:47PM -0400, Nathan Hawkins wrote:
Looked like a bourne shell to me. Default root shell is /bin/csh on
FreeBSD, but I believe /bin/sh is basically the same as ash.
Interestingly, MAKEDEV fails to work with bash but works fine with ash.
Weird. Have you tried with the ash from Debian? Could you paste the lines
failing and error from MAKEDEV?
Yes, that's what I'm using for MAKEDEV now. The errors I'm getting with
MAKEDEV look like this. (There are a lot of them.)
skaro:/dev# /sbin/MAKEDEV all
MAKEDEV: line 1292: syntax error near unexpected token `)'
MAKEDEV: line 1292: ` )'
However, there are quite a few other places where /bin/sh is used.
Particularly, BSD make calls /bin/sh by default, and some of the
Makefiles failed until I changed make to use /usr/bsd/bin/sh.
sh is one of the tools it needs to build the source. There are several
skaro:/# ls /usr/bsd/bin
byacc gcov kas kgdb kranlib make patch yacc
colldef gensetdefs kc++filt kld kreadelf mkdep sh
compile_et install kcc knm ksize mknod tcsh
csh kaddr2line kcpp kobjcopy kstrings mktemp tsort
find kar kgasp kobjdump kstrip objformat xargs
And yes, all of these are things for which I can't presently substitute
the regular versions of these from Debian packages. :(
Several of the tools are there because they have incompatible options to
GNU versions. find and install for example. Others are apparently
BSD-specific, like gensetdefs or compile_et.
I think at least we should have a compatible install, csh, tcsh, make
(pmake package) and sh in Debian.
I'm not sure this is the way to go. We'll have to see. pmake package
won't work, it'd have to be FreeBSD's make.
I'd like to use Debian tcsh when I get it to work. For install, make,
find, xargs and some of the others, I think the setup I have now is a
better solution, since they conflict badly with the GNU ones.
Remember, these are used almost exclusively to build the kernel and
libc. Reliability is more important here than beauty.
But of course you've convinced me that /usr/bsd is necessary for some
Some such thing, anyway. It was an obvious name, and nearly the first
thing that occurred to me. As I said, I'll see about getting it an FHS
compliant path at some point.
But as for actually having it in the first place, I have no doubts that
it's the best solution right now. I've tried some others, and this works
best so far.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com