From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Compiling Heimdal
Date: Thu, 10 Apr 2014 12:18:00 -0000 [thread overview]
Message-ID: <20140410121844.GA14330@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20140410T131622-281@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Apr 10 11:18, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > I'm wondering, though, couldn't the cygport script contain something
> > like this to give warning that the so-and-so devel packages are required
> > before building? Does cygport support this already, perhaps, and I just
> > missed it?
>
> Yes it can check for prerequisites and either warn or throw an error, but
> you have to put that test into the cygport file by hand.
Rpm spec files also have to contain the build reqs explicitely, so
that's fine then, IMHO. Maybe we should just urge ourselves to utilze
this more often :}
Skimming the cygport manual, I just can't find the keyword to specify
the build reqs.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-10 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:59 Henry S. Thompson
2014-04-09 17:26 ` Yaakov (Cygwin/X)
2014-04-09 17:47 ` Henry S. Thompson
2014-04-09 17:56 ` Achim Gratz
2014-04-09 18:39 ` Yaakov (Cygwin/X)
2014-04-10 7:42 ` Csaba Raduly
2014-04-10 8:04 ` Corinna Vinschen
2014-04-10 11:19 ` Achim Gratz
2014-04-10 12:18 ` Corinna Vinschen [this message]
2014-04-10 13:15 ` Achim Gratz
2014-04-10 13:51 ` Corinna Vinschen
2014-04-10 14:01 ` Ken Brown
2014-04-10 14:54 ` Corinna Vinschen
2014-04-10 15:40 ` Achim Gratz
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=20140410121844.GA14330@calimero.vinschen.de \
--to=corinna-cygwin@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).