From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Instability with signals and threads
Date: Fri, 21 Nov 2014 16:37:00 -0000 [thread overview]
Message-ID: <20141121160608.GF3810@calimero.vinschen.de> (raw)
In-Reply-To: <546F5F37.9010509@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Nov 21 16:50, Marco Atzeri wrote:
> 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...
Oh, right.
> It will be nice to not use it for building cygwin docs.
The html docs are not built with fop, only the pdf. And even then,
make from the parent dir continues to build everything else, even
if make in the doc dir fails:
$(SUBDIRS):
@${MAKE} -C $@ all || ([ "$@" == doc ] && echo "*** error ignored")
If you have another way to create pdf files from xml input, which works
on Cygwin and Linux, please feel free to provide one.
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-11-21 16:06 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
2014-11-21 16:37 ` Corinna Vinschen [this message]
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=20141121160608.GF3810@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).