Larry Hall (Cygwin) wrote:
fred wrote:
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll
On Sat, Dec 20, 2008 at 12:16:52AM -0500, Larry Hall (Cygwin) wrote:
> fred wrote:
>> Larry Hall (Cygwin) wrote:
FAQ: http://cygwin.com/faq/
>>>
>>> ?
>>>
>>> My WAG is that you're building in the source directory which, as the FAQ
>>> says, is a no-no.
>>>
>> ok thanks, but
fred wrote:
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a FA
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a FAQ on this ? haven;t found it
Gary R. Van Sickle wrote:
Another one who believes what their calendar tells them?
Another one who doubts the calendar and can't do math...
Then riddle me this Andrew: If this were in fact the 21st century (AKA
"The Future"),
But you see that's the thing. It's not AKA "The Future" - it's now.
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a FAQ on this ? haven;t found it though
Than
Steve Rainbird wrote:
If I do the following
xx &
pid=$!
I get the cygwin pid.
Is there a way of getting the real windows pid?
Not directly, no. But 'ps -W' will show you the Windows PID as well.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc.
If I do the following
xx &
pid=$!
I get the cygwin pid.
Is there a way of getting the real windows pid?
--
Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
On 12/19/2008 4:38 PM, Angelo Graziosi wrote:
...and, last but not least, yes we need a Cygwin Emacs maintainer:
There *is* an official emacs maintainer, Steffen Sledz, but there's no
indication that he monitors this list for emacs questions/problems. The
last message I saw from him was to t
Lawrence Mayer wrote:
On Dec 18 20:53, Lawrence Mayer wrote:
Is there any way to get noacl functionality when using MS-DOS
destination
paths?
My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
C:\cygwin\bin\mkdir.exe /c/foo
creates directory C:\foo with NTFS default perm
On Dec 18 20:53, Lawrence Mayer wrote:
Is there any way to get noacl functionality when using MS-DOS destination
paths?
My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
C:\cygwin\bin\mkdir.exe /c/foo
creates directory C:\foo with NTFS default permissions inherited from
p
Good afternoon,
Corinna Vinschen wrote:
[...]
Fixed in CVS.
[...]
Closing the loop: I got the cygwin update today and it works for me.
Thanks!
--Glenn S.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Ken Brown wrote:
And I think Angelo has built CVS versions of emacs 23 with it
Yes, I confirm. I build Emacs-23 weekly.
In the last year many things have changed, and in better.
Now it bootstraps in less than 20 minutes (before, more than an hour).
Also, some strange bootstrap failure (which
Alex Martin wrote:
Gary R. Van Sickle wrote:
A few gaps that need filling before anything better than SWAGs can
come your
way:
- Is this app a Cygwin app,
No, it is a windows app.
I am using cygwin primarily because I get the /dev/ttyS* devices.
If you're using /dev/ttyS*, then you
Gary R. Van Sickle wrote:
From: Alex Martin
Well, I was using a port monitor to debug some of the traffic
between my serial device, and my software, when I noticed the
output accidentally.
I am not sure when the behavior started. It used to work
fine, I was using printf to debug things,
> From: Alex Martin
> Gary R. Van Sickle wrote:
> >> From: Alex Martin
> >>
> >> Well, I was using a port monitor to debug some of the
> traffic between
> >> my serial device, and my software, when I noticed the output
> >> accidentally.
> >>
> >> I am not sure when the behavior started. It use
Matt Wozniski wrote:
On Fri, Dec 19, 2008 at 2:30 PM, Gary R. Van Sickle wrote:
From: Alex Martin
Hello,
I have a cygwin environment, running some software I am
writing to talk to some serial devices.
Somehow, trying to debug why I could not see printf output to
console, I ran a serial port
> From: Alex Martin
>
> Well, I was using a port monitor to debug some of the traffic
> between my serial device, and my software, when I noticed the
> output accidentally.
>
> I am not sure when the behavior started. It used to work
> fine, I was using printf to debug things, then I turned o
Well, I was using a port monitor to debug some of the traffic between my
serial device, and my software, when I noticed the output accidentally.
I am not sure when the behavior started. It used to work fine, I was
using printf to debug things, then I turned off all of those printf
statements,
[Followups set to -talk due to apropos but not-necessarily-Cygwin-specific
devolution of the discussion]
> From: Corinna Vinschen
>
> On Dec 19 10:29, Gary R. Van Sickle wrote:
> > > From: Andrew DeFaria
> > >
> > > Mark J. Reed wrote:
> > > > On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle
On Fri, Dec 19, 2008 at 2:30 PM, Gary R. Van Sickle wrote:
>> From: Alex Martin
>>
>> Hello,
>>
>> I have a cygwin environment, running some software I am
>> writing to talk to some serial devices.
>>
>> Somehow, trying to debug why I could not see printf output to
>> console, I ran a serial port s
> From: Alex Martin
>
> Hello,
>
> I have a cygwin environment, running some software I am
> writing to talk to some serial devices.
>
> Somehow, trying to debug why I could not see printf output to
> console, I ran a serial port sniffer and voila all of my
> printf commands are writing on th
Hello,
I have a cygwin environment, running some software I am writing to talk
to some serial devices.
Somehow, trying to debug why I could not see printf output to console, I
ran a serial port sniffer and voila all of my printf commands are
writing on the serial port.
Any idea how to fix
On Dec 19 12:25, Andrew Schulman wrote:
> > > I tested it, and it fixes the error. Nice hunting.
> >
> > Sure? Did it occur reliably so far and now it doesn't? I thought
> > it only occurs intermittently. Maybe you could test a while longer...
>
> The error was occurring reliably on the first
> > I tested it, and it fixes the error. Nice hunting.
>
> Sure? Did it occur reliably so far and now it doesn't? I thought
> it only occurs intermittently. Maybe you could test a while longer...
The error was occurring reliably on the first, and only the first, login shell
after each reboot.
On Dec 19 12:01, Andrew Schulman wrote:
> > Working (strace2):
> >
> > pwdgrp::load: \etc\passwd curr_lines 20308
> >
> > Failing (strace1):
> >
> > pwdgrp::load: \etc\passwd curr_lines 520
> >
> > So Cygwin thinks there are only 520 lines in the file, even though it
> > knows that the filesi
On 12/19/2008 11:19 AM, Eli Zaretskii wrote:
Yes, Angelo deserves a lot of kudos for his efforts, but unfortunately
much more is needed. For example, even though it is possible to build
a Cygwin version now, if you are willing to install specific versions
of development tools, the following ent
On Dec 19 10:29, Gary R. Van Sickle wrote:
> > From: Andrew DeFaria
> >
> > Mark J. Reed wrote:
> > > On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
> > >> Me too, and like you and the OP report, it "just works"
> > 99.44% of the
> > >> time. Of course, since it's not the 21st centur
> Working (strace2):
>
> pwdgrp::load: \etc\passwd curr_lines 20308
>
> Failing (strace1):
>
> pwdgrp::load: \etc\passwd curr_lines 520
>
> So Cygwin thinks there are only 520 lines in the file, even though it
> knows that the filesize is 2490367 bytes.
OK, good. Curious that the bad behavi
> From: Andrew DeFaria
>
> Mark J. Reed wrote:
> > On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
> >> Me too, and like you and the OP report, it "just works"
> 99.44% of the
> >> time. Of course, since it's not the 21st century yet, many Unixoid
> >> programs are still unable to ha
> Date: Fri, 19 Dec 2008 10:21:06 -0500
> From: Ken Brown
> CC: eliz at gnu dot org
>
> On 12/19/2008 3:27 AM, Eli Zaretskii wrote:
>
> > I guess this is an ample opportunity to call for volunteers to come on
> > board and help maintaining the Cygwin build of Emacs. As of now, the
> > Cygwin bu
Mark J. Reed wrote:
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me too, and like you and the OP report, it "just works" 99.44% of the
time. Of course, since it's not the 21st century yet, many Unixoid
programs are still unable to handle text files properly, hence the
remaining 0
on Fri Dec 19 2008, Eric Blake wrote:
> By the way, the program 'd2u' is your friend.
I'm on *nix now to avoid all such issues, but yeah, when I have to run
Cygwin in a VM, it's a thing to keep in mind.
Thanks for all the responses everyone.
--
Dave Abrahams
BoostPro Computing
http://www.boo
On Fri, Dec 19, 2008 at 06:34:19AM -0700, Eric Blake wrote:
>According to David Abrahams on 12/18/2008 7:42 PM:
>>Can anyone explain why the installer began recommending using *nix line
>>ending conventions?
>
>Because Unix line endings work out of the box with more programs, and
>because it is fas
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
> Me too, and like you and the OP report, it "just works" 99.44% of the time.
> Of course, since it's not the 21st century yet, many Unixoid programs are
> still unable to handle text files properly, hence the remaining 0.66%.
100 - 99.44
On Dec 19 09:38, Andrew Schulman wrote:
> > On Dec 17 09:39, Andrew Schulman wrote:
> > > After a reboot, I ran
> > >
> > > strace -o strace.txt c:\cygwin-1.7\bin\bash.exe --login
> > >
> > > and observed the error in the shell that started. The strace output is at
> > > http://home.comcast.net/
On 12/19/2008 3:27 AM, Eli Zaretskii wrote:
I guess this is an ample opportunity to call for volunteers to come on
board and help maintaining the Cygwin build of Emacs. As of now, the
Cygwin build has some known ``stability issues'' (read: it sometimes
crashes during the build or in routine ope
> On Dec 17 09:39, Andrew Schulman wrote:
> > After a reboot, I ran
> >
> > strace -o strace.txt c:\cygwin-1.7\bin\bash.exe --login
> >
> > and observed the error in the shell that started. The strace output is at
> > http://home.comcast.net/~aschulman2/cygwin-1.7/strace.txt.bz2 .
>
> Thanks fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new version of the asciidoc package, asciidoc 8.3.1-2, is now available
for download, replacing the broken 8.3.1-1 and leaving 8.2.7-1 as previous.
NEWS:
=
This is a repackage of a new upstream release, which fixes my packaging
bug caused by ups
On Dec 19 14:14, Corinna Vinschen wrote:
> [...] As usual, please report bugs and problems to the mailing
> list cygwin AT
Erm... "the mailing list cygwin AT cygwin DOT com".
I also forgot to repeat the pointer to the new online documentation:
http://cygwin.com/1.7/cygwin-ug-net/cygwin-ug-net.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steve Rainbird on 12/19/2008 2:22 AM:
> When i run a Fuijitsu Cobol program it requires environmental variables
> starting with the @ sign.
That is inherently non-portable. POSIX states that "Other characters may
be permitted by an imple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to David Abrahams on 12/18/2008 7:42 PM:
> Can anyone explain why the installer began recommending using *nix line
> ending conventions?
Because Unix line endings work out of the box with more programs, and
because it is faster, and because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to AMADE Paul Bernard on 12/19/2008 12:40 AM:
> updated asciidoc
> the asciddoc executable in /usr/bin is empty and does nothing
> how should I correct this?
Indeed, so it is :( Probably due to the fact that asciidoc 8.3.1 switched
from a h
Hi community,
As my (probably) last action before the New Year break (I'll be offline
most of the time until January the 7th), I just uploaded a new Cygwin
1.7 test release, 1.7.0-36.
As announced in my first message about the 1.7 test, just download
http://cygwin.com/setup-1.7.exe and use that
On Dec 18 20:53, Lawrence Mayer wrote:
> Is there any way to get noacl functionality when using MS-DOS destination
> paths?
>
> My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
>
> C:\cygwin\bin\mkdir.exe /c/foo
>
> creates directory C:\foo with NTFS default permissions inhe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the distribution:
*** gamin-0.1.10-1
*** libfam0-0.1.10-1
*** libfam-devel-0.1.10-1
*** libgamin1_0-0.1.10-1
*** libgamin1-devel-0.1.10-1
*** python-gamin-0.1.10-1
gamin is a portable drop-in replacement fo
> From: Spiro Trikaliotis
>
> Hello David,
>
> * On Thu, Dec 18, 2008 at 05:42:20PM -0900 David Abrahams wrote:
> >
> > Can anyone explain why the installer began recommending using *nix
> > line ending conventions? DOS-compatible endings have
> always "just worked"
> > for me and I've heard
When i run a Fuijitsu Cobol program it requires environmental variables
starting with the @ sign.
SET @CBR_CONSOLE=SYSTEM
When I try and set these in a bash shell I get the following.
$ export @CBR_CONSOLE=SYSTEM
-bash: export: `...@cbr_console=system': not a valid identifier
Is there any way
Hello David,
* On Thu, Dec 18, 2008 at 05:42:20PM -0900 David Abrahams wrote:
>
> Can anyone explain why the installer began recommending using *nix line
> ending conventions? DOS-compatible endings have always "just worked"
> for me and I've heard of lots of problems doing it the now-recommende
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cygport has been updated to 0.4.3 for Cygwin 1.5, and 0.9.4 for 1.7,
with similar changes to both:
* Requires libtool-2.2 throughout.
* cygpatch() tries with and without --binary.
* lndirs() uses lndir(1) unconditionally.
* Override pushd and popd w
> From: gustav
> Date: Thu, 11 Dec 2008 21:50:53 -0500 (EST)
>
>
> If you still use Emacs' original Rmail with POP under Cygwin, you may
> have noticed that it doesn't work. The reason is that Rmail tries to
> create a file with a ":" in its name, which Cygwin can't do. A simple
> remedy is to e
Can anyone explain why the installer began recommending using *nix line
ending conventions? DOS-compatible endings have always "just worked"
for me and I've heard of lots of problems doing it the now-recommended
way. See
http://news.gmane.org/find-root.php?message_id=%3ca61d44020812070523t3778f9
53 matches
Mail list logo
