public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michael A. Chase" <mchase@ix.netcom.com>
To: "Armin Theissen" <Armin.Theissen@Sun.COM>, <cygwin@sources.redhat.com>
Subject: Re: does patch.exe work different than other unx patch tools?
Date: Wed, 18 Jul 2001 06:39:00 -0000	[thread overview]
Message-ID: <005701c10f8e$b3415320$6464648a@ca.boeing.com> (raw)
In-Reply-To: <200107180941.KAA16581@ireserver.Ireland.Sun.COM>

----- Original Message -----
From: "Armin Theissen" <Armin.Theissen@Sun.COM>
To: <mchase@ix.netcom.com>
Sent: Wednesday, July 18, 2001 02:41
Subject: Re: does patch.exe work different than other unx patch tools?


> thanks for all your help on that issue. We got the patch working
> now.
>
> First, Corrina's suggestion of forgetting the 'type' works, but
> the patch is part of a makefile which should work for unix platforms
> as well (openoffice.org) and the type command is needed there for
> reasons I don't know right now ( = I don't build the unix stuff).
> Then, it makes no difference whether I use the newest latest cygwin
> or the old one (which we need to compile openoffice.org properly
> from the 4nt shell using cygwin tools).
> Last but not least, the line-ends. The solution to make the patch
> working is
>
> type patch-file-name | tr -d "\015"| patch -b -p2

In UNIX, 'type' may be used to search for a command in the directories
listed in $PATH.  In MSDOS, 'type' copies its input file to STDOUT which is
more like UNIX 'cat'.  That leads me to believe you are already in a MSDOS
(or 4nt) specific section of your makefile.

What problems prevent you from compiling openoffice.org using the latest
Cygwin?  If you have problems in the future with the old version, you are
going to have a hard time finding anyone to help.

> > You appear to be using a rather old version of the Cygwin environment
> > (C:\cygnus\CYGWIN~1\H-I586~1\bin\).  A newer version of Cygwin with the
> > patch.exe built for it might work better.

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



--
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/

       reply	other threads:[~2001-07-18  6:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200107180941.KAA16581@ireserver.Ireland.Sun.COM>
2001-07-18  6:39 ` Michael A. Chase [this message]
2001-07-18 12:14 Heribert Dahms
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18  2:42 Armin Theissen
2001-07-17  5:49 Armin Theissen
2001-07-17  6:26 ` Corinna Vinschen
2001-07-17  9:23 ` Oliver Nittka
2001-07-17  9:46   ` Corinna Vinschen
2001-07-17  9:44 ` Michael A. Chase
2001-07-17  9:57   ` Corinna Vinschen
2001-07-17  2:40 Armin Theissen
2001-07-17  4:49 ` Corinna Vinschen

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='005701c10f8e$b3415320$6464648a@ca.boeing.com' \
    --to=mchase@ix.netcom.com \
    --cc=Armin.Theissen@Sun.COM \
    --cc=cygwin@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).