When compiling SQLite using cygport 0.20.1-1, I'm getting the
following messages when doing "cygport xxx.cygport package":
:1:in `require': cannot load such file --
rubygems.rb (LoadError)
from :1:in `'
:1:in `require': cannot load such file --
rubygems.rb (LoadError)
from :1:in `'
On Jun 17 06:40, JonY wrote:
> On 6/16/2015 17:34, Corinna Vinschen wrote:
> > On Jun 16 06:24, JonY wrote:
> >> On 6/16/2015 00:41, Corinna Vinschen wrote:
> >>> Hi Jon,
> >>>
> >>> any idea what happened to tchar.h in the latest w32api update?
> >>>
> >>
> >> tchar.h seems to be part of the CRT h
Unfortunately, using the 64-bit wscript.exe didn't change anything - same
behavior as before with excel hanging.
We are using 64-bit cygwin and 32-bit Excel (Excel 2007).
Denis
On Tue, Jun 16, 2015 at 9:27 AM, Kertz, Denis (D)** CTR **
wrote:
> We need to run some Excel programs via cron and a
On Jun 17 13:29, Kertz, Denis (D)** CTR ** wrote:
> Unfortunately, using the 64-bit wscript.exe didn't change anything - same
> behavior as before with excel hanging.
>
> We are using 64-bit cygwin and 32-bit Excel (Excel 2007).
The problem is probably related to some of the changes between XP a
I'm having numerous problems recently running gdb inside emacs (both
-w32 and -X11):
1) The stack trace window requires one or two gdb commands to catch up
with the current stack frame. E.g., I'll hit a breakpoint after "run"
and then type "up"; the frame pointer still points at frame 0. I'll
ty
(Trying to remove TOFU to make the conversation appear chronological again and
with correct attributions.)
Kertz, Denis (D)** CTR ** wrote:
> > > We need to run some Excel programs via cron and are using vbscript to do
> > > this. We have this running on a WinXP machine but are having trouble
Yes, I was confused, by the system32, but I still managed to do what was
suggested. Previously I was running:
c:/Windows/System32/wscript.exe 'c:\cygwin64\home\Upar3\tst.vbs'
Then as suggested I ran:
c:/Windows/SysWow64/wscript.exe 'c:\cygwin64\home\Upar3\tst.vbs'
Both version
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
> Kiehl, Horst
> Sent: Wednesday, June 17, 2015 8:10 AM
> To: Kertz, Denis (D)** CTR **; cygwin@cygwin.com
> Subject: RE: Unable to run excel via cron
>
> (Trying to remove TOFU to make the
We are running cron under the specific cygwin login (not cyg_server).
Presumably there is a solution to this problem. We have 3 Win7 Pro PCs and
this works on one of the PCs (unfortunately, not the one where we need it to
work) and fails on the other two PCs.
Thanks for the two suggested links
Hello.
==Preamble==
Some time ago I noticed that cygwin executables (e.g. bash, tar, echo
& so on) handle specially *, {} and some other symbols in
command-line, even when being invoked not from shell (e.g.
programmatic invocation or cmd.exe). After some googling, I found
CYGWIN=noglob setting, wh
Hello.
[Sorry if duplicate, previous message was sent from wrong address, so
not sure if it reached.]
==Preamble==
Some time ago I noticed that cygwin executables (e.g. bash, tar, echo
& so on) handle specially *, {} and some other symbols in
command-line, even when being invoked not from shell (
The following package has been updated in the Cygwin distribution:
* perl-Text-CSV_XS-1.19-1
Text::CSV_XS provides facilities for the composition and decomposition
of comma-separated values. An instance of the Text::CSV_XS class will
combine fields into a CSV string and parse a CSV string into f
On 06/17/2015 12:55 PM, Kertz, Denis (D)** CTR ** wrote:
We are running cron under the specific cygwin login (not cyg_server).
Presumably there is a solution to this problem. We have 3 Win7 Pro PCs
and this works on one of the PCs (unfortunately, not the one where we need it
to
work) and fails
13 matches
Mail list logo
