d.henman writes:
>
[...]
Please keep that conversation on the cygwin-apps list. The audience there
is more appropriate for what Dave K was asking.
..mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cyg
I agree that it should be released. The sooner the better.
It might help me and others with some building problems I've runn into, that
didn't exist before. At the very least, it would reduce the number of variables
that might be the cause of unsuccessful builds.
Dave Korn wrote:
> Hi all,
On 2013-03-27, Adam Dinwoodie wrote:
> Having bash-completion installed significantly slows down starting a new
> Cygwin
> Bash login shell. It's a problem I've noticed, and I've seen other users
> report it on this list and elsewhere, too. I've done a bit of digging into
> what the problem is,
On Tue, Apr 09, 2013 at 08:04:29PM +0400, Ilya Basin wrote:
>Here's my script that works on linux:
>
>cmd="ssh -T -N -g -1 -L 10001:anotherhost:22"
>fifo=`mktemp -u`
>mkfifo "$fifo"
>$cmd <"$fifo" &
>exec 3>"$fifo"
># message: Pseudo-terminal will not be allocated because st
> Should be fixed in 0.9.7.
Yes, it is fixed. The information reported now is:
OS Name: Microsoft Windows Server 2012
OS Version:64 bits (Build 9200).
Thanks a lot for your time.
Regards.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Here's my script that works on linux:
cmd="ssh -T -N -g -1 -L 10001:anotherhost:22"
fifo=`mktemp -u`
mkfifo "$fifo"
$cmd <"$fifo" &
exec 3>"$fifo"
# message: Pseudo-terminal will not be allocated because stdin is not a
terminal.
# netstat shows that port 10001 is LISTE
On 4/9/2013 11:19 AM, Dr. Rainer Woitok wrote:
Greetings,
the problem I'm having seems to be either Mercurial or Cygwin related.
I'm currently using Mercurial 2.4.2 and Cygwin 1.7.17, which I'm running
with the "winsymlinks" option in the "CYGWIN" environment variable:
@echo off
set CYGWIN=g
Greetings,
the problem I'm having seems to be either Mercurial or Cygwin related.
I'm currently using Mercurial 2.4.2 and Cygwin 1.7.17, which I'm running
with the "winsymlinks" option in the "CYGWIN" environment variable:
@echo off
set CYGWIN=glob:noignorecase proc_retry:10 nodosfilewarning w
On 4/9/2013 3:50 AM, Corinna Vinschen wrote:
On Apr 8 17:01, Charles Wilson wrote:
user@machine /k/path $ cp bob fred
cp: skipping file `bob', as it was replaced while being copied
cp checks the inode numbers before and after, and it seems the inode
numbers on this drive are not persistent.
On Apr 9 09:19, Charles Wilson wrote:
> On 4/9/2013 5:16 AM, Corinna Vinschen wrote:
> >On Apr 8 13:54, Charles Wilson wrote:
> >>But doesn't this mean that the cygwin's w32api package should
> >>exclude all of the ddk headers; it's not simply a case that you
> >>"shouldn't" use ddk/*.h, but that
On 4/9/2013 5:16 AM, Corinna Vinschen wrote:
On Apr 8 13:54, Charles Wilson wrote:
But doesn't this mean that the cygwin's w32api package should
exclude all of the ddk headers; it's not simply a case that you
"shouldn't" use ddk/*.h, but that you actually cannot, because
compilation will fail.
On Tue, Apr 9, 2013 at 2:23 AM, Corinna Vinschen wrote:
No, not really. You can do that, and I still use the Linux cross
compiler to build Cygwin, but we don't really *have* to bootstrap
anymore.
$ cygport cygwin.cygport download prep compile install package
or
$ cygp
Greetings, andrei!
> result of 'ls /dev/sd*':
> I should have /dev/shm and /dev/mqueue and possibly other directories in the
> /dev directory?
If you list files matching /dev/sd* pattern, you're unlikely to see anything
other, than what you're looking for.
I hope, that was a simple oversight on
On Apr 9 10:41, andrei wrote:
> Larry Hall (Cygwin cygwin.com> writes:
> > What's the result of 'ls /dev/sd*'?
>
> Hello Larry,
>
> result of 'ls /dev/sd*':
>
> $ ls /dev/sd*
> /dev/sda /dev/sda2 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
> /dev/sda1 /dev/sdb /dev/sdc /dev/sdd /dev/s
On 2013-04-07 15:38, David Stacey wrote:
I would like to adopt perl-Text-CSV and perl-Text-CSV_XS. At the moment,
both of these are present in Cygwin Ports, and previously Yaakov asked
for first refusal when it comes to adopting packages that are already
present in Ports.
Yaakov: If you are happ
Larry Hall (Cygwin cygwin.com> writes:
>
> On 4/8/2013 12:04 PM, andrei wrote:
> > Hi
> >
> > Running version 1.7.17-1
> >
> > Trying to $ dd if=/dev/sdb of=/dev/null count=10 - compact flash card in
the
> > PC CF card reader.
> >
> > Running above command displays: dd: opening `/dev/sdb': Perm
2013/4/9 Corinna Vinschen schrieb:
> On Apr 9 01:05, Charles Wilson wrote:
>> The following are missing from the definition of enum
>> WELL_KNOWN_SID_TYPE in winnt.h:
>> [...]
>> Should I send this as a patch to mingw64.sf (are they the
>> maintainers of our w32api now?)
>
> Yes, and yes.
>
>
> Th
On Apr 9 11:16, Corinna Vinschen wrote:
> On Apr 8 13:54, Charles Wilson wrote:
> > On 4/8/2013 3:48 AM, Corinna Vinschen wrote:
> > >On Apr 8 01:59, Charles Wilson wrote:
> > >>Any suggestions for a fix?
> > >
> > >Yes. Do not use the ddk headers with Cygwin. Not only that intrin.h is
> > >re
On Apr 8 13:53, Gregory M. Turner wrote:
> On 4/8/2013 2:38 AM, Corinna Vinschen wrote:
> >On Apr 8 10:10, Corinna Vinschen wrote:
> >>On Apr 7 13:53, Gregory M. Turner wrote:
> >>>On my cygwin64, all bash process substitutions fail:
> >>>
> >>>$ ls -l <(echo foo)
> >>>lrwxrwxrwx 1 greg None 0 A
On Apr 9 01:05, Charles Wilson wrote:
> The following are missing from the definition of enum
> WELL_KNOWN_SID_TYPE in winnt.h:
> [...]
> Should I send this as a patch to mingw64.sf (are they the
> maintainers of our w32api now?)
Yes, and yes.
Thanks,
Corinna
--
Corinna Vinschen
On Apr 8 13:54, Charles Wilson wrote:
> On 4/8/2013 3:48 AM, Corinna Vinschen wrote:
> >On Apr 8 01:59, Charles Wilson wrote:
> >>Any suggestions for a fix?
> >
> >Yes. Do not use the ddk headers with Cygwin. Not only that intrin.h is
> >really missing(*), the ddk headers in mingw-w64 are not f
On Apr 8 17:01, Charles Wilson wrote:
> On 3/29/2013 4:36 PM, Larry Hall (Cygwin) wrote:
> >On 3/29/2013 4:25 PM, Bill Priest wrote:
> >>#3 I saw lots of complaints and responses for requests for drive info;
> >>but I never saw an explanation of why this checking is being done.
> >
> >I haven't lo
22 matches
Mail list logo
