I'm cross-posting this to cygwin-xfree@cygwin.com, and cygwin@cygwin.com
because, although it appears to be X-related, the root cause may turn out
not to be. Here's what's up...
I'm attempting to build an X-client from source. I've done it many times
before without a hitch, although the last
I'm having a problem building an app which #includes . It
depends on some #defines which are inside a #if (_WIN32_WINNT >= 0x0403 ..
#endif clause. (to be specific, it needs the typedef for LPINPUT in
winuser.h). My build environment is Windows 2000 SP4, and a quick test
tells me that _WIN32
2 separate questions about customizing the list of mirror URLs in the cygwin
setup.exe program:
1) When adding a custom URL, what is the correct syntax to describe the path
to the cygwin pacakge directory? For instance, on an FTP accessible server I
have a directory in my home directory called
Do you run a CPU-soaking background program such as SETI@home,
Folding@home (the protein folding experiment) or fightAIDS@home
(the AIDS drug discovery program)?
If so, you're seeing the result of the changes to how Cygin accesses
pipes in 1.3.18.
You hit the nail on the head!!
I'm running SETI
Update. I've further observed that while running whoami at the command-line
returns a result immediately, running it inside a pair of back-tics "`"
shows the blocking behavior. For instance, if I do this:
$ whoami
I get a result immediately.
However, if I do this:
$ echo `whoami`
It takes
I recently ran Cygwin setup and installed lots of updates. However, ever
since, I noticed that starting a new shell takes a relatively long time
(we're talking 10 seconds or so between typing "bash" and getting a prompt -
it might not sound like a lot, but try running make on something of moder
I got to playing around with Windows 2000 Task Manager the other day and
discovered that you can change the priority of a running task. This led me
to discover that you can specify the priority of a task when you launch it
by way of the windows start command using one of the following options:
I'm looking for a convenient place to cross-compile a Linux Kernel
targetting an x86 platform. Is this something I can do under Cygwin, or am
I asking for trouble? While I've compiled the Linux kernel before, I've
never cross-compiled it on a different platform.
_
I downloaded the source for the Cygwin setup program (via setup), ran
configure, and then make. All went smoothly until this:
Making all in libgetopt++
make[2]: Entering directory `/usr/src/setup-0/libgetopt++'
source='src/GetOption.cc' object='src/GetOption.lo' libtool=yes \
depfile='src/.deps
When I run the Cygwin setup program, the second screen titled "Choose a
download source" has 3 radio buttons. More often than not I select the one
labeled "Install from Local Directory". Unfortunately, setup does not
"remember" that selection the next time I run it, always defaulting to
"Inst
10 matches
Mail list logo