From: Peter Wang <novalazy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc calls connect on Windows?
Date: Fri, 12 Nov 2010 00:22:00 +1100 [thread overview]
Message-ID: <20101111132159.GF1400@plug.localdomain> (raw)
In-Reply-To: <20101110163328.GA30715-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
No options are required.
However, I have discovered that the problem does not occur with
pandoc 1.4 and earlier versions.
On 2010-11-10, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I have no idea what could be causing this... I'm completely
> ignorant of Windows programming. It might help to know what
> options pandoc was called with, though.
>
> +++ Peter Wang [Nov 10 10 08:48 ]:
> > Hi,
> >
> > I'm using pandoc as part of a build system to generate API
> > documentation. When pandoc is called within an MS Visual Studio build,
> > it produces this error message:
> >
> > pandoc.exe: connect: failed (Cannot assign requested address (WSAEADDRNOTAVAIL))
> >
> > Is it too far fetched that pandoc (or one of the libraries it depends on)
> > calls connect, and Visual Studio runs build commands in a restricted
> > environment?
> >
> > Peter
> >
next prev parent reply other threads:[~2010-11-11 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 21:48 Peter Wang
[not found] ` <20101109214800.GB1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
2010-11-10 16:33 ` John MacFarlane
[not found] ` <20101110163328.GA30715-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-11 13:22 ` Peter Wang [this message]
[not found] ` <20101111132159.GF1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
2010-11-12 8:45 ` John MacFarlane
2010-11-12 9:57 ` Tillmann Rendel
[not found] ` <4CDD0F90.5030004-jNDFPZUTrfTbB13WlS47k8u21/r88PR+s0AfqQuZ5sE@public.gmane.org>
2010-11-12 22:13 ` Peter Wang
[not found] ` <20101112221339.GI1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
2010-11-13 2:30 ` John MacFarlane
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=20101111132159.GF1400@plug.localdomain \
--to=novalazy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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 NNTP newsgroup(s).