public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: js185 package problem (was Re: Seg Fault in strftime)
Date: Tue, 25 Aug 2015 18:27:00 -0000	[thread overview]
Message-ID: <1440527238.6808.5.camel@cygwin.com> (raw)
In-Reply-To: <CAOC2fq_CO2F=2zBSTCBN7cYpEpnm75+kMZVe88h3xM9hp=zjxQ@mail.gmail.com>

On Tue, 2015-08-25 at 10:17 -0700, Michael Enright wrote:
> On Mon, Aug 24, 2015 at 10:39 AM, Yaakov Selkowitz  wrote:
> > On Mon, 2015-08-17 at 10:10 +0200, Corinna Vinschen wrote:
> >> Maybe the package just needs rebuilding.  Yaakov?
> >
> > I have uploaded js185-1.0.0-4.  Please let me know if that helps.
> 
> Good news.
> The upload propagated to my favorite mirror, I tried out my
> application and it worked.

Glad to hear that.

> At one point I checked the box for the source to this library, and
> looked at the tarball. I saw that there were patches (minor if I
> recall correctly) and I wondered if I'd be able to reproduce the build
> accurately from the tarball and those patches. Is there a generic
> reference for how packages are built to ship in Cygwin, or is this an
> ad hoc thing with different steps for different packages?

Most packages now use cygport.  Install all the build requirements,
then:

cygport js185.cygport all

--
Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2015-08-25 18:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  0:16 Seg Fault in strftime Michael Enright
2015-07-31 12:51 ` Jon TURNEY
2015-07-31 19:50   ` Michael Enright
2015-07-31 23:43     ` Michael Enright
2015-08-01  0:47   ` Michael Enright
2015-08-01 21:47 ` Brian Inglis
2015-08-02  1:47   ` Michael Enright
2015-08-03  3:37     ` Brian Inglis
2015-08-03  8:36     ` Corinna Vinschen
2015-08-03 10:54       ` Michael Enright
2015-08-03 13:42         ` Corinna Vinschen
2015-08-03 15:52           ` Michael Enright
2015-08-04  5:33             ` Michael Enright
2015-08-05  8:02               ` Corinna Vinschen
2015-08-17  3:00                 ` Michael Enright
2015-08-17  8:11                   ` js185 package problem (was Re: Seg Fault in strftime) Corinna Vinschen
2015-08-24 17:39                     ` Yaakov Selkowitz
2015-08-25 17:17                       ` Michael Enright
2015-08-25 18:27                         ` Yaakov Selkowitz [this message]

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=1440527238.6808.5.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin@cygwin.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).