From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Instability with signals and threads
Date: Fri, 28 Nov 2014 21:13:00 -0000 [thread overview]
Message-ID: <5478E4FA.3000905@cygwin.com> (raw)
In-Reply-To: <20141121203628.GA17637@calimero.vinschen.de>
On 2014-11-21 14:36, Corinna Vinschen wrote:
> On Nov 21 14:06, Yaakov Selkowitz wrote:
>> On 2014-11-21 10:06, Corinna Vinschen wrote:
>>> 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?!?
>>>>
>>>> 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.
>>
>> https://cygwin.com/ml/cygwin-developers/2013-07/msg00008.html
>>
>> Which resulted in:
>>
>> https://sourceware.org/viewvc/src/winsup/doc/Makefile.in?r1=1.33&r2=1.34
>>
>> Has this bug been fixed yet in TeX Live? I had no problems building the
>> PDFs after reverting this commit. I'll have to try on Fedora 20 and 21,
>> unless someone else can get to it first.
>
> Again, if you have another way to create pdf files from xml input, which
> works on Cygwin and Linux, please feel free to provide one. I had no
> problems creating pdfs on Linux using fop, so I had no incentive to
> switch. Just provide a patch to cygwin-patches. If it works it's as
> good as applied.
For the archives:
https://cygwin.com/ml/cygwin-patches/2014-q4/msg00016.html
--
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
next prev parent reply other threads:[~2014-11-28 21:11 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
2014-11-21 20:36 ` Yaakov Selkowitz
2014-11-21 20:44 ` Corinna Vinschen
2014-11-28 21:13 ` Yaakov Selkowitz [this message]
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=5478E4FA.3000905@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).