* pandoc calls connect on Windows?
@ 2010-11-09 21:48 Peter Wang
[not found] ` <20101109214800.GB1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
0 siblings, 1 reply; 7+ messages in thread
From: Peter Wang @ 2010-11-09 21:48 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[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-12 9:57 ` Tillmann Rendel
1 sibling, 1 reply; 7+ messages in thread
From: John MacFarlane @ 2010-11-10 16:33 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
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
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[not found] ` <20101110163328.GA30715-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
@ 2010-11-11 13:22 ` Peter Wang
[not found] ` <20101111132159.GF1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
0 siblings, 1 reply; 7+ messages in thread
From: Peter Wang @ 2010-11-11 13:22 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
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
> >
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[not found] ` <20101111132159.GF1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
@ 2010-11-12 8:45 ` John MacFarlane
0 siblings, 0 replies; 7+ messages in thread
From: John MacFarlane @ 2010-11-12 8:45 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
+++ Peter Wang [Nov 12 10 00:22 ]:
> No options are required.
>
> However, I have discovered that the problem does not occur with
> pandoc 1.4 and earlier versions.
In 1.5, I added a dependency on network libraries, so pandoc
could take a URI as parameter. My guess is that this is the
root of your problem...
John
>
>
> 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
> > >
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[not found] ` <20101109214800.GB1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
2010-11-10 16:33 ` John MacFarlane
@ 2010-11-12 9:57 ` Tillmann Rendel
[not found] ` <4CDD0F90.5030004-jNDFPZUTrfTbB13WlS47k8u21/r88PR+s0AfqQuZ5sE@public.gmane.org>
1 sibling, 1 reply; 7+ messages in thread
From: Tillmann Rendel @ 2010-11-12 9:57 UTC (permalink / raw)
To: Peter Wang; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
Hi,
Peter Wang wrote:
> 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))
Maybe the build system calls pandoc on something which looks like an
URI, and pandoc tries to fetch it, instead of accessing a local file?
Tillmann
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[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>
0 siblings, 1 reply; 7+ messages in thread
From: Peter Wang @ 2010-11-12 22:13 UTC (permalink / raw)
To: Tillmann Rendel; +Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
On 2010-11-12, Tillmann Rendel <rendel-jNDFPZUTrfTbB13WlS47k8u21/r88PR+s0AfqQuZ5sE@public.gmane.org> wrote:
> Hi,
>
> Peter Wang wrote:
> >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))
>
> Maybe the build system calls pandoc on something which looks like an
> URI, and pandoc tries to fetch it, instead of accessing a local
> file?
Indeed. Thanks to you and John; I had forgotten about this new feature
in pandoc.
readSource src = case parseURI src of
Just u -> readURI u
Nothing -> UTF8.readFile src
parseURI parses "c:/bar.txt" as if the drive was a URI scheme, so
readURI is called. Perhaps pandoc should limit itself to "http:" schemes?
In the meantime, I can work around this by using native Windows syntax
(backslashes) when on Windows.
Peter
PS. My testing was a bit hasty before.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pandoc calls connect on Windows?
[not found] ` <20101112221339.GI1400-8h6xrAJxAEd82hYKe6nXyg@public.gmane.org>
@ 2010-11-13 2:30 ` John MacFarlane
0 siblings, 0 replies; 7+ messages in thread
From: John MacFarlane @ 2010-11-13 2:30 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
+++ Peter Wang [Nov 13 10 09:13 ]:
> On 2010-11-12, Tillmann Rendel <rendel-jNDFPZUTrfTbB13WlS47k8u21/r88PR+s0AfqQuZ5sE@public.gmane.org> wrote:
> > Hi,
> >
> > Peter Wang wrote:
> > >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))
> >
> > Maybe the build system calls pandoc on something which looks like an
> > URI, and pandoc tries to fetch it, instead of accessing a local
> > file?
>
> Indeed. Thanks to you and John; I had forgotten about this new feature
> in pandoc.
>
> readSource src = case parseURI src of
> Just u -> readURI u
> Nothing -> UTF8.readFile src
>
> parseURI parses "c:/bar.txt" as if the drive was a URI scheme, so
> readURI is called. Perhaps pandoc should limit itself to "http:" schemes?
Done in
c2636e61d784e88c4a2c8916fdf564266dd7cabd
Thanks for the help debugging this, everyone.
John
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2010-11-13 2:30 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-09 21:48 pandoc calls connect on Windows? 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
[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
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).