GNU sed and other non standard packages.

• Previous message: Arnold Korns: "XWindows on OpenBSD 3.4"
• Next in thread: Janne Johansson: "Re: GNU sed and other non standard packages."
• Reply: Janne Johansson: "Re: GNU sed and other non standard packages."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Wed, 24 Mar 2004 13:39:54 +1000

Hi all.

I just started out on OpenBSD 3.4 (which I found on a Magazine cover
recently) and am still feeling my way around.

While trying to build GNU Common Lisp (GCL) I found that the BSD sed doesn't
handle the expressions fed to it by the GCL makefile which is very much GNU
oriented. Looking around I find there is no instance of GNU sed in the
precompiled packages for OpenBSD.

Is it hidden inside one of the packages or should I be building it myself?

If I build it myself, should I call it gsed?

What is the usual OpenBSD way of dealing with non-native utilities which
might normally have the same name as the ones supplied? (I notice that GNU
make is called "gmake", for example.)

Looking further ahead, should I be aiming to use just the standard tools
available in the simplest possible OpenBSD 3.4 install with no downloads at
all from the packages/ports area?

In particular, I'm thinking of upgrading the compiler to gcc 3.2 in the hope
of obtaining "isnormal()" and friends and/or a more recent version of
"ieeefp.h" with, especially, the macro FP_NZERO which seems to be missing.
It concerns me that it might not be the best thing to do to have in the
Readme for OpenBSD GCL - "download this, download that" rather than building
out of the box with a basic system.

As it stands ptoential builders would have to get GNU make and the
autotools.

Thanks for any comments,

Mike Thomas.

• Previous message: Arnold Korns: "XWindows on OpenBSD 3.4"
• Next in thread: Janne Johansson: "Re: GNU sed and other non standard packages."
• Reply: Janne Johansson: "Re: GNU sed and other non standard packages."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]