On 1/18/2016 8:08 PM, Kenneth Wolcott wrote:
On Mon, Jan 18, 2016 at 2:45 PM, Ken Brown wrote:
On 1/18/2016 4:06 PM, Kenneth Wolcott wrote:
Hi;
Taking a very long time to run
/etc/postinstall/texlive-dollection-context.sh
How long should it take? I've had to terminate it prior to completio
On 01/18/2016 02:50 PM, Warren Young wrote:
On Jan 18, 2016, at 8:27 AM, David Sicilia wrote:
3) The native windows program successfully completes and exits with
code 0 internally
4) But -- the error code returned to the bash script is 127 --
despite no indication of an error anywhere
On Mon, Jan 18, 2016 at 2:45 PM, Ken Brown wrote:
> On 1/18/2016 4:06 PM, Kenneth Wolcott wrote:
>>
>> Hi;
>>
>> Taking a very long time to run
>> /etc/postinstall/texlive-dollection-context.sh
>>
>> How long should it take? I've had to terminate it prior to completion
>> a couple of times becaus
On 1/18/2016 4:06 PM, Kenneth Wolcott wrote:
Hi;
Taking a very long time to run /etc/postinstall/texlive-dollection-context.sh
How long should it take? I've had to terminate it prior to completion
a couple of times because I had to logout of the machine (Windows 2008
Standard server). The lon
Hi;
Taking a very long time to run /etc/postinstall/texlive-dollection-context.sh
How long should it take? I've had to terminate it prior to completion
a couple of times because I had to logout of the machine (Windows 2008
Standard server). The longest I had it run was about 18 hours.
Somet
On Jan 18, 2016, at 8:27 AM, David Sicilia wrote:
>
> 3) The native windows program successfully completes and exits with
> code 0 internally
> 4) But -- the error code returned to the bash script is 127 --
> despite no indication of an error anywhere
We’ll want a simple test case showing th
On Jan 18 18:10, Henri wrote:
> Corinna Vinschen cygwin.com> writes:
>
> > There's no firewall involved if a simple socket call goes wrong.
> > For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbound
> > until you call bind or connect.
>
> s/AF_INET/AF_UNIX/ ? (sorry for my intrusi
Corinna Vinschen cygwin.com> writes:
> There's no firewall involved if a simple socket call goes wrong.
> For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbound
> until you call bind or connect.
s/AF_INET/AF_UNIX/ ? (sorry for my intrusion)
Regards,
Henri
--
Problem reports:
I did some debugging regarding the issue I had and next following some results.
TL;DR: Giving executable permissions to the library, fixed the issue.
So when I execute the binary file ./MQTTAsync_publish.exe, it
terminates with exit code 127
$ ./MQTTAsync_publish.exe
$ echo $?
127
I tried to us
On Jan 16 18:16, Glen L wrote:
>
> Greetings all,
>
> I'm moving a "C" program to 64-bit Windows 10 that worked previously
> in 32-bit Win7. It builds, compiles and runs (AFAIK) with the
> exception of being able to open a socket. Calling the socket thusly:
>
> if ((g->listen = socket(PF_LOC
Hi there,
I have a strange problem for which I could not find any help online or
in the Cygwin FAQs (have been searching for about a month now). I
have Cygwin64 on Windows 7 (downloaded maybe about 8 months ago).
I have a bash script that, in addition to running Cygwin programs,
runs a few nativ
11 matches
Mail list logo
