Marco Atzeri wrote:
> The current link command is
> /bin/sh ../libtool --tag=CXX --mode=link g++-4 -g -O2 -DHAVE_CONFIG_H
> -mieee-fp -Wall -W -Wshadow -Wold-style-cast -Wformat -g -O2 -g -O2
> -release 3.3.50+ -no-undefined -o liboctave.la -rpath
> /usr/local/lib/octave-3.3.50+ [huge l
I've been using emacs 23.1.1 via cygwin 1.7 all day without a problem. Thanks
Ken for the tip. Thanks to the Cygwin team for a great job.
Ken replied:
> On 10/29/2009 9:28 AM, Rockefeller, Harry wrote:
> > Emacs under X (all three: native cygwin Xwin, X-win32, and Exceed)
> > hangs intermitten
Hi All,
the development of octave is moving to automake + libtool
but we have some problem to convince libtool to correctly link
all the libs on cygwin.
Octave is built in C++, C and Fortran and during
the link phase we are specifing
both C++, C and Fortran installed libs, in same case static.
Su
Hi
I copying files from a linux station to a win32 - cygwin 1.7 station
using the current openssh server from cygwin
I run:
rsync -rpogv . -e "ssh" host:/
This works, except that for some binaries ( I could not determine any
pattern or rule ) ending with .exe .src or .sys , cygwin adds .ex
Florent Fievez wrote:
2009/11/3 Linda Walsh :
^^^ -- another no no**(see bottom)
[curious] Why did you copy [the previous,] complete note
into your response, when [all you said was] "me too"?
I simply clicked on "reply" button of my webmail. I will not do
Christopher Faylor wrote:
> On Wed, Nov 04, 2009 at 03:27:10PM +, Dave Korn wrote:
>> Thomas Werner wrote:
>>> i need to analyse the cygwin1.dlls assembler code for statistical
>>> purpose. but therefor i need to know which compiler is used and its
>>> version. every pe tool i used said "comp
On 11/04/2009 08:45 AM, Joel Gwynn wrote:
Hey all. I'm just wondering what people use in lieu fuse for mounting
sshfs drives in cygwin. Is there a solution, or do I need to buy
something?
Whether or not you want to buy something is certainly your choice. There
is no Cygwin facility for this.
On Wed, Nov 04, 2009 at 03:27:10PM +, Dave Korn wrote:
>Thomas Werner wrote:
>>i need to analyse the cygwin1.dlls assembler code for statistical
>>purpose. but therefor i need to know which compiler is used and its
>>version. every pe tool i used said "compiler unknown", so can anyone
>>help
See previous discussion: http://www.cygwin.com/ml/cygwin/2009-08/msg00362.html
The problem is that rxvt takes ~10 seconds to open if another instance
is already running. Deleting /var/run/utmp solves the problem. I am
running as an administrator.
Unfortunately, it seems to have fixed itself, but
On 11/04/2009 07:11 AM, Steven Henke wrote:
Hello,
What is the status of Cygwin under WinXP, non-blocking i/o reads from
/dev/ttyS0 or /dev/com1 type devices?
Writing to the serial port works but I can't get it to not block on
reads and forget about handling a sigaction SIGIO event.
Any ideas?
Thomas Werner wrote:
> hi,
>
> i need to analyse the cygwin1.dlls assembler code for statistical
> purpose. but therefor i need to know which compiler is used and its
> version. every pe tool i used said "compiler unknown", so can anyone
> help me?
It is compiled by the version of gcc-4.3.4 cur
On Nov 4 09:34, Ken Brown wrote:
> On 11/3/2009 9:54 AM, Corinna Vinschen wrote:
> >- Add a bigger patch which allows by default to run multiple Cygwin
> > installations in parallel [...]
>
> I experimented a little with the new features and found a couple of
> glitches. My normal cygwin instal
Yaakov (Cygwin/X) wrote:
> While trying to build 2.28 I came across a possible
> incompatibility between the implib generated by dlltool and auto-import
> linkage:
Thanks for the STC. I'm pretty sure this is a real binutils bug, Kai and I
were discussing the amount of overlapping code betwee
On 11/3/2009 9:54 AM, Corinna Vinschen wrote:
- Add a bigger patch which allows by default to run multiple Cygwin
installations in parallel without interferring and without interaction
between processes running within these installations. This is done by
computing a key value from the inst
On Nov 4 12:28, Ali Irfan Ustek wrote:
> Hi all,
>
> I did an update today and when I run xhere command I get
>
> $ xhere /bin/bash.exe /cygdrive/c
> /usr/bin/cygpath.exe: error while loading shared libraries:
> cygstdc++-6.dll: cannot open shared object file: No such file or
> directory
That's
Thomas Werner wrote:
i need to analyse the cygwin1.dlls assembler code for statistical
purpose. but therefor i need to know which compiler is used and its
version. every pe tool i used said "compiler unknown", so can anyone
help me?
If a guess that it may have been done with a gcc cross co
Hey all. I'm just wondering what people use in lieu fuse for mounting
sshfs drives in cygwin. Is there a solution, or do I need to buy
something?
TIA,
Joel
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwi
Hi all,
I did an update today and when I run xhere command I get
$ xhere /bin/bash.exe /cygdrive/c
/usr/bin/cygpath.exe: error while loading shared libraries:
cygstdc++-6.dll: cannot open shared object file: No such file or
directory
Starting /bin/bash.exe
And actually directory is not changed
Hello,
What is the status of Cygwin under WinXP, non-blocking i/o reads from
/dev/ttyS0 or /dev/com1 type devices?
Writing to the serial port works but I can't get it to not block on
reads and forget about handling a sigaction SIGIO event.
Any ideas?
Cheers,
Steven Henke
P.S.
$ uname -r
1.5.2
hi,
i need to analyse the cygwin1.dlls assembler code for statistical
purpose. but therefor i need to know which compiler is used and its
version. every pe tool i used said "compiler unknown", so can anyone
help me?
if it's important. the file version i'm talking about is 1005.25.0.0.
pleas
On Nov 3 20:13, Charles Wilson wrote:
> Corinna Vinschen wrote:
> > Maybe Chuck can make this definitive?
>
> But that's not to say there aren't some packages out there that do
> something evil like this:
>
> #if defined(__HPUX__)
> # define MODULE_EXTENSION ".sl"
> #elif !defined(__CYGWIN__) &&
On Nov 4 06:19, Andy Koppe wrote:
> 2009/11/4 Linda Walsh:
> >> C: and C:\ aren't the same thing in DOS/cmd.exe. C: means the current
> >> directory of the C drive, whereas C:\ means the root directory of the
> >> C drive. Within each cmd.exe session, each drive has its own current
> >> directory.
22 matches
Mail list logo
