Dave Korn wrote:
Andrew DeFaria wrote:
Found out a funny thing about Cygwin today. I've known for a while that
forward slashes works as well as backslashes when specifying a path to
execute. So all of the following work from a cmd prompt:
C:> C:\Cygwin\bin\ls
C:> C:\Cygwin/bin\ls
C:> C:/Cygwi
On 30/07/2009 08:43, Martine Carannante wrote:
I try to port on CYGWIN an open source which runs correctly on Linux.
In this open source, a shared module (linked with option -shared) is
created and after it's loaded by the main program with lt_dlopen()
function.
On CYGWIN, I have a problem when
Andrew DeFaria wrote:
> Found out a funny thing about Cygwin today. I've known for a while that
> forward slashes works as well as backslashes when specifying a path to
> execute. So all of the following work from a cmd prompt:
>
> C:> C:\Cygwin\bin\ls
> C:> C:\Cygwin/bin\ls
> C:> C:/Cygwin/bin/ls
Found out a funny thing about Cygwin today. I've known for a while that
forward slashes works as well as backslashes when specifying a path to
execute. So all of the following work from a cmd prompt:
C:> C:\Cygwin\bin\ls
C:> C:\Cygwin/bin\ls
C:> C:/Cygwin/bin/ls
Also the following works:
C:>
Chris Sutcliffe wrote:
>> Wanna try strace-ing mintty and shoving the output in a pastebin somewhere
>> for
>> us to take a look at?
>
> Sure think, you can find the strace here:
>
> http://emergedesktop.org/cygwin/mintty.strace
Interesting. Looks like something went wrong during patch conv
> Sure think, you can find the strace here:
Ugh... think = thing
> http://emergedesktop.org/cygwin/mintty.strace
>
> Let me know if there is anything else I can do to help.
Chris
--
Chris Sutcliffe
http://emergedesktop.org
--
Problem reports: http://cygwin.com/problems.html
FAQ:
> Wanna try strace-ing mintty and shoving the output in a pastebin somewhere
> for
> us to take a look at?
Sure think, you can find the strace here:
http://emergedesktop.org/cygwin/mintty.strace
Let me know if there is anything else I can do to help.
Chris
--
Chris Sutcliffe
http://emergede
Chris Sutcliffe wrote:
>> Something still not 100% correct with 1.7.0-54
>>
>> startxwin.bat gives me this error:
>>
>> xterm: Can't execvp /usr/bin/tcsh: Invalid argument
>> xterm: Could not exec /bin/bash: Invalid argument
>>
>> I can start both shells in a DOS window, however.
>
> Starting mint
Hello
--- Haojun Bao wrote:
>
> So one of your program is native and the other cygwin.
>
> It's like a similar issue I met when using native Emacs+Gnus and cygwin
> programs (openssl client) to read imap mails, it is very slow.
>
> I guess it was a pipe size issue, for old DOS compatibility, t
Hello
--- Christopher Faylor wrote:
>
> 1) Cygwin is a free software project so source code is available. If
> you have questions about how stuff is done you can always look at the
> source code.
>
> 2) Please don't use this mailing list to debug problems with Windows
> code. If you don't wan
> Something still not 100% correct with 1.7.0-54
>
> startxwin.bat gives me this error:
>
> xterm: Can't execvp /usr/bin/tcsh: Invalid argument
> xterm: Could not exec /bin/bash: Invalid argument
>
> I can start both shells in a DOS window, however.
Starting mintty with bash also fails with:
exec
The /etc/rc.d/init.d/postgresql script has a bug that makes it slightly
harder to uninstall the service; see the patch below:
$ diff -wup /etc/rc.d/init.d/postgresql{,.mod}
--- /etc/rc.d/init.d/postgresql 2009-01-07 10:48:52.00100 -0600
+++ /etc/rc.d/init.d/postgresql.mod 2009-07-30 18:06
Dave Korn wrote:
Jason Tishler wrote:
Dave,
On Wed, Jul 29, 2009 at 04:27:20PM +0100, Dave Korn wrote:
Jason Tishler wrote:
The following will solve the above build problem:
LDFLAGS=-L/usr/lib/python2.5/config configure
Jason
I believe you're meant to specify L
Hi Corinna,
Something still not 100% correct with 1.7.0-54
startxwin.bat gives me this error:
xterm: Can't execvp /usr/bin/tcsh: Invalid argument
xterm: Could not exec /bin/bash: Invalid argument
I can start both shells in a DOS window, however.
- Jim
On Thu, Jul 30, 2009 at 2:29 PM, Corinna
Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-54.
This fixes the bug I introduced in -53 which resulted in a non-functional
Cygwin DLL when building optimized code. Sorry, guys.
Since that's otherwise identical to -53, I kept the remainder
of the -53 release announcement untou
On Jul 30 18:44, Corinna Vinschen wrote:
> Hi folks,
>
>
> I just uploaded a new Cygwin 1.7 test release, 1.7.0-53.
I removed the -53 test release from cygwin.com. There's a bug which
apparently only occurs in code build with optimization. My local debug
version works, but I have no time to de
On Tue, Jul 28, 2009 at 5:16 AM, Corinna Vinschen wrote:
> Works fine in tcsh.
tcsh uses the csh style of nested backticks, where the inner backticks
are doubled instead of backslashed. So the backticks don't introduce
any extra level of backslash parsing.
Also of note when testing this sort of
> The only way was to back out to the previous version (1.7.0-52)
I'm in the same boat, launching bash.exe with the -53 build was a no-go:
5 [main] bash 5604 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
1600 [main] bash 5604 open_stackdumpfile: Dumping stack trace to
ba
I rebooted - no go
I re-installed - no go
The only way was to back out to the previous version (1.7.0-52)
- Jim
On Thu, Jul 30, 2009 at 12:40 PM, Jim Reisert
AD1C wrote:
> Since the update, nothing works. Here is output from "uname":
>
>
> 3 [main] uname 8664 _cygtls::handle_exceptions: E
On Thu, Jul 30, 2009 at 2:36 PM, Eric Blake wrote:
>> > bash... maybe cygpath, seems to be doing something weird:
> Weird - yes. But buggy - no.
Backtick-quoting rules are strange. For instance, single quotes
within backticks still prevent variable expansion:
$ x=1
$ echo `echo '$x'`
$x
Since the update, nothing works. Here is output from "uname":
3 [main] uname 8664 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
406 [main] uname 8664 open_stackdumpfile: Dumping stack trace to
uname.exe.stackdump
423630 [main] uname 8664 _cygtls::handle_exceptions: Ex
> > bash... maybe cygpath, seems to be doing something weird:
Weird - yes. But buggy - no.
> >
> > $ cygpath -u '\\someuncpath\someshare'
> > //someuncpath/someshare
> > $ echo `cygpath -u '\\someuncpath\someshare'`
> > /cygdrive/c/someuncpath/someshare
> > $ # what's going on here
> > $ echo "`
> > DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed
> 's|/c/\(.\):/|/\1/|')"
> > mkdir -p "$DEVDIR" || result=1
>
> Hmm, this looks kind of fragile. Not to say it looks wrong.
>
> $ cygpath -am /dev/
> C:/cygwin/dev
>
> Ok.
>
> $ echo "C:/$(cygpath -am /dev/)"
> C:/C:/cygwin/dev
I d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martine Carannante wrote, On 30.7.2009 15:43:
> Hi
>
> I try to port on CYGWIN an open source which runs correctly on Linux.
> In this open source, a shared module (linked with option -shared) is
> created and after it's loaded by the main program
- Original Message -
From: "Corinna Vinschen"
On Jul 29 19:25, Christopher Faylor wrote:
On Wed, Jul 29, 2009 at 03:32:28PM +0800, Haojun Bao wrote:
>Christopher Faylor writes:
>
>> On Tue, Jul 28, 2009 at 10:52:44AM +0800, Haojun Bao wrote:
>>>I have debugged it again, and I think
Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-53.
That's really the last test release. Hopefully.
The two problems which had to be fixed are partially fixed now.
You know the drill by now, see the older test release announcements
as http://cygwin.com/ml/cygwin-announce/2009-0
On Jul 29 19:25, Christopher Faylor wrote:
> On Wed, Jul 29, 2009 at 03:32:28PM +0800, Haojun Bao wrote:
> >Christopher Faylor writes:
> >
> >> On Tue, Jul 28, 2009 at 10:52:44AM +0800, Haojun Bao wrote:
> >>>I have debugged it again, and I think I have more clue. I have read the
> >>>how-cygheap-
Brendan Molloy wrote:
> Would I be able to get definitive instructions on setting up a
> successful Cygwin toolchain?
Since I've never gotten around to building myself a Linux-x-Cygwin cross
toolchain, I decided to spend some time this afternoon doing just that. I'll
write it up once I'm done
> > I tried to reproduce on Linux but without success - did you simply
> > run
> > my script or perhaps something else? Do you see error "141" as
> well?
>
> Status 141 is from SIGPIPE. Basically, it happens when the read end
> of the
> pipe exits before the writer. It is not specific to cygwin,
On Thu, Jul 30, 2009 at 09:45:39PM +0800, Haojun Bao wrote:
>Tatsuro MATSUOKA writes:
>> I have involved in the octave project.
>> Octave uses gnuplot as a graphic backend and data are sent and recieved via
>> pipe.
>>
>> A report of slowness issue of the plot on octave on windows reported.
>
>So
On Thu, Jul 30, 2009 at 02:11:10PM +1200, David Antliff wrote:
>On Thu, Jul 30, 2009 at 11:31, Christopher
>Faylor wrote:
>> On Wed, Jul 29, 2009 at 05:16:24PM +1200, David Antliff wrote:
>>>I've noticed a strange problem with bash pipelines in Cygwin that
>>>might indicate some sort of race condit
David Antliff wrote:
> >>I've noticed a strange problem with bash pipelines in Cygwin that
> >>might indicate some sort of race condition. I cannot reproduce the
> >>problem on a Linux system, but it seems easy to reproduce in
> Cygwin.
> >
> > This doesn't appear to be a cygwin problem. I get occa
Tatsuro MATSUOKA writes:
> Hello
>
> I have involved in the octave project.
> Octave uses gnuplot as a graphic backend and data are sent and recieved via
> pipe.
>
> A report of slowness issue of the plot on octave on windows reported.
So one of your program is native and the other cygwin.
It
Hi
I try to port on CYGWIN an open source which runs correctly on Linux.
In this open source, a shared module (linked with option -shared) is
created and after it's loaded by the main program with lt_dlopen() function.
On CYGWIN, I have a problem when I create the module (gcc option
-shared)
> >>I've noticed a strange problem with bash pipelines in Cygwin that
> >>might indicate some sort of race condition. I cannot reproduce the
> >>problem on a Linux system, but it seems easy to reproduce in
> Cygwin.
> >
> > This doesn't appear to be a cygwin problem. I get occasional
> errors
> >
Hello. I've been searching through Google, reading everything I can
and rigorously searched through the mailing lists for information
about setting up a toolchain for Cygwin on Linux.
In http://cygwin.com/ml/cygwin/2008-04/msg00138.html, Brian Dessent says:
"For $deity's sake just use a sysroot; t
Hello
I have involved in the octave project.
Octave uses gnuplot as a graphic backend and data are sent and recieved via
pipe.
A report of slowness issue of the plot on octave on windows reported.
Please see
http://www.nabble.com/Plotting-with-3.2.0-on-Windows-is-SLOO-td24703690.html
I
37 matches
Mail list logo
