Sorry to return to this old favourite. For ages (years) I have had both
/usr/bin/ and /bin/ set in my PATH and cygcheck -srv reported both as
d:\bin. I just removed the latter from the PATH and now get exactly one
report of d:\bin.
BUT cygcheck -srv still claims
Warning: There are multiple cygw
Angelo Graziosi wrote:
Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I do not know if this can help, but...
Building the above test with G95, it does not fail!
If I have understood it, I have pressed 1 ENTER
Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I do not know if this can help, but...
Building the above test with G95, it does not fail!
If I have understood it, I have pressed 1 ENTER without problem!
With
jrtayloriv wrote:
Thanks Larry, that really cleared up a lot for me. Sorry for the dumb
questions, I'm still learning my way around windows, and some of the
concepts are very foreign to me. I decided to reinstall cygwin, since I
hadn't put any work into that install yet. I had one question regard
madfran wrote:
Sorry, but the problem it is not so easy to solve.
I'd be surprised if my prescribed solution doesn't work for you. You should
try it.
If you read carrefully my original post, you realize that:
Actually, I consciously read your posting twice to make sure that you
didn't show
Dave Korn wrote:
On 03 February 2008 19:24, Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
Those of you most familiar with the Windows environment could perhaps help
here. Is this a bug in Cygwin memory manag
I flag the following for the sake of completeness.
I have the habit to build Emacs from CVS almost weekly, without big
problems.
Recently the unicode branch of Emacs was merged to trunk. Since then,
the build fails as described here [1].
I have tried with: GCC-3.4.4, 4.0.4, 4.1.2, 4.2.2, 4.2.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wei Le wrote:
| Hello,
|
| I tried to port Unix C programs to Windows VC using
| cygwin. I hope the programs can be compiled and linked
| correctly under VC. However, it does not require that
| the programs run correctly.
|
| As the first step, I tri
On 03 February 2008 19:24, Jerry DeLisle wrote:
> I have confirmed this problem on Cygwin reported here:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
> Those of you most familiar with the Windows environment could perhaps help
> here. Is this a bug in Cygwin memory management?
Ar
On 2008-02-03 19:24Z, Jerry DeLisle wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
[...]
> Is this a bug in Cygwin memory management?
According to this report (marked in bugzilla as a duplicate):
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35064
a similar problem was observed
Wei Le wrote:
> I tried to port Unix C programs to Windows VC using
> cygwin. I hope the programs can be compiled and linked
> correctly under VC. However, it does not require that
> the programs run correctly.
>
> As the first step, I tried the compilation. I added
> sys/cygwin.h to the beginni
Hello,
I tried to port Unix C programs to Windows VC using
cygwin. I hope the programs can be compiled and linked
correctly under VC. However, it does not require that
the programs run correctly.
As the first step, I tried the compilation. I added
sys/cygwin.h to the beginning of the unix C pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new release of coreutils, 6.10-1, has been promoted to current (it had
been available as experimental). This means 6.9-5 is now the previous
version.
NEWS:
=
This is a new stable upstream release. It adds a few new utilities: arch
performs a
Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I am not very familiar with the windows environment. Having patched
most of the gfortran I/O library in the last 2-3 years I can say that
we do a lot of memory alloca
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I am not very familiar with the windows environment. Having patched most of the
gfortran I/O library in the last 2-3 years I can say that we do a lot of memory
allocation for I/O.
On Lin
Hi,
Recently I installed Vista SP1 RC v.668 (Vista Vista Ultimate) with Cygwin DLL
1.5.25.
Now VIM seems to fail to write out files properly. Here are the symptoms
1. If I delete the last characters in a file and write it out from inside VIM
the last character is converted into a '\n' (newli
16 matches
Mail list logo