public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: ash and String Manipulation
Date: Tue, 7 Jan 2003 12:52:10 +0000	[thread overview]
Message-ID: <20030107125209.GD29126@raq465.uk2net.com> (raw)
In-Reply-To: <20030107121202.GB29420@calcitration.ecs.soton.ac.uk>

On Tue, Jan 07, 2003 at 12:12:02PM +0000, Al Riddoch wrote:

Wow I didn't know you were still following ELKS :)

> > There are several small sed implementations. One obvious candidate is
> > the sed from http://www.tuxedo.org/~esr/software.html

I'm pretty sure I've seen this working on elks too.

Quick check, compiles ok under elksemu

[pauln@host sed]$ file sed
sed: Linux-8086 executable not stripped
[pauln@host sed]$ echo foo bar baz | ./sed 's/foo/bar/'
bar bar baz

Paul

diff -ruN sed-minix/Makefile sed/Makefile
--- sed-minix/Makefile	Mon Jun  1 17:46:50 1998
+++ sed/Makefile	Tue Jan  7 12:45:24 2003
@@ -2,14 +2,16 @@
 
 VERSION=1.3
 
-CFLAGS=-g
-LFLAGS=-lg
+CFLAGS=-0
+CC=bcc
+CPP=gcc -E
+#LFLAGS=-lg
 
 sed: sedcomp.o sedexec.o
-	cc $(LFLAGS) sedcomp.o sedexec.o -o sed
+	bcc $(LFLAGS) sedcomp.o sedexec.o -o sed
 
 mnsed: mnsed.c
-	cc $(LFLAGS) mnsed.c -o mnsed
+	bcc $(LFLAGS) mnsed.c -o mnsed
 
 sedcomp.o: sedcomp.c sed.h
 sedexec.o: sedexec.c sed.h

  reply	other threads:[~2003-01-07 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 21:24 ash and String Manipulation Neil Holmes
2003-01-04  9:50 ` jb1
2003-01-06 11:12   ` Neil Holmes
2003-01-07 11:04     ` jb1
2003-01-07 11:02       ` Neil Holmes
2003-01-07 12:42       ` Alan Cox
2003-01-07 12:12         ` Al Riddoch
2003-01-07 12:52           ` Paul Nasrat [this message]
2003-01-07 13:57             ` Al Riddoch
2003-01-09  9:37             ` sed-1.3 problems [WAS: Re: ash and String Manipulation] jb1

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030107125209.GD29126@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox