I successfully built OpenSSL 0.9.7-beta1 on my m68k-next-openstep42
system. It did require adding an extra include somewhere I can't
remember offhand, and patching one of the test case files, but other
than that it built right out of the box without any issues. Make test
completes without any
Richard Levitte via RT wrote:
Can I assume that sed exists and works properly? dirname can be
coded like this:
echo $$i | sed -e 's|[^/]*$||' -e 's|/$||'
dirname foo returns . which the above doesn't catch.
I can only think of the following short shell script
#! /bin/sh
In message [EMAIL PROTECTED] on Wed, 05 Jun 2002 09:43:45 -0400, Rich
Salz [EMAIL PROTECTED] said:
rsalz Richard Levitte via RT wrote:
rsalz Can I assume that sed exists and works properly? dirname can be
rsalz coded like this:
rsalz
rsalz echo $$i | sed -e 's|[^/]*$||' -e 's|/$||'
On 02-06-05 15:43:45 CEST, Rich Salz wrote:
Richard Levitte via RT wrote:
Can I assume that sed exists and works properly? dirname can be
coded like this:
echo $$i | sed -e 's|[^/]*$||' -e 's|/$||'
dirname foo returns . which the above doesn't catch.
I can only think of the
On 02-06-05 15:43:45 CEST, Rich Salz wrote:
Richard Levitte via RT wrote:
Can I assume that sed exists and works properly? dirname can be
coded like this:
echo $$i | sed -e 's|[^/]*$||' -e 's|/$||'
dirname foo returns . which the above doesn't catch.
I can only think of the
I just commited a change that involves having a new script called
dirname.pl in util/.
Thanks for the report.
[[EMAIL PROTECTED] - Wed Jun 5 09:33:57 2002]:
I successfully built OpenSSL 0.9.7-beta1 on my m68k-next-openstep42
system. It did require adding an extra include somewhere I
rsalz*/* ) echo $I | sed -e 's@\(.*\)/.*@\1@' ;;
Why such a complicated sed? 's@/[^/]*$@@' is perfecty sufficient, and
a little bit more efficient :-).
Because it makes the implementation of basename pretty obvious :)
As for efficiency :) here's an implementation that
