Re: _GLIBCXX_USE_C99 not working?
Christian Franke wrote:
> Defining _GLIBCXX_USE_C99 does not work with current Cygwin C++ includes.
>
> Testcase:
>
> #define _GLIBCXX_USE_C99 1 // need std::llabs()
>
> #include
>
> long long f(long long x)
> {
>return std::llabs(x);
> }
>
>
> Compile fails with:
>
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/cstdlib:181:
> error: `::strtold' has not been declared
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/cstdlib:200:
> error: `__gnu_cxx::strtold' has not been declared
>
>
> The function strtold() does actually not exist in stdlib.h
> and the corresponding _GLIBCXX_HAVE_STRTOLD in
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/i686-pc-cygwin/bits/c++config.h
>
> is not set.
>
> But "using ::strtold" exists in the "#if _GLIBCXX_USE_C99" part of
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/cstdlib
>
> Workaround: delete the two "using ::strtold" lines from cstdlib.
>
> Christian
Look into the cstdlib header. You will find that llabs(long long) and
abs(long long) are in the __gnu_cxx namespace there. It is because long
long is not C++ standard type.
--
Vaclav Haisman
signature.asc
Description: OpenPGP digital signature
Re: _GLIBCXX_USE_C99 not working?
Václav Haisman wrote:
>> ...
>>
> Look into the cstdlib header. You will find that llabs(long long) and
> abs(long long) are in the __gnu_cxx namespace there. It is because
long
> long is not C++ standard type.
>
Yes - but abs() and llabs() is also included into std namespace a few
lines later.
The problem is that ::strtold() is also included, but does not exist in
Cygwin's stdlib.h:
cstdlib:
...
#include "stdlib.h"
...
#if _GLIBCXX_USE_C99
namespace __gnu_cxx
{
...
inline long long
llabs(long long __x) { return __x >= 0 ? __x : -__x; }
...
using ::strtold;
}
namespace std
{
...
using __gnu_cxx::llabs;
...
using __gnu_cxx::strtold;
}
#endif
The llabs() in my testcase was only intended as a real-world (found
in ddrescue) usage example.
The problem occurs also if cstdlib is simply included, but not used:
#define _GLIBCXX_USE_C99 1
#include
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/cstdlib:181:
error: `::strtold' has not been declared
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/cstdlib:200:
error: `__gnu_cxx::strtold' has not been declared
This can be fixed by adding some dummy declaration of strtold:
#define _GLIBCXX_USE_C99 1
void strtold();
#include
Christian
--
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/
Building problem with PIDGIN IM- Using Cygwin...Please help
Hi, I am building pidgin using the Build pidgin instructions from http://developer.pidgin.im/wiki/BuildingWinPidgin using Cygwin and I got an error during the process.. OS - Windows Cygwin ---> saved in local D: drive I also try the process of in the source The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. ---> I got an error in this line like this: 79: undefined reference to `_g_free' XMLNode.o: In function `XS_Purple__XMLNode_to_str': /cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plugins/perl/common/XMLNode.c:2 92: undefined reference to `_purple_perl_ref_object' /cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plugins/perl/common/XMLNode.c:2 96: undefined reference to `_xmlnode_to_str' /cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plugins/perl/common/XMLNode.c:3 03: undefined reference to `_g_free' Creating library file: libPurple.dll.a collect2: ld returned 1 exit status perlld: *** system() failed to execute gcc -shared -o Purple.dll -Wl,--out-implib=libPurple.dll.a -Wl,--export-all-sym bols -Wl,--enable-auto-import -Wl,--stack,8388608 -Wl,--enable-auto-image-base \ -s -L/usr/local/lib Account.o AccountOpts.o BuddyIcon.o BuddyList.o Cipher.o Cmd s.o Connection.o Conversation.o Core.o Debug.o FT.o ImgStore.o Log.o Network.o N otify.o Plugin.o PluginPref.o Pounce.o Prefs.o Privacy.o Proxy.o Prpl.o Purple.o Request.o Roomlist.o SSLConn.o SavedStatuses.o Server.o Signal.o Sound.o Status .o Stringref.o Util.o XMLNode.o /usr/lib/perl5/5.8/cygwin/CORE/libperl.dll.a make[6]: *** [blib/arch/auto/Purple/Purple.dll] Error 2 make[6]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plu gins/perl/common' make[5]: *** [all-local] Error 2 make[5]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plu gins/perl' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple/plu gins' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple' make[2]: *** [all] Error 2 make[2]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0/libpurple' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/d/devpmt/pidgin/pidgin-2.0.0' make: *** [all] Error 2 I find it hard to solve this problem... Please help me and thanks in advance... Thanks, Skat -- View this message in context: http://www.nabble.com/Building-problem-with-PIDGIN-IM--Using-Cygwin...Please-help-tf3776529.html#a10678771 Sent from the Cygwin Users mailing list archive at Nabble.com. -- 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/
Re: DualCores and Current Cygwin problems
Joseph Kowalski wrote: Linda Walsh wrote: Hi, I don't claim to know what is going on, but I'm using a dual-core system and haven't noticed the problems you are having, but my processors are Intel Dual Core. That shouldn't make a difference I wouldn't think. Joseph Kowalski wrote: 1) Windows XP, fully updated; 2) Visual Studio .NET Professional (2003) 3) Microsoft Platform SDK (2004 - *not* R2) 4) Microsoft DirectX SDK (Summer 2004); 5) Sun Java 6 SDK (1.6.0_01) 6) Cygwin (current). That's it. No additional software components. None. What do you mean by "components"? Do you mean if you go into the "Add/Remove Programs", the only items I would see would be the MS SDK, XP "Patches", DirectX SDK, and Sun Java? If you tell it to hide "updates", I'd guess you only have 3 items on your Software list? the MS-Platform SDK, the DirectX SDK and the Sun Java SDK? (Cygwin wouldn't be listed). That's a pretty short list, but I assume it is a test machine that's off the main net and is only for testing? Well, it depends upon how you look at it. Its probably best viewed as a build machine for building the Sun Java SDK, with emphasis on OpenJDK. Its a test machine in the sense that I'm starting with a bare machine to "test" the instructions for setting up a build environment for the JavaSDK. That's why its a short list. The goal is for it to be the minimal list to build with. I'm 2500 miles from this machine at the moment, so I'm not exactly sure what you would see in add/remove programs. I suspect your list is correct, but you'ld also see Virtual Studio (which you probably missed due to the missing above). "At the moment?" How are you logging into the machine if you are 2500 miles away? Is it on the net? Yet you have no firewall other than XP's builtin, and no other security software? Could it be possible the machine has been hacked? No, I haven't tried this, and I'm not sure exactly how I would do this. --- When I do it interactively at console, I run process explorer (a GUI). Hey, just noticed, it's in the task manager too, on the processes page, rightclick and make sure only 1 cpu is checked on your "parent" process -- i.e. if you run from 'bash', setting the affinity on bash will also propagate it to the children. In the response after yours, by Oliver Walsh, he mentions another tool that modifies "exe"s to limit them to a particular cpu -- that's another possibility. I am down rev. (one rev.) from the current BIOS provided by ASUS, but the newer rev only claims to expand CPU support. --- Could that provide better support for multi-core cpu's? Dunno. But maybe making sure you have latest drivers from manufacturers even though they may not be coming with your standard WinXP install would help? I can check the rev. on the nVidia site, and if newer, will update and report back. Linda That all said, there are a lot of threads here recently reporting this failure symptom. Some of the reports tend to indicate that the problem only appeared when Cygwin was updated (then again, how many of us visit Windows Update and forget to mention that). I tend not to think its a chip driver revision problem. Urg...I usually remember visits to win-update...they are usually painful. Takes hours for them to download as is constantly trying to go around my proxy and go direct with each file -- after taking forever and timing out on several servers it eventually gives up and downloads it through the proxy, but it slows down each file download to a few to several minutes... Seems to be a new feature with SP2didn't have the problem in SP1 for some reason, but MS mucked heavily with SP2's network stack and messed up more than one network related program. linda -- 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/
RE: _GLIBCXX_USE_C99 not working?
On 17 May 2007 21:32, Christian Franke wrote: > Defining _GLIBCXX_USE_C99 does not work with current Cygwin C++ includes. > > Testcase: > > #define _GLIBCXX_USE_C99 1 // need std::llabs() Can you point me at any documentation that says this is a valid thing to do? AFAICT that's an internal symbol in the '_' namespace that user code has no business messing around with. Cygwin is not a glibc program so telling libstdc that it is seems inherently bogus to me. /artimi/software/firmware $ grep -wB1 _GLIBCXX_USE_C99 /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/i686-pc-cygwin/bits/c++config.h // Define if C99 features such as lldiv_t, llabs, lldiv should be exposed. /* #undef _GLIBCXX_USE_C99 */ As you see, it is part of the internal configuration, generated by autoconf or some similar process at the time the library is compiled and installed. http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/c++config_8h.html "This is an internal header file, included by other library headers. You should not attempt to use it directly." If you want this to work, I guess we shoult implement strtold in newlib, or patch libstdc for finer granularity in what it assumes _GLIBCXX_USE_C99 implies is available. cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: _GLIBCXX_USE_C99 not working?
Dave Korn wrote: > ... > Can you point me at any documentation that says this is a valid thing to do? > AFAICT that's an internal symbol in the '_' namespace that user code has no > business messing around with. Cygwin is not a glibc program so telling > libstdc that it is seems inherently bogus to me. > That's correct. I missed that the symbol is part of c++config.h, sorry for the noise. Christian -- 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/
Cygwin Easy: let you work with Cygwin without any installation
Hi to all, I create Cygwin Easy, an autorun disk that let you work easily and quickly with Cygwin environment in a Windows computer without install anything on your hard disk. Visit the project site for more infos: http://www.cygwineasy.tk Here you can find also a video with Cygwin Easy running on Windows Vista! (I try to upload this video to google video but the quality degradated and the commands written to the shells weren't readable. If someone know an online video service without quality loss please let me know) The ISO image downloadable from main site includes 448 software packages (X is one of these), shortly with Cygwin Easy you can do everything you want. Howewer you can create your own ISO or USB disk (development of Cygwin Easy, for example, was made in my USB hard disk) following the instructions that you can found here: http://code.google.com/p/cygwin-easy/wiki/CreateYourCygwinEasyDisk Cygwin Easy includes also the console project (http://www.sourceforge.net/projects/console): thanks to this you can switch to more cygwin shells with tabs (keyboard shorcuts are similar to Linux: ALT-Fx to switch to x console). I point my attention also on computers where Cygwin is already installed, in this case after you use Cygwin Easy the system return back to the previous environment. Read the documentation on the project site for more informations and features. If you have problem with Cygwin Easy or you want to give me some suggestions please post in the project discussion group: http://groups.google.com/group/cygwin-easy I would to thank fergus (http://www.cygwin.com/ml/cygwin/2003-07/msg01117.html) and Dick Repasky (http://xlivecd.indiana.edu), without their works Cygwin Easy wasn't possible. I hope you find this project useful, try it and let me know your impressions. Use Cygwin everywhere with Cygwin Easy! whitone PS: I create Cygwin Easy because Windows is the only OS without an UNIX-like shell (PowerShell has similar commands but different syntax and it's a bit slow because it's .NET based), an indispensable system component for me that I work with Linux, Mac OS X, Haiku and Solaris. Thanks to Cygwin Easy I can use this shell in every Windows installation I find. -- 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/
Re: _GLIBCXX_USE_C99 not working?
Dave Korn wrote: > Can you point me at any documentation that says this is a valid thing to do? > AFAICT that's an internal symbol in the '_' namespace that user code has no > business messing around with. Cygwin is not a glibc program so telling > libstdc that it is seems inherently bogus to me. You're right that it's an internal gcc symbol, but the "_GLIBCXX" preprocessor namespace belongs/refers to libstdc++ not glibc, so in this case it's not necessarily got anything to do with glibc, rather just indicating target libc C99 support is available to be used by libstdc++. Brian -- 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/
Re: ssh-add cannot connect to authentication agent
Haven't been able to nail it down that specific. I ended up modifying ssh-agent to run as a service under the SYSTEM account rather than as a background process under the user-account. It worked fine that way, even with McAfee but like I said, it required a modification of ssh-agent itself. Tim Len Giambrone wrote: I'm using XP. I disabled everything I could in McAfee, but still no luck. Did you figure out what in McAfee was causing the problem in W2K? -Len Tim Beuman <[EMAIL PROTECTED]> writes: I had the same problem on W2K. Seemed to be caused by McAfee. No problems with McAfee on WXP though. Tim Len Giambrone wrote: The agent starts correctly, but I can't get ssh-add to give me anything other than: Could not open a connection to your authentication agent. I'm running the latest Cygwin/packages. The socket is where it's supposed to be, the env variables are set. I've tried using ssh-agent -a and putting the socket in a different place in case it's a permissions issue, but no luck. I have it working on my laptop. A combination of comparing an strace of the failing and working ssh-add and a previous post of Corinna's leads me to believe the problem is here: 67 84289 [main] ssh-add 4264 cygwin_select: 4, 0x0, 0x22C870, 0x22C850, 0x0 117 84406 [main] ssh-add 4264 dtable::select_write: fd 3 49 84455 [main] ssh-add 4264 dtable::select_except: fd 3 47 84502 [main] ssh-add 4264 cygwin_select: to NULL, ms 51 84553 [main] ssh-add 4264 cygwin_select: sel.always_ready 0 115 84668 [main] ssh-add 4264 start_thread_socket: Handle 0x6D0 54 84722 [main] ssh-add 4264 start_thread_socket: Added to writefds 47 84769 [main] ssh-add 4264 start_thread_socket: Added to exceptfds 835 85604 [main] ssh-add 4264 start_thread_socket: opened new socket 0x6B8 70 85674 [main] ssh-add 4264 start_thread_socket: exitsock 0x6B8 54 85728 [main] ssh-add 4264 start_thread_socket: stuff_start 0x22C7D4 452 86180 [select_socket] ssh-add 4264 cygthread::stub: thread 'select_socke t', id 0x16B8, stack_ptr 0x1900CDC0 79 86259 [select_socket] ssh-add 4264 thread_socket: stuff_start 0x676F14 5405 91664 [main] ssh-add 4264 select_stuff::wait: m 2, ms 4294967295 993673 1085337 [select_socket] ssh-add 4264 thread_socket: Win32 select returned 1 85 1085422 [select_socket] ssh-add 4264 thread_socket: s 0x673ED0, testing fd 3 () 63 1085485 [select_socket] ssh-add 4264 thread_socket: except_ready *** In the working strace, this is "write_ready" *** 64 1085549 [main] ssh-add 4264 select_stuff::wait: woke up. wait_ret 1. ver ifying 51 1085600 [main] ssh-add 4264 select_stuff::wait: gotone 1 45 1085645 [main] ssh-add 4264 select_stuff::wait: returning 0 42 1085687 [main] ssh-add 4264 select_stuff::cleanup: calling cleanup routine s 44 1085731 [main] ssh-add 4264 socket_cleanup: si 0x673F00 si->thread 0x61104 F30 73 1085804 [main] ssh-add 4264 socket_cleanup: sent a byte to exitsock 0x6B8, res 1 86 1085890 [main] ssh-add 4264 socket_cleanup: reading a byte from exitsock 0 x6B8 58 1085948 [main] ssh-add 4264 socket_cleanup: recv returned 1 91 1086039 [main] ssh-add 4264 socket_cleanup: returning 50 1086089 [main] ssh-add 4264 peek_socket: considering handle 0x6D0 43 1086132 [main] ssh-add 4264 peek_socket: adding write fd_set , fd 3 54 1086186 [main] ssh-add 4264 peek_socket: WINSOCK_SELECT returned 0 43 1086229 [main] ssh-add 4264 set_bits: me 0x673ED0, testing fd 3 () 44 1086273 [main] ssh-add 4264 set_bits: ready 1 44 1086317 [main] ssh-add 4264 select_stuff::poll: returning 1 43 1086360 [main] ssh-add 4264 select_stuff::cleanup: calling cleanup routine s 43 1086403 [main] ssh-add 4264 select_stuff::~select_stuff: deleting select r ecords 96 1086499 [main] ssh-add 4264 cygwin_getsockopt: WinSock SO_ERROR = 10061 44 1086543 [main] ssh-add 4264 cygwin_getsockopt: 0 = getsockopt (3, 65535, 0 x1007, 0x22C8B4, 0x22C8B8) 46 1086589 [main] ssh-add 4264 __set_errno: int cygwin_connect(int, const soc kaddr*, socklen_t):806 val 111 According to Corinna, Winsock 1006 is connection refused. As she suggests in that post, I've disabled the firewall to see if that fixes the problem, but no luck. I've uninstalled and reinstalled ssh several times and of course rebooted several times. Still no luck. At this point, the only other thing I can think of to try is reinstalling Cygwin from scratch, but I'd like to avoid that if I can. Any suggestions on what else to try/look for? Cygcheck output follows. Cygwin Package Information Package VersionStatus _update-info-dir00517-1OK alternatives1.3.29a-1 OK apache 1.3.33-2 OK ash 20040127-3 OK base-files 3.7-1 OK base-passwd 2.2-1 OK bas
Re: ssh-add cannot connect to authentication agent
From: Tim Beuman Subject: Re: ssh-add cannot connect to authentication
agent
Date: Fri, 18 May 2007 09:11:00 -0700
Haven't been able to nail it down that specific. I ended up modifying
ssh-agent to run as a service under the SYSTEM account rather than as a
background process under the user-account. It worked fine that way, even
with McAfee but like I said, it required a modification of ssh-agent
itself.
Tim
Hi All...
I've been using ssh-agent as a service for years, with no modifications. I
started doing it because keychain was slow to start up and lost the keys on
logout, whereas ssh-agent as a service keeps the keys until a reboot.
Attached are two scripts secret-agent-service and
secret-agent-service-install are the scripts used for running ssh-agent as a
service (one for each user that wants it). The sendchenv makes sure that the
environment variables are up to date (if the service starts after the user
logs in...have to love Microsoft).
HTH,
...Karl
_
Like the way Microsoft Office Outlook works? Youll love Windows Live
Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507
#!/bin/bash
# Launch the ssh-agent from a service so it survives logoff.
# When the service stops, kill the ssh-agent.
trap "ssh-agent -k;
exit 0" TERM
# Clean up old files that may be left behind after a crash.
# The file permissions make this safe to do in a multi-user
# environment, but "/tmp" must be local to this host.
rm -rf /tmp/ssh-*
# Launch the ssh-agent.
eval $(ssh-agent)
# Provide the ssh-agent socket ID via the registry and broadcast
# the change in case the user is logged before we finish.
# Do not provide the ssh-agent PID to minimize the risk of
# accidentally killing the ssh-agent.
regtool -s set /HKEY_CURRENT_USER/Environment/SSH_AUTH_SOCK $SSH_AUTH_SOCK
regtool remove /HKEY_CURRENT_USER/Environment/SSH_AGENT_PID
sendchenv
# Wait quietly until the service is stopped.
while true; do
sleep 24h &
wait
done
#!/bin/bash
# secret-agent-service-install service-name user-name
if [ "~$1" = "~" ]; then
echo A service name is required.
exit 1
fi
if [ "~$2" = "~" ]; then
echo A user name is required.
exit 1
fi
echo Uninstalling the secret-agent service, $1.
cygrunsrv --remove $1
echo Adding the \"Log on as a Service\" right for $2.
editrights -a SeServiceLogonRight -u $2
echo Installing the secret-agent service, $1.
cygrunsrv --install $1 \
--args '/bin/secret-agent-service' \
--disp "Secret Agent $2" \
--desc "Creates an ssh-agent process for $2." \
--path '/bin/bash' \
--shutdown \
--user "$2"
echo Starting the secret-agent service, $1.
cygrunsrv --start $1
// Notify all windows that environment variables may have changed.
#include
int main()
{
DWORD dwReturnValue;
if (SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,
(LPARAM) "Environment", SMTO_ABORTIFHUNG, 5000, &dwReturnValue))
return 0;
else
return 1;
}
--
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/
Re: DualCores and Current Cygwin problems
Linda Walsh wrote: I'm 2500 miles from this machine at the moment, so I'm not exactly sure what you would see in add/remove programs. I suspect your list is correct, but you'ld also see Virtual Studio (which you probably missed due to the missing above). "At the moment?" How are you logging into the machine if you are 2500 miles away? Is it on the net? Yet you have no firewall other than XP's builtin, and no other security software? Could it be possible the machine has been hacked? I started this tread from my home/office in Hawaii. I'm in the SF Bay Area this week on business. I'm not logging in to the machine this week - I said I'd run the suggested experments when I got back to being in proximity to the machine. This week I'm just responding to questions on the thread. Its *very* unlikely the machine has been compromised. It's not discoverable from outside my firewall (on a router), I don't read/download mail on it and no other software has been install on it. Its a specific use machine - building Sun Java using the Cygwin tools. It also only had a couple of days to be compromised from a full, clean, install to the problem report. No, I haven't tried this, and I'm not sure exactly how I would do this. --- When I do it interactively at console, I run process explorer (a GUI). Hey, just noticed, it's in the task manager too, on the processes page, rightclick and make sure only 1 cpu is checked on your "parent" process -- i.e. if you run from 'bash', setting the affinity on bash will also propagate it to the children. I missed the "propagation" aspect. Yes, the entire build is started from the bash command line. This may not be the most interesting experiment because this means that everything under the "make" will have affinity to a single processor, including the Visual Studio tools. All that will be running on the other processor will be background system processes (of which Windows has more than a few). This does make the experiment quite easy. I'll report back results when I can. - Joseph Kowalski -- 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/
