I downloaded Cygwin 1.7.0-58 source from path:
http://ftp.eq.uc.pt/software/pc/prog/cygwin/release-2/cygwin/
Also downloaded all the packages of cygwin version 1.7.0.58
ftp://www.fruitbat.org/pub/cygwin/circa-2/index.html";
And followed instructions to compile from below document:
https://cygw
On Mon, Mar 28, 2016 at 7:06 AM, Rashi Singhal wrote:
> Hi,
>
> I am not getting what is wrong in my mail.
>
> I replayed in the last conversation of the message.
"Top-posting" is posting your entire reply at the top of the message
you are replying to rather than placing your reply into logical
pl
Hi,
I am not getting what is wrong in my mail.
I replayed in the last conversation of the message.
On Mon, Mar 28, 2016 at 4:12 PM, Andrey Repin wrote:
> Greetings, Rashi Singhal!
>
>> Thanks a lot for help.
>> Now my compilation went down but again stopped at some point.Its
>> halting in awk
Greetings, Rashi Singhal!
> Thanks a lot for help.
> Now my compilation went down but again stopped at some point.Its
> halting in awk command after warning
> config.status: WARNING: '/oss/src/winsup/Makefile.in' seems to ignore
> the --datarootdir setting
> awk: ./confXqR7rV/subs.awk:1: BEGIN
Hi,
Thanks a lot for help.
Now my compilation went down but again stopped at some point.Its
halting in awk command after warning
config.status: WARNING: '/oss/src/winsup/Makefile.in' seems to ignore
the --datarootdir setting
awk: ./confXqR7rV/subs.awk:1: BEGIN {\r
awk: ./confXqR7rV/subs.awk:1:
On Mar 24, 2016, at 1:29 PM, Warren Young wrote:
>
> On Mar 23, 2016, at 10:20 PM, Rashi Singhal wrote:
>>
>> configure:3288: gcc --version &5
>> gcc (GCC) 4.3.2 20080827 (beta) 2
>> Copyright (C) 2008 Free Software Foundation, Inc.
>
> According to the Cygwin Time Machine, Cygwin was still sh
On Mar 23, 2016, at 10:20 PM, Rashi Singhal wrote:
>
> Is there any other procedure for building an older release of cygwin.
Cygwin is not GCC Ada, nor vice versa.
I’m being pedantic because you’re referencing Cygwin build instructions but
having trouble with a third-party package. You may ha
On Thu, 17 Mar 2016, Rashi Singhal wrote:
Date: Thu, 17 Mar 2016 16:49:22 +0530
From: Rashi Singhal
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.7-58 with windows 2008
Hi,
Greetings, Rashi,
I really need help/clue on this:
We have our system qualified with cygwin 1.7.0.58 and we are
On 17/03/2016 12:19, Rashi Singhal wrote:
Hi,
I really need help/clue on this:
We have our system qualified with cygwin 1.7.0.58 and we are facing
some issue in msgsnd/msgrcv functions.
We have got the fix of this problem but the code change is in
sysv_msg.cc ( under cygserver) by calling msle
Hi,
I really need help/clue on this:
We have our system qualified with cygwin 1.7.0.58 and we are facing
some issue in msgsnd/msgrcv functions.
We have got the fix of this problem but the code change is in
sysv_msg.cc ( under cygserver) by calling msleep
We tried to download source from the pat
Rashi Singhal writes:
> Hello.
>
> Please help me in resolving below compilation error:
> I am compiling Cygwin 1.7.0.58
>
> make[5]: Leaving directory
> `/cygwin-1.7.0-58/i686-pc-cygwin/winsup/w32api/lib/directx'
> make[4]: Leaving directory `/cygwin-1.7.0-58/i686-pc-
cygwin/winsup/w32api/lib'
>
Hello.
Please help me in resolving below compilation error:
I am compiling Cygwin 1.7.0.58
make[5]: Leaving directory
`/cygwin-1.7.0-58/i686-pc-cygwin/winsup/w32api/lib/directx'
make[4]: Leaving directory `/cygwin-1.7.0-58/i686-pc-cygwin/winsup/w32api/lib'
make[3]: Leaving directory `/cygwin-1.
On 09/03/2016 09:00, Rashi Singhal wrote:
Hi ,
We need to download Cygwin version 1.7.0-58 (with source)
Please help us from we can download old versions
http://www.fruitbat.org/Cygwin/#cygwintimemachine
--
Problem reports: http://cygwin.com/problems.html
FAQ: http
Hi ,
We need to download Cygwin version 1.7.0-58 (with source)
Please help us from we can download old versions
On Fri, Mar 4, 2016 at 10:10 PM, Rashi Singhal wrote:
> Hi,
>
> Further to this we could now see that "NO MORE PROCESS" error is
> displayed due to some of the process not get de-qu
Hi,
Further to this we could now see that "NO MORE PROCESS" error is
displayed due to some of the process not get de-queued from memory
Our application use fork process to create child and then pass SIGUSR1
for SIGCHLD to terminate child process.
Sighandler is installed on the start of process.B
On 23/02/2016 04:34, Rashi Singhal wrote:
Hi ,
We have call to "msgsnd" function that fails after processing 3 to 4 messages.
We tried both Block and NO Block mechanism (IPC_NOWAIT)
Also we changes configuration of cygserver.conf .This increases
message processing to 8-10 messages.But fails af
Hi ,
We have call to "msgsnd" function that fails after processing 3 to 4 messages.
We tried both Block and NO Block mechanism (IPC_NOWAIT)
Also we changes configuration of cygserver.conf .This increases
message processing to 8-10 messages.But fails after that.
Attached is cygserver.conf file f
On 22/02/2016 10:50, Rashi Singhal wrote:
Hi ,
Last version working with out application is 1.7.32. We tried with
this version but problem remain same.
With the latest version of cygwin (2.4.1 release) our program gives
compilation error for Yacc and LEX modules.( We are checking on this)
fle
Hi ,
Last version working with out application is 1.7.32. We tried with
this version but problem remain same.
With the latest version of cygwin (2.4.1 release) our program gives
compilation error for Yacc and LEX modules.( We are checking on this)
Please can you suggest something on EAGAIN issue
On 17/02/2016 09:44, Rashi Singhal wrote:
We tried with latest version also . But problem remain same
Assuming you are using IPC cygserver calls
https://cygwin.com/cygwin-ug-net/using-cygserver.html
Is cygserver service running ?
In general it will be difficult to replicate your problem
witho
On 2/17/2016 12:53 AM, Rashi Singhal wrote:
Hi ,
I have a application that is invoked multiple times. Each invocation
accesses shared memory for a performing task.
This all works with Cygwin1.3
Now We are using Cygwin 1.7-58 with windows 2008 after this The number...
Cygwin 1.7.x is actual
Hi Stephen,
On Tue, Jan 19, 2016 at 8:39 AM, Agyeman, Stephen O DLA CTR
Information Operations wrote:
> Good morning,
>
> I hope all is well with you. May you please send me the software for Cygwin
> 1.7 and or send me the link to download it as I do not see in on Cygwin's
> main site anymore.
I faced with same problem also. After quick investigation, I've found that
even after closing cygwin I had one bash process still running. Killing this
process helped me to fix an issue. Now I can launch several mintty sessions
again. Hope it will help.
Br,
Roman
--
View this message in context
On 01/04/2015 07:14 PM, Howard Guo wrote:
> It seems that segfaults go unreported using pthread and Cygwin 1.7.33-2.
>
> Here is a minimal code piece to reproduce:
>
> #include
>
> void* thread_run(void* _) {
> int *p = 0;
> *p = 1;
> return NULL;
> }
>
> int main(int a
I want to go on record that it happening to us, too. And, I can say
that it is happening *much* more since I moved to this machine:
2x AMD Opteron 6134 (16 cores total)
Server 2008 R2 Enterprise, Service Pack 1
Software we have installed on the machine:
ActivePerl
AVG 9.0
Chrome
Jav
On Apr 29 11:35, John Dong wrote:
> Hi,
>
> Cygwin on Windows 7, seems to exhibit a rather peculiar behavior: Sometimes
> the exit status of a Win32 process is incorrectly captured by Cygwin.
Please:
http://cygwin.com/acronyms/#PCYMTWLL
http://cygwin.com/acronyms/#TOFU
> [...]
> > int _tmain(
On Wed, May 25, 2011 at 07:20:35PM -0700, John Dong wrote:
>It's nice to hear from Edward that we're not the only ones to notice
>this behavior.
>
>Of course, patches would be nice, and I would be interested in digging
>in into this if someone familiar with Cygwin's codebase would be
>willing to en
Hi Chris,
It's nice to hear from Edward that we're not the only ones to notice this
behavior.
Of course, patches would be nice, and I would be interested in digging in into
this if someone familiar with Cygwin's codebase would be willing to enlighten
me as to the codepath for grabbing Win32 p
On Wed, May 25, 2011 at 10:16:03AM -0400, Edward Lam wrote:
>On 29/04/2011 2:35 PM, John Dong wrote:
>> Reproducing this seems nondeterministic -- sometimes I can get it to
>> happen in 5 minutes, other times it takes overnight. I've tried using
>> a different shell (like dash), but it doesn't make
On 29/04/2011 2:35 PM, John Dong wrote:
Reproducing this seems nondeterministic -- sometimes I can get it to
happen in 5 minutes, other times it takes overnight. I've tried using
a different shell (like dash), but it doesn't make a difference,
leading me to suspect this to be a lower-level issue
I can still reproduce this on the latest snapshot. I also tried some different
hardware and virtual machines too, and I don't think my machine is to blame.
Has anyone else been able to reproduce this bug? Or have pointers of further
things I can do to diagnose it?
Thanks in advance,
John
On
Hi Edward,
For what it's worth, I just left it running since my last reply and it's still
running. I can fairly confidently say this only happens when executing a
Windows binary from Cygwin.
Any insights or suggestions of further things to test would be greatly
appreciated. These kinds of bugs
Hi Edward,
Yeah, I forgot to mention that I tried scripting it in a batch file outside
cygwin in much the same way as your script, and it ran for a day or two without
fail. I can keep that going for longer just in case it fails less frequently,
but I don't think it's a Windows / MSVCRT bug.
J
On Fri, Apr 29, 2011 at 13:35, John Dong wrote:
>I've tried using a different shell (like dash), but it doesn't make a
>difference, leading me to suspect this to be a lower-level issue within the
>Cygwin DLL.
Have you tried it with the stock Windows command processor? Something
like this (untest
Am 17.03.2011 18:26, schrieb jean-benoit.ouel...@bell.ca:
I changed my LANG from en_US.ISO-8859-1 to C.ISO-8859-1 and it resolved the
problem.
Thanks for your quick input.
Possibly you can use LC_COLLATE and/or LC_CTYPE instead, if you're
looking for narrower overrides.
--
Matthias Andree
I changed my LANG from en_US.ISO-8859-1 to C.ISO-8859-1 and it resolved the
problem.
Thanks for your quick input.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: htt
> From: jean-benoit.ouel...@bell.ca
>
> Hi!
> I just upgraded Cygwin from 1.5.21-2 to 1.7.8-1 and I'm getting
> problems with case sensitivity.
> Let's assume that 'file.csv' contains these 2 lines:
> Hello, 123
> hello, 456
>
> The following commands will output both lines instead of the desired
On 2011-03-17 12:44Z, jean-benoit.ouel...@hidden.ca wrote:
>
> I just upgraded Cygwin from 1.5.21-2 to 1.7.8-1 and I'm getting problems with
> case sensitivity.
> Let's assume that 'file.csv' contains these 2 lines:
> Hello, 123
> hello, 456
>
> The following commands will output both lines inste
On 23/12/2010 05:54, Lucky Lu wrote:
> I am having trouble with building the gcc 4.5.1 with --enable-plugin on
> Cygwin.
Sorry, GCC plugins are only supported on systems that use the ELF executable
file format such as Linux, they can't work on Windows-based systems owing to
limitations of the P
On 10/11/2010 6:29 AM, David Billinghurst wrote:
> Will cygwin 1.7 run on a netbook with an Intel Atom N450 cpu and Win XP
> Home or Win 7 starter?
Yes (tested on Toshiba NB200).
--
René Berber
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/
On Sep 17 10:57, sven-eric.ber...@sanofi-aventis.com wrote:
> Hi,
>
> I have windows 2008 R2 servers with cygwin 1.7 installed.
> When i want to execute the cluster.exe command, I have :
> seber...@flosapptest02 /cygdrive/c/windows/system32
> $ ./cluster res
> bash: ./cluster: No such file or dir
On 8/20/2010 4:04 PM, Larry Hall (Cygwin) wrote:
> On 8/20/2010 3:31 PM, Steve Holden wrote:
[...]
> If rebaseall is "failing", then that makes me think that some kind of
> BLODA is your real issue.
>
Hmm, I didn't check hard enough - it was Spybot. Thanks.
regards
Steve
--
Steve Holden
On 8/20/2010 3:31 PM, Steve Holden wrote:
On 8/20/2010 11:34 AM, Larry Hall (Cygwin) wrote:
On 8/20/2010 11:28 AM, Baldur Gislason wrote:
Hi, I recently installed the latest version of cygwin after using
previous
(1.5) versions without problems. Almost nothing works on 1.7 and even
after
reinst
On 8/20/2010 11:34 AM, Larry Hall (Cygwin) wrote:
> On 8/20/2010 11:28 AM, Baldur Gislason wrote:
>> Hi, I recently installed the latest version of cygwin after using
>> previous
>> (1.5) versions without problems. Almost nothing works on 1.7 and even
>> after
>> reinstalling my machine
>> I still
On 8/20/2010 11:28 AM, Baldur Gislason wrote:
Hi, I recently installed the latest version of cygwin after using previous
(1.5) versions without problems. Almost nothing works on 1.7 and even after
reinstalling my machine
I still have the same problem. My machine runs Windows XP SP2.
My install.lo
On Aug 18 10:07, Christopher Faylor wrote:
> On Wed, Aug 18, 2010 at 09:51:29PM +0800, Huang Bambo wrote:
> >2010/8/18 Eric Blake :
> >> On 08/18/2010 05:08 AM, Corinna Vinschen wrote:
> > Looks like this behaviour is a problem and we should better close the
> > old handle. ?What to do with
On Wed, Aug 18, 2010 at 09:51:29PM +0800, Huang Bambo wrote:
>2010/8/18 Eric Blake :
>> On 08/18/2010 05:08 AM, Corinna Vinschen wrote:
> Looks like this behaviour is a problem and we should better close the
> old handle. ?What to do with the new one? ?Just set it to NULL and
> disallow
2010/8/18 Eric Blake :
> On 08/18/2010 05:08 AM, Corinna Vinschen wrote:
Looks like this behaviour is a problem and we should better close the
old handle. What to do with the new one? Just set it to NULL and
disallow stackdumps as long as we're in a virtual path? Or set it to
On 08/18/2010 05:08 AM, Corinna Vinschen wrote:
>>> Looks like this behaviour is a problem and we should better close the
>>> old handle. What to do with the new one? Just set it to NULL and
>>> disallow stackdumps as long as we're in a virtual path? Or set it to
>>> some well known path, like C
On Aug 18 14:28, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> >>Do you have a series of steps that produces the problem you see?
> >> >>
> >> >
> >> >As I said in previous mail.
> >> >1. cd /cygdriver/i( I is mounted as a usb-stick)
> >> >2. cd /proc 3. Use some tools such as Un
Greetings, Corinna Vinschen!
>> >>Do you have a series of steps that produces the problem you see?
>> >>
>> >
>> >As I said in previous mail.
>> >1. cd /cygdriver/i( I is mounted as a usb-stick)
>> >2. cd /proc 3. Use some tools such as Unlocker to check driver I,
>> >Unlocker said driver I
On Aug 18 01:52, Christopher Faylor wrote:
> On Wed, Aug 18, 2010 at 01:05:13PM +0800, Huang Bambo wrote:
> >>Do you have a series of steps that produces the problem you see?
> >>
> >
> >As I said in previous mail.
> >1. cd /cygdriver/i( I is mounted as a usb-stick)
> >2. cd /proc 3. Use some
On Wed, Aug 18, 2010 at 01:05:13PM +0800, Huang Bambo wrote:
>>Do you have a series of steps that produces the problem you see?
>>
>
>As I said in previous mail.
>1. cd /cygdriver/i( I is mounted as a usb-stick)
>2. cd /proc 3. Use some tools such as Unlocker to check driver I,
>Unlocker said
>
> Do you have a series of steps that produces the problem you see?
>
As I said in previous mail.
1. cd /cygdriver/i( I is mounted as a usb-stick)
2. cd /proc
3. Use some tools such as Unlocker to check driver I, Unlocker said
driver I is locked by bash.
4. cd / ( / is at d:\cygwin )
On 8/17/2010 10:44 PM, Huang Bambo wrote:
cygwin version: 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 Cygwin
I don't know if this happen to previous version or not.
If I first cd to a directory, for example /cygdriver/x
then cd to a virtual directory, for example /proc
the /cygdriver/x will be locke
Eric Blake wrote:
> [reviving an old thread, relevant to today's current bash postinstall
> failures]
> ...
> I'm building a new bash package now that should fix all this mess, by
> using the same means as 000-cygwin-post-install.sh to populate necessary
> entries into /dev.
Splendid! Just for t
[reviving an old thread, relevant to today's current bash postinstall
failures]
On 03/17/2010 12:28 PM, Corinna Vinschen wrote:
> On Mar 17 12:21, Eric Blake wrote:
>> On 03/17/2010 02:19 AM, rolandc wrote:
>>> I do not understand why the postinstall script bash.sh is so complex
>>>
>>> DEVDIR
On 6/2/2010 5:53 AM, Mario Küchler wrote:
Corinna Vinschen wrote:
(...)
In contrast, the behaviour of Cygwin 1.7, which is to read the actual
reparse point content and treat it as symlinks, does not make sense for
remote reparse points, apparently. Only the remote system knows how to
treat them
Corinna Vinschen wrote:
(...)
> In contrast, the behaviour of Cygwin 1.7, which is to read the actual
> reparse point content and treat it as symlinks, does not make sense for
> remote reparse points, apparently. Only the remote system knows how to
> treat them correctly. So I just applied a patc
Jim Reisert AD1C wrote:
What's the simplest migration path from "gcc -mno-cygwin" (gcc3) to
the equivalent in gcc4?
Larry Hall wrote:
It's not ready yet.
For now, as workaround, you could use Cygwin packages (Win32 or Win64)
from[1]:
http://sourceforge.net/projects/mingw-w64/files
(GCC-4
On 6/1/2010 5:45 PM, Jim Reisert AD1C wrote:
Since upgrading to Cygwin 1.7 eons ago, I lost the ability to compile
-mno_cygwin using gcc4. I did find that I can still compile using
gcc3.
What's the simplest migration path from "gcc -mno-cygwin" (gcc3) to
the equivalent in gcc4? I've seen this
On May 18 09:11, Mario Küchler wrote:
> Hi,
>
> there seems to be a change from 1.5 to 1.7 when processing junctions
> (reparse points). This was already discussed here but I want to point to
> an issue when accessing them via SMB.
>
> Both hosts have a local junction from d:\temp to c:\temp.
>
Nellis, Kenneth wrote on 2010-04-19:
From: LiuYan 刘研
Sent: Monday, April 19, 2010 04:51
To: cygwin@cygwin.com
Subject: Cygwin 1.7 man: '-' char in option/switch in man page is not
displayed/not encoded well if LANG=C.UTF-8
After moved from Cygwin 1.5 to Cygwin 1.7, the '-' char in
switch/optio
> From: LiuYan 刘研
> Sent: Monday, April 19, 2010 04:51
> To: cygwin@cygwin.com
> Subject: Cygwin 1.7 man: '-' char in option/switch in man page is not
> displayed/not encoded well if LANG=C.UTF-8
>
>
> After moved from Cygwin 1.5 to Cygwin 1.7, the '-' char in
> switch/option in
> man page is no
LiuYan 刘研 wrote on 2010-04-19:
After moved from Cygwin 1.5 to Cygwin 1.7, the '-' char in switch/option
in
man page is not displayed.
As Cygwin 1.7 have revised to 1.7.5 and cygwin-doc-1.7 is released and
this
problem still exists, so I decide to figure it out.
I have a previous post "C
Dave Korn a écrit :
I'm on the edge of massively deploying Cygwin 1.7 from Cygwin 1.5
(+400 workstations), and I'm concerned about the time setup.exe
takes to verify MD5 packages signature.
When the repository is a remote SaMBa share, it looks that
setup.exe download all packages one time to ch
>>P.S.: I presume the fix will show up in the next Cygwin release.
>Nope. It's just for you. No one else is privileged enough to get the
>fix. :-)
:-))
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.
On 3/19/2010 2:32 PM, Christopher Faylor wrote:
On Fri, Mar 19, 2010 at 02:30:32PM -0400, Larry Hall (Cygwin) wrote:
On 3/19/2010 2:27 PM, Christopher Faylor wrote:
On Fri, Mar 19, 2010 at 05:59:40PM +0100, Schmidt, Oliver wrote:
Thanks for your very active support in solving this issue with o
On Fri, Mar 19, 2010 at 02:30:32PM -0400, Larry Hall (Cygwin) wrote:
>On 3/19/2010 2:27 PM, Christopher Faylor wrote:
>>On Fri, Mar 19, 2010 at 05:59:40PM +0100, Schmidt, Oliver wrote:
>>>Thanks for your very active support in solving this issue with our far
>>>from mainstream scenario!
>>
>>You're
On 3/19/2010 2:27 PM, Christopher Faylor wrote:
On Fri, Mar 19, 2010 at 05:59:40PM +0100, Schmidt, Oliver wrote:
Thanks for your very active support in solving this issue with our far from
mainstream scenario!
You're welcome. It really was a pretty serious problem so I'm glad that
it surfaced
On Fri, Mar 19, 2010 at 05:59:40PM +0100, Schmidt, Oliver wrote:
>Thanks for your very active support in solving this issue with our far from
>mainstream scenario!
You're welcome. It really was a pretty serious problem so I'm glad that
it surfaced and that we were theoretically able to fix it.
>
Hi Christopher,
> How about today's snapshot? Corinna has YA told me what I did wrong with the
> latest round of spinlock changes and today's snapshot reflects her obvious
> fix.
Good news for the weekend! I've been running my original scenario with
20100318 repeatedly all day long. I couldn't r
> Had the same problem, cp and mv appending exe to nearly everything.
> After I upgraded coreutils from 8.4.1 to 8.4.2 the issue has been resolved.
I have coreutils 7.0-2 and "mv" seems to work correctly for me,
however I see that both rsync and rdiff-backup add the .exe suffix
when copying an exe
Herb Maeder maeder.org> writes:
>
> With a fresh install of cygwin-1.7 on a vanilla Vista system, I see that
> the 'mv' command appends a .exe extension to the destination file for any
> source files that have a .bat or .com extensions.
Had the same problem, cp and mv appending exe to nearly ev
On Thu, Mar 18, 2010 at 03:55:48PM +0100, Schmidt, Oliver wrote:
>Hi Corinna,
>
>> Would you mind to give the latest developer snapshot from
>> http://www.cygwin.com/snapshots/ a try? It tries very carefully to
>> eliminate concurrency problems in the initialization phase.
>
>I see. With the same
Hi Corinna,
> Would you mind to give the latest developer snapshot from
> http://www.cygwin.com/snapshots/ a try? It tries very carefully to
> eliminate concurrency problems in the initialization phase.
I see. With the same scenario as in my original posting I trigger an
assertion added by Chris
Oliver,
On Mar 16 13:06, Corinna Vinschen wrote:
> On Mar 16 10:53, Schmidt, Oliver wrote:
> > >No one is doubting that problems exist. That's why we're working
> > >on them.
> >
> > Sorry for again being unclear. The information above was soley meant to
> > complement the cygcheck output - whic
On Mar 17 12:29, Eric Blake wrote:
> On 03/17/2010 12:28 PM, Corinna Vinschen wrote:
> >
> > Nothing of this should be necessary since the 000-cygwin-post-install.sh
> > script from the base-cygwin package already creates /dev.
>
> Does it also create /dev/stdin, or does bash still need to do tha
On Mar 17 19:28, Corinna Vinschen wrote:
> On Mar 17 12:21, Eric Blake wrote:
> > On 03/17/2010 02:19 AM, rolandc wrote:
> > > I do not understand why the postinstall script bash.sh is so complex
> > >
> > > DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed
> > > 's|/c/\(.\):/|/\1/|')"
>
On 03/17/2010 12:28 PM, Corinna Vinschen wrote:
>
> Nothing of this should be necessary since the 000-cygwin-post-install.sh
> script from the base-cygwin package already creates /dev.
Does it also create /dev/stdin, or does bash still need to do that?
--
Eric Blake ebl...@redhat.com+1-80
Eric Blake wrote:
> On 03/17/2010 02:19 AM, rolandc wrote:
>> I do not understand why the postinstall script bash.sh is so complex
>>
>> DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed
>> 's|/c/\(.\):/|/\1/|')"
>> mkdir -p "$DEVDIR" || result=1
>>
>> it would be simple (too simple?)
On Mar 17 12:21, Eric Blake wrote:
> On 03/17/2010 02:19 AM, rolandc wrote:
> > I do not understand why the postinstall script bash.sh is so complex
> >
> > DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed
> > 's|/c/\(.\):/|/\1/|')"
> > mkdir -p "$DEVDIR" || result=1
> >
> > it woul
On 03/17/2010 02:19 AM, rolandc wrote:
> I do not understand why the postinstall script bash.sh is so complex
>
> DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed
> 's|/c/\(.\):/|/\1/|')"
> mkdir -p "$DEVDIR" || result=1
>
> it would be simple (too simple?) to
> mkdir -p /dev ||
On 03/16/2010 09:54 AM, Andy Koppe wrote:
> /dev would be E:\cygwin1.7\dev, not E:\cygwin1.7\E\cygwin1.7\dev.
>
> Looks like a bug to me, and the finger of blame points at
> /etc/postinstall/{00,}bash.sh:
>
> DEVDIR="$(cygpath -au "C:/$(cygpath -am /dev/)" | sed 's|/c/\(.\):/|/\1/|')"
> mkdir -p
2010/3/16 Cliff Hones :
> Andy Koppe wrote:
>> Christopher Faylor:
>>> rolandc:
I have installed cygwin 1.7 in e:\cygwin1.7
After installation, there is a "strange" directory :
/E/cygwin1.7/dev/ (posix path)
E:\cygwin1.7\E\cygwin1.7\dev (win32 path)
What is the role
Andy Koppe wrote:
> Christopher Faylor:
>> rolandc:
>>> I have installed cygwin 1.7 in e:\cygwin1.7
>>> After installation, there is a "strange" directory :
>>> /E/cygwin1.7/dev/ (posix path)
>>> E:\cygwin1.7\E\cygwin1.7\dev (win32 path)
>>>
>>> What is the role of this directory?
>> It is "/dev"
Christopher Faylor:
> rolandc:
>>I have installed cygwin 1.7 in e:\cygwin1.7
>>After installation, there is a "strange" directory :
>> /E/cygwin1.7/dev/ (posix path)
>> E:\cygwin1.7\E\cygwin1.7\dev (win32 path)
>>
>>What is the role of this directory?
>
> It is "/dev".
/dev would be E:\cygwin1.7
On Tue, Mar 16, 2010 at 04:36:59PM +0100, rolandc wrote:
>Hi,
>
>I have installed cygwin 1.7 in e:\cygwin1.7
>After installation, there is a "strange" directory :
> /E/cygwin1.7/dev/ (posix path)
> E:\cygwin1.7\E\cygwin1.7\dev (win32 path)
>
>What is the role of this directory?
It is "/dev".
>I
On Tue, Mar 16, 2010 at 10:53:06AM +0100, Schmidt, Oliver wrote:
>>>Please find attached the requested information. However I had to edit
>>>it - as carefully as possible - to omit hints on the SAP-internal IT
>>>infrastructure.
>
>>Thanks. It would be nice if we could come up with some way to mak
On Mar 16 10:53, Schmidt, Oliver wrote:
> >No one is doubting that problems exist. That's why we're working
> >on them.
>
> Sorry for again being unclear. The information above was soley meant to
> complement the cygcheck output - which was produced on my XP-64 machine -
> trying to say that the
Hi Christopher,
>>Please find attached the requested information. However I had to edit
>>it - as carefully as possible - to omit hints on the SAP-internal IT
>>infrastructure.
>Thanks. It would be nice if we could come up with some way to make
>cygcheck not output sensitive information but I do
On Mon, Mar 15, 2010 at 11:01:04AM +0100, Schmidt, Oliver wrote:
>Hi Christopher,
>
>> Also, one big thing is missing here: cygcheck output [...]
>> Please send that ASAP.
>
>Please find attached the requested information. However I had to edit
>it - as carefully as possible - to omit hints on the
Hi Corinna,
> Are you absolutely sure that you can rule out BLODA effects?
I found and read http://cygwin.com/faq/faq.using.html#faq.using.bloda.
I can _NOT_ rule out those effects at all. In the opposite I know that I
run such software and I have sporadic file access problems (as described)
th
Hi Christopher,
> Is echo being run under a bash shell? From the command prompt? In a
> .bat file? Repeatedly in a loop?
I experienced it in the same scenario described in my original report:
A non-Cygwin shell calling a non-Cygwin 'gnumake -j' processing Makefiles
with rules calling Cygwin p
On Fri, Mar 12, 2010 at 04:35:48PM -0500, Christopher Faylor wrote:
>On Fri, Mar 12, 2010 at 04:28:45PM -0500, Christopher Faylor wrote:
>>...that would be useful.
>
>Also, one big thing is missing here: cygcheck output, as per
>http://cygwin.com/problems.html. I just went back to check on what OS
On Fri, Mar 12, 2010 at 04:28:45PM -0500, Christopher Faylor wrote:
>...that would be useful.
Also, one big thing is missing here: cygcheck output, as per
http://cygwin.com/problems.html. I just went back to check on what OS
was being used and I don't see that anywhere.
Please send that ASAP.
c
On Fri, Mar 12, 2010 at 04:48:14PM +0100, Schmidt, Oliver wrote:
>Hi,
>
>> Does the patch help?
>
>As the issue is sporadic it's not that easy to come up with a conclusive
>answer...
>
>I downloaded http://cygwin.com/snapshots/cygwin1-20100309.dll.bz2,
>unpacked and renamed the DLL and used it as
On 12/03/2010 17:28, Corinna Vinschen wrote:
> Hang on. This endless loop has nothing to do with Cygwin code. The
> addresses show that we're outside of Cygwin, which is in the 0x61xx
> address range. 0x7dxx is probably somewher in a Windows DLL.
That'll be WFMO, I'd bet. So it's
On Mar 12 17:27, Corinna Vinschen wrote:
> On Mar 12 16:48, Schmidt, Oliver wrote:
> > Hi,
> >
> > > Does the patch help?
> >
> > As the issue is sporadic it's not that easy to come up with a conclusive
> > answer...
> >
> > I downloaded http://cygwin.com/snapshots/cygwin1-20100309.dll.bz2,
> >
On Mar 12 16:48, Schmidt, Oliver wrote:
> Hi,
>
> > Does the patch help?
>
> As the issue is sporadic it's not that easy to come up with a conclusive
> answer...
>
> I downloaded http://cygwin.com/snapshots/cygwin1-20100309.dll.bz2,
> unpacked and renamed the DLL and used it as drop-in replacem
1 - 100 of 328 matches
Mail list logo
