Mail Archives: cygwin/2001/06/27/18:54:10
Sheesh, another typo, the `tar' in step two shoulda been
tar xjvf ../cygwin-src-yyyymmdd.tar.bz2
Though I do sometimes claim that I deliberately introduce
errors so as not make things too easy ;-)
Oh, and the `v' isn't really needed. I just sorta like to see
what is going on... probably for the same reason I distrust
scripts and prefer to enter the commands myself.
So I'm an anachronism, wanna make something of it ;-P
Greg Smith wrote:
>
> Missed a command in step (2), let me try again
>
> This is what I do, especially when I'm behind a firewall and
> can't get out on the cvs port.
>
> (1) I get the latest snapshot via ftp from a cygwin mirror site
> and put it in the \cygwin directory
> (2) I bring up a cygwin window and do:
> cd /
> rm -Rf src
> rm -Rf obj
> mkdir src
> mkdir obj
> cd src
> tar jzvf ../cygwin-src-yyyymmdd.tar.bz2
> (3) cd /obj
> /src/configure --prefix=/tmp/cygwin && make && make install
> and exit the cygwin window
> (4) from a windows command prompt I then do
> copy \cygwin\tmp\cygwin\bin\* \cygwin\bin\*
> (5) Fire up a new cygwin window and run `cygcheck -s' to verify
> the snapshot level and build date (which is near the bottom
> of the display).
>
> If there are patches that I want, then I can usually save them
> from an attachment in a cygwin or cygwin-patches post, usually
> in my \cygwin directory. Usually the patches hit src/winsup/cygwin.
> So, before step (3) I do
> cd /src/winsup/cygwin
> patch < /whatever.patch
>
> Greg
> >
> > --
> > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting: http://cygwin.com/bugs.html
> > Documentation: http://cygwin.com/docs.html
> > FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -