bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grep


From: Eli Zaretskii
Subject: Re: grep
Date: Tue, 12 Oct 2004 23:11:23 +0200

> Date: Tue, 12 Oct 2004 12:59:48 -0400 (EDT)
> From: "Alain Magloire" <address@hidden>
> Cc: address@hidden, address@hidden
> 
> >   1. `cd' to the directory containing the package's source code and type
> >      `./configure' to configure the package for your system.  If you're
> >      using `csh' on an old version of System V, you might need to type
> >      `sh ./configure' instead to prevent `csh' from trying to execute
> >      `configure' itself.
> > 
> >      Running `configure' takes awhile.  While running, it prints some
> >      messages telling which features it is checking for.
> > 
> >   2. Type `make' to compile the package.
> > 
> >   3. Optionally, type `make check' to run any self-tests that come with
> >      the package.
> > 
> >   4. Type `make install' to install the programs and any data files and
> >      documentation.
> > 
> >   5. You can remove the program binaries and object files from the
> >      source code directory by typing `make clean'.  To also remove the
> >      files that `configure' created (so you can compile the package for
> >      a different kind of computer), type `make distclean'.  There is
> >      also a `make maintainer-clean' target, but that is intended mainly
> >      for the package's developers.  If you use it, you may have to get
> >      all sorts of other programs in order to regenerate files that came
> >      with the distribution.
> > 
> > do this grep work on Windows 98 if not is there another grep I can use.

It will work if you will install ports of GNU tools, starting from
Bash.

However, I'd suggest to find a precompiled Windows binary and use
that, it will save you lots of trouble.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]