From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Instability with signals and threads
Date: Fri, 21 Nov 2014 16:30:00 -0000 [thread overview]
Message-ID: <546F5F37.9010509@gmail.com> (raw)
In-Reply-To: <20141121144333.GA6633@calimero.vinschen.de>
On 11/21/2014 3:43 PM, Corinna Vinschen wrote:
>
>
>> On 32-bit. The rebuild of cygwin1.dll requires large number of packages to
>> create the documentation (including tex and java) and I haven't bloated
>
> Java?!?
make[3]: [cygwin-ug-net/cygwin-ug-net.pdf] Error 127 (ignored)
xsltproc --xinclude ../../../../src_new/winsup/doc/fo.xsl
../../../../src_new/winsup/doc/cygwin-api.xml | fop -q -fo -
cygwin-api/cygwin-api.pdf
/bin/sh: fop: command not found
Making portrait pages on USletter paper (8.5inx11in)
Makefile:64: recipe for target 'cygwin-api/cygwin-api.pdf' failed
FOP is a Java application....grrr...
It will be nice to not use it for building cygwin docs.
Regards
Marco
--
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
next prev parent reply other threads:[~2014-11-21 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 20:24 Mikulas Patocka
2014-11-21 4:24 ` Mikulas Patocka
2014-11-21 10:28 ` Corinna Vinschen
2014-11-21 10:38 ` Corinna Vinschen
2014-11-21 14:43 ` Mikulas Patocka
2014-11-21 14:46 ` Mikulas Patocka
2014-11-21 14:47 ` Corinna Vinschen
2014-11-21 16:30 ` Marco Atzeri [this message]
2014-11-21 16:37 ` Corinna Vinschen
2014-11-21 20:36 ` Yaakov Selkowitz
2014-11-21 20:44 ` Corinna Vinschen
2014-11-28 21:13 ` Yaakov Selkowitz
2014-11-28 22:35 ` Corinna Vinschen
2014-12-04 9:42 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2014-11-19 16:43 Mikulas Patocka
2014-11-19 17:30 ` Mikulas Patocka
2014-11-20 10:00 ` Corinna Vinschen
2014-11-20 16:22 ` 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=546F5F37.9010509@gmail.com \
--to=marco.atzeri@gmail.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).