On Tue, Aug 21, 2007 at 10:29:29AM +0100, Pedro Alves wrote:
>Attached cygcheck output
Thanks. That shows that you are using FAT32 drives. Corinna was kind
enough to try mutt with FAT drives for me and was able to duplicate the
problem. mutt is trying to do some trickery with link that doesn't
On Wed, 22 Aug 2007, point wrote:
> Hello,
>
> this is my problem: I used Windows XP and would like to install the
> graph visualization software CaGe, obtainable at
>
> http://www.math.uni-bielefeld.de/~CaGe/
>
> which is built in, and requires Java; the system requirements include
> the followin
On Wed, 22 Aug 2007 10:30:15 Corinna Vinschen wrote:
>
> Second, even if a FS appears case-insensitive, it isn't necessarily so.
> NTFS is case-sensitive. The case-insensitivity is actually handled by
> the Windows kernel. Basically, a flag in calls to functions taking a
> filename as parameter i
Hi,
I'm in the process of updating my cross-compilation
environment from cygwin-1.5.12 to cygwin-1.5.24, mainly
because we have had code generation problems with
gcc-3.3.3-3 from the former.
However, I get the following message
No support for this host/target combination
from gcc-3.4.4/libs
Hello,
this is my problem: I used Windows XP and would like to install the graph
visualization software CaGe, obtainable at
http://www.math.uni-bielefeld.de/~CaGe/
which is built in, and requires Java; the system requirements include
the following passage:
a Java installation
(with Java Nativ
Corinna Vinschen schrieb:
So, in the Linux/FAT example we have a case-sensitive OS with a
case-insensitive FS, with Win32/NTFS (Cygwin/NTFS) we have a
case-insensitive OS with a case-sensitive FS. While the NT kernel can
return information about the case-sensitivity of the underlying FS (***)
(*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please keep replies on list; redirected. http://cygwin.com/acronyms/#PPIOSPE
Please don't top-post on lists; reformatted.
http://cygwin.com/acronyms/#TOFU
According to Jam One on 8/22/2007 8:25 AM:
I have downloaded the recent copy of cygwin an
Hello,
I've been using Cygwin for quite some time now for a few different
packages. The one that interests me the most, however, is Octave and it
is extremely important to my day to day activities at work.
Unfortunately, Cygwin has not updated Octave in quite some time. I was
wondering whethe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forwarding this conversation from the cygwin lists, as it provides some
useful information on the recent topic of case insensitivity.
According to Corinna Vinschen on 8/22/2007 2:30 AM:
> On Aug 21 15:47, Eric Blake wrote:
>> According to Reini Urban
On 22 August 2007 13:33, Enna wrote:
> Thanks for all the replies, i still don't know what the problem was, except
> that recompiling the program file helped... if any of you can make sense of
> that, please let me know.
So, the file must have got damaged or broken somehow. However, it's prett
Thanks for all the replies, i still don't know what the problem was, except
that recompiling the program file helped... if any of you can make sense of
that, please let me know.
Enna wrote:
>
> I have the following problem: I would like to execute a C program from the
> cygwin console. This pro
On 22 August 2007 12:48, Enna wrote:
> I have the following problem: I would like to execute a C program from the
> cygwin console. This program is supposed to get its input from another file,
> so what I type into the cygwin console is
>
> /path to the program/programname
> This worked fine yes
Hi,
Thanks a lot, "filename" is present and I am giving the full path anyway,
anything else doesn't work on my computer.
I found that recompiling of the program actually helped.
Strange... but thanks anyway.
Patil, Ashwin Channabasavaraj wrote:
>
> Hi,
> Check whether "filename" is present in y
Hi,
Check whether "filename" is present in you present working directory.
Alternatively, give the absolute path to the file "filename" when you
run your program.
-Ashwin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Enna
Sent: Wednesday, August 22, 2007
Hi,
Enna wrote:
/path to the program/programname
check for spaces in the names and insert a space behind the program name.
Erich
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/
I have the following problem: I would like to execute a C program from the
cygwin console. This program is supposed to get its input from another file,
so what I type into the cygwin console is
/path to the program/programnamehttp://www.nabble.com/executing-C-program-in-cygwin-tf438.html#a12
On Aug 22 10:18, Thorsten Kampe wrote:
> [latest Cygwin snapshot]
>
> I noticed that I have errors when running simple pipes in a cmd shell
> like "echo 12543 | grep 5":
>
> grep: (standard input): Bad file descriptor"
>
> The same command works in bash/zsh.
>
> Any hints?
http://sourceware.o
[latest Cygwin snapshot]
I noticed that I have errors when running simple pipes in a cmd shell
like "echo 12543 | grep 5":
grep: (standard input): Bad file descriptor"
The same command works in bash/zsh.
Any hints?
Thorsten
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On Aug 21 15:47, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Reini Urban on 8/21/2007 3:26 PM:
> >> This is a minor patch release. It attempts to add some
> >> case-insensitivity
> >> smarts to mv, cp, and install. In other words, 'mv a A' should now caus
> > So the effect seems to be the same as before: As if a
> different clock
> > were used when calculating the time stamps for creating a file, or
> > for modifying it.
>
> Hmm, could it be that your files reside on a remote mount,
> and that NFS is
> reflecting the time of the remote machine (i
Angelo Graziosi wrote:
> configure: WARNING: fixed-point is not supported for this target
>^
> checking whether make sets $(MAKE)... yes
> ...
>
> This warning was absent with the bootstrap I did 20070819 trunk-127626.
That's becaus
With GFortran 4.3.0-20070821 trunk-127680 there is this warning:
[ -f stage_final ] || echo stage3 > stage_final
make[1]: Entering directory `/tmp/gcc/build'
make[2]: Entering directory `/tmp/gcc/build'
make[2]: Leaving directory `/tmp/gcc/build'
make[2]: Entering directory `/tmp/gcc/build'
Conf
22 matches
Mail list logo