From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Building from latest git master no longer builds winsup...
Date: Fri, 16 Jul 2021 20:39:44 -0600 [thread overview]
Message-ID: <475242ce-84f2-c17b-c209-36186d4f0fde@SystematicSw.ab.ca> (raw)
In-Reply-To: <70824315-830c-3fbd-1c0a-c5fecd3594d2@cornell.edu>
On 2021-07-16 09:59, Ken Brown via Cygwin wrote:
> On 7/16/2021 11:35 AM, Brian Inglis wrote:
>> On 2021-07-14 12:44, Brian Inglis wrote:
>>> On 2021-07-14 11:48, Ken Brown via Cygwin wrote:
>>>> On 7/14/2021 1:13 PM, Brian Inglis wrote:
>>>>> Building from latest git master does not build winsup... only newlib.
>>>> Did you run winsup/autogen.sh? See
>>>> https://cygwin.com/pipermail/cygwin-developers/2021-June/012161.html
>>
>> Build now works on winsup but quits at doc - log extract attached:
>>
>> $ egrep -A5 'db2|docbook2' build64.log
>>
>> docbook2x-texi --xinclude --info --utf8trans-map=charmap
>> ../../../../winsup/doc/cygwin-api.xml --string-param
>> output-file=cygwin-api
>> could not find ParserDetails.ini in
>> /usr/share/perl5/vendor_perl/5.32/XML/SAX
>> could not open -: No such file or directory
>> /usr/bin/db2x_texixml: program in pipeline exited with an error
>
> This is caused by a bug in texinfo-6.8-1 that was fixed in texinfo-6.8-2.
Thanks Ken,
I was looking for evidence of issues with docbook or SAX, but would not
have suspected texinfo, so I'll bear that in mind in future, and try
wider searches on messages.
My Cygwin32 environment works because it's unusually backlevel there,
and Cygwin64 is not quite up to date, so I'll get them both resynced,
and redo.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-07-17 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 17:13 Brian Inglis
2021-07-14 17:48 ` Ken Brown
2021-07-14 18:44 ` Brian Inglis
2021-07-16 15:35 ` Brian Inglis
2021-07-16 15:59 ` Ken Brown
2021-07-17 2:39 ` Brian Inglis [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=475242ce-84f2-c17b-c209-36186d4f0fde@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).