public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Compiling Heimdal
Date: Thu, 10 Apr 2014 15:40:00 -0000	[thread overview]
Message-ID: <87d2gpb3cb.fsf@Rainer.invalid> (raw)
In-Reply-To: <5346A429.8060506@cornell.edu> (Ken Brown's message of "Thu, 10	Apr 2014 10:01:13 -0400")

Ken Brown writes:
> Actually I think what you're looking for is "DEPEND"
> (/usr/share/doc/cygport/manual.html#robo821).

I've stopped using this one since it doesn't tell you which of the
potentially many dependencies failed and it just stops the compilation
cold.  The individual check_* functions aren't any more complicated to
use and you can be a bit more lenient with certain errors if you want.
That said, if its simply a single dependency or two it msy not matter
much.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

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

      parent reply	other threads:[~2014-04-10 15:40 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
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 [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=87d2gpb3cb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).