Jose Arcangel Salazar Delgado wrote:
> I have a problem, i'm using gcc included in cygwin to compile a
> ncurses aplication. The problem its that I need the installation of
> cygwin to run the application. Its any way to compile a .exe that dont
> need all the cygwin install (at least only a few l
Hi!
I have a problem, i'm using gcc included in cygwin to compile a
ncurses aplication. The problem its that I need the installation of
cygwin to run the application. Its any way to compile a .exe that dont
need all the cygwin install (at least only a few libs) and run in
windows.
thanks for
Thanks
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Thank You
Lou Rosas
--- Larry Hall
<[EMAIL PROTECTED]> wrote:
> At 05:08 PM 11/27/2004, you wrote:
> >I tried Three times to install Cygwin on my
> computer.
> >I downloaded all the packages from the sight:
> except
> >the databases, which I set to default. I then
> click
> >the setup icon to s
At 05:08 PM 11/27/2004, you wrote:
>I tried Three times to install Cygwin on my computer.
>I downloaded all the packages from the sight: except
>the databases, which I set to default. I then click
>the setup icon to start the install. I select Install
>from local directory and chose where I want
I tried Three times to install Cygwin on my computer.
I downloaded all the packages from the sight: except
the databases, which I set to default. I then click
the setup icon to start the install. I select Install
from local directory and chose where I want to
install. Everything goes along just
On Sat, Nov 27, 2004 at 07:48:03PM +0100, Roberto Bagnara wrote:
>I am wondering why this header file and the corresponding C99
>functionality appears to be missing from cygwin.
>Does anyone know?
99.9% of the time, the answer to "Why doesn't X exist in cygwin?" is "No
one has implemented/contribu
On Sat, Nov 27, 2004 at 01:32:00PM -0500, Igor Pechtchanski wrote:
>>In my case, I provide an option for a terminal program what device
>>should be used to open the file. I don't want to restrict what devices
>>are or are not allowed, except by using function calls to the Posix API
>>to determine
I am wondering why this header file and the corresponding C99
functionality appears to be missing from cygwin.
Does anyone know?
Cheers,
Roberto
P.S. I know fenv.h is available in mingw, but this does not
help me as I cannot then link with libmingwex.
--
Prof. Roberto Bagnara
Computer Scie
On Sat, 27 Nov 2004, Jason Curl wrote:
> Hello,
>
> I have a general question for the developers of cygwin.
>
> When I open the file "\\.\COM37" this is not opened by cygwin as a
> serial port, but rather as a file. The reasoning (that I'm not
> disputing) is cygwin should have more of a posix/uni
news.gosonic.com wrote:
Hi,
I set the so_linger to let the socket to linger 60 seconds before I use
close() to close the socket. The linger never happened, why? What is the
proper why to set up the test?
Could you please send a simple compilable testcase?
Gerrit
--
=^..^=
--
Unsubscribe info:
On Sat, 27 Nov 2004, Jason Curl wrote:
> Igor Pechtchanski wrote:
> > > > First off, you could have actually removed the offending entries
> > > > from the PATH using something like
> > > >
> > > > OFFENDING_ENTRY="/cygdrive/c/ClearCase/bin"
> > > > PATH="`echo "$PATH" | sed "s#:$OFFENDING_ENTRY##
Hello,
I have a general question for the developers of cygwin.
When I open the file "\\.\COM37" this is not opened by cygwin as a
serial port, but rather as a file. The reasoning (that I'm not
disputing) is cygwin should have more of a posix/unix flavour. And so
specific functionality to treat t
With some help, I used the following configuration:
./configure --enable-languages=vhdl --enable-nls=no
I used gcc-ada and gcc-core 3.4.1 from
http://sunsite.utk.edu/ftp/pub/cygwin/release/gcc/gcc-ada/?M=D
and was able to build it okay on cygwin.
The asmple test hello.vhdl
compiles okay
ghdl -a 1
postgresql-cygwin is working fine. See the testfarm.
Just cygwin itself, cygserver - the IPC daemon - has problems.
On msgctl(IPC_INFO) the internal msg buffer struct msqid_ds *buf is
allocated at a non-writable area, IsBadWritePtr() fails. I suspect it's
a new gcc-3.4 feature, but haven't found
Igor Pechtchanski wrote:
First off, you could have actually removed the offending entries from the
PATH using something like
OFFENDING_ENTRY="/cygdrive/c/ClearCase/bin"
PATH="`echo "$PATH" | sed "s#:$OFFENDING_ENTRY##"`"
Alternatively, if you want to translate any Win32 path to a Cygwin
(POSIX) pat
16 matches
Mail list logo