Dave Korn writes:
> Bill McCormick wrote:
>> Bill McCormick wrote:
>>> Bill McCormick wrote:
Hello,
There's something wrong with my man pager; it's producing garbage
output. My ~/.bashrc has these entries:
export MANPAGER='less -isrR'
export PAGER='less -r'
--- I wrote:
>>> For me, using the unpatched version, (not the CVS version), the
>>> persistence works some times only. At other times the semaphore
>>> disappears with the Control c.
It is not reproducible.
I'm sorry from wasting your time.
--
Unsubscribe info: http://cygwin.com/ml/#
Paul August wrote:
> David, thanks for the further information. I will try to follow your
> steps exactly (except for a fresh installation of Windows part) and
> see what happens.
YW. :-) Please feel free to expand, clarify, edit, and/or otherwise
improve upon the procedure and repost. For exam
This message was sent with wrong subject line. So I try again. Paul
I believe this is for the trouble I previously reported.
David, thanks for the further information. I will try to follow your steps
exactly
(except for a fresh installation of Windows part) and see what happens.
Paul.
>
Bill McCormick wrote:
> Bill McCormick wrote:
>> Bill McCormick wrote:
>>> Hello,
>>>
>>> There's something wrong with my man pager; it's producing garbage
>>> output. My ~/.bashrc has these entries:
>>>
>>> export MANPAGER='less -isrR'
>>> export PAGER='less -r'
>>>
>> I've looked the the archives
>> The persistence of the semaphore also works for you?
>>
>> For me, using the unpatched version, (not the CVS version), the
>> persistence works some times only. At other times the semaphore
>> disappears with the Control c.
>
> The semaphore is backed by a file on disk. If you don't call
>
I believe this is for the trouble I previously reported.
David, thanks for the further information. I will try to follow your steps
exactly
(except for a fresh installation of Windows part) and see what happens.
Paul.
> -Inline Message Follows-
>
> What's your trouble?
>
> 2009/6
On Jun 12 15:56, Pedro Izecksohn wrote:
> Corinna Vinschen read my mind.
>
> > What is semtool?
>
> semtool - A utility for tinkering with semaphores
>
> USAGE: semtool (c)reate
> (l)ock
> (u)nlock
> (d)elete
> (m)ode
>
Corinna Vinschen read my mind.
> What is semtool?
semtool - A utility for tinkering with semaphores
USAGE: semtool (c)reate
(l)ock
(u)nlock
(d)elete
(m)ode
It comes in some package available through the Cygwin's insta
On 12/06/2009 05:19, Corinna Vinschen wrote:
On Jun 12 12:16, Corinna Vinschen wrote:
Certainly a good idea. I don't know if it would hurt if too many
symbols could be linked against via librt.a. We could move the
realtime functions from timer.cc and times.cc into its own source
file. Or we c
On Jun 12 17:38, Thomas Wolff wrote:
> IWAMURO Motonori wrote to me by private mail:
> > I oppose your proposal because I think that it is useless for us.
> >
> > 2009/6/6 Thomas Wolff :
> >> the intention is that the "codepage" information should be the same
> >> for all locales having thbe "UTF-
IWAMURO Motonori wrote to me by private mail:
> I oppose your proposal because I think that it is useless for us.
>
> 2009/6/6 Thomas Wolff :
>> the intention is that the "codepage" information should be the same
>> for all locales having thbe "UTF-8" (or any other) charmap. So you
>> cannot free
Bill McCormick wrote:
Bill McCormick wrote:
Bill McCormick wrote:
Hello,
There's something wrong with my man pager; it's producing garbage
output. My ~/.bashrc has these entries:
export MANPAGER='less -isrR'
export PAGER='less -r'
I've looked the the archives and others have other problems
Bill McCormick wrote:
Bill McCormick wrote:
Hello,
There's something wrong with my man pager; it's producing garbage
output. My ~/.bashrc has these entries:
export MANPAGER='less -isrR'
export PAGER='less -r'
I've looked the the archives and others have other problems and
solutions that ar
Bill McCormick wrote:
Hello,
There's something wrong with my man pager; it's producing garbage
output. My ~/.bashrc has these entries:
export MANPAGER='less -isrR'
export PAGER='less -r'
I've looked the the archives and others have other problems and
solutions that are documented (ref:
htt
On Jun 12 14:30, Fr?d?ric Bron wrote:
> I used the following program to obtain mac address and ip of network
> adpaters. It works fine with 1.5 but not with 1.7.
>
> Output with 1.5:
> sock=3
> trying eth0
> mac: 00.1f.3c.57.XX.XX, ip: XXX.XXX.XXX.XXX
> trying eth1
> mac: 00.1d.09.df.XX.XX, ip: XX
On Fri, Jun 12, 2009 at 07:16:55PM +0800, Pan ruochen wrote:
>Well, I was always confused in selecting/deselecting packages during
>setup. And I often got the information about some package is required
>by another in the final step. So I decided to try patching the setup
>source code to make the se
On Fri, Jun 12, 2009 at 10:26:25AM +0200, Corinna Vinschen wrote:
>On Jun 11 13:41, Andrew Schulman wrote:
>> Every time I run ipconfig from bash, I get the following:
>>
>> $ ipconfig
>> 3 [main] bash 1192! _pinfo::dup_proc_pipe: DuplicateHandle failed,
>> pid 1192, hProcess 0x65C, wr_proc_
New releases of the emacs, emacs-X11, and emacs-el packages, 23.0.92-10,
are now available for those testing cygwin 1.7, leaving 21.2-13 as
previous. These are essentially the same as the experimental versions
that were made available a few weeks ago, but they have now been
promoted to "current".
I used the following program to obtain mac address and ip of network
adpaters. It works fine with 1.5 but not with 1.7.
Output with 1.5:
sock=3
trying eth0
mac: 00.1f.3c.57.XX.XX, ip: XXX.XXX.XXX.XXX
trying eth1
mac: 00.1d.09.df.XX.XX, ip: XXX.XXX.XXX.XXX
trying eth2
mac: 08.00.27.00.XX.XX, ip: XX
Pan ruochen wrote:
Well, I was always confused in selecting/deselecting packages during
setup. And I often got the information about some package is required
by another in the final step. So I decided to try patching the setup
source code to make the setup more easy for me (and maybe for other
pe
Well, I was always confused in selecting/deselecting packages during
setup. And I often got the information about some package is required
by another in the final step. So I decided to try patching the setup
source code to make the setup more easy for me (and maybe for other
people).
Until now I'v
Corinna Vinschen wrote:
> On Jun 12 11:51, Dave Korn wrote:
>> Corinna Vinschen wrote:
>>> On Jun 12 12:16, Corinna Vinschen wrote:
On Jun 12 04:47, Yaakov S wrote:
> On 12/06/2009 03:49, Corinna Vinschen wrote:
>> Even if linking against librt.a would be necessary on Cygwin
> But
On Jun 12 11:51, Dave Korn wrote:
> Corinna Vinschen wrote:
> > On Jun 12 12:16, Corinna Vinschen wrote:
> >> On Jun 12 04:47, Yaakov S wrote:
> >>> On 12/06/2009 03:49, Corinna Vinschen wrote:
> Even if linking against librt.a would be necessary on Cygwin
> >>> But a stub librt.a would be hel
Corinna Vinschen wrote:
> On Jun 12 12:16, Corinna Vinschen wrote:
>> On Jun 12 04:47, Yaakov S wrote:
>>> On 12/06/2009 03:49, Corinna Vinschen wrote:
Even if linking against librt.a would be necessary on Cygwin
>>> But a stub librt.a would be helpful nonetheless. It looks like most of
>>>
Corinna Vinschen wrote:
> On Jun 12 01:50, Pedro Izecksohn wrote:
>> Also: gcc4 does not understand the option "-lrt" so it must be removed.
>
> Even if linking against librt.a would be necessary on Cygwin, which it
> isn't, the gcc call is wrong. The libs must always follow the object
> files
On Jun 12 10:49, Corinna Vinschen wrote:
> SUSv4 states:
>
> The name argument conforms to the construction rules for a pathname,
> except that the interpretation of characters other than the
> leading character in name is implementation-defined, [...]
>
> If name begins with the chara
On Jun 12 12:16, Corinna Vinschen wrote:
> On Jun 12 04:47, Yaakov S wrote:
> > On 12/06/2009 03:49, Corinna Vinschen wrote:
> >> Even if linking against librt.a would be necessary on Cygwin
> >
> > But a stub librt.a would be helpful nonetheless. It looks like most of
> > the relevant symbols a
On Jun 12 04:47, Yaakov S wrote:
> On 12/06/2009 03:49, Corinna Vinschen wrote:
>> Even if linking against librt.a would be necessary on Cygwin
>
> But a stub librt.a would be helpful nonetheless. It looks like most of
> the relevant symbols are in posix_ipc.cc, timer.cc, and times.cc, but
> t
On 12/06/2009 03:49, Corinna Vinschen wrote:
Even if linking against librt.a would be necessary on Cygwin
But a stub librt.a would be helpful nonetheless. It looks like most of
the relevant symbols are in posix_ipc.cc, timer.cc, and times.cc, but
there are other symbols defined in the latter
On Jun 12 01:50, Pedro Izecksohn wrote:
> Does the function sem_open work for anyone using Cygwin 1.7.0 ?
Yes.
> How to use semtool ?
What is semtool?
> I wrote an example that works on Jaunty on x86-64 but not on Cygwin:
> http://www.izecksohn.com/pedro/c/semaphores/semaphores.tar.gz
Wo
On Jun 11 13:41, Andrew Schulman wrote:
> Every time I run ipconfig from bash, I get the following:
>
> $ ipconfig
> 3 [main] bash 1192! _pinfo::dup_proc_pipe: DuplicateHandle failed,
> pid 1192, hProcess 0x65C, wr_proc_pipe 0x704, Win32 error 5
>
> The command then runs apparently normally
32 matches
Mail list logo
