search for: hackaround

...xed. The configure script had trouble finding the openssl package, even though I had it installed in the standard place (/usr/local/ssl). I investigated and found that the failed test compile was caused by two nonfatal compiler warnings that memset and RAND_add were being implicitly defined. As a hackaround I inserted #include <string.h> #include <openssl/rand.h> just before #include <openssl/rsa.h> #include <openssl/bn.h> #include <openssl/sha.h> in the test program. configure succeeded, and so did the subsequent compile. I'm rather unfamiliar with the conventio...

...ed, it was trying to look up '*' for a pw server, '*' doesn't resolve so well on my DNS server. My domain name does, but it was trying to contact '*' for a pw server instead of using itself (this used to work before I tried upgrading to 3.6, FWIW)... Anyway, explicit hackaround: added: passwd server=localhost to my smb.conf. Now the PDC is smart enough to know to look up passwords on itself rather than going out and looking for '*', which "wbinfo" REALLY didn't like -- lots of "*" not found messages from wbinfo... Along with the i...

I've tried to install office 97 on Gentoo using the latest Gentoo wine version (wine-20040716). Everything goes fine until after I choose the installation directory, after a few seconds I get Office 97 Setup was not completed successfully I can't find any logs anywhere to debug the problem. Any clues?

I am trying to mix Flash and RoR (for fileupload without pagerefresh) Unfortunately the requests originating from the flashplayer do not have the right sessionid. So I tried to hackaround with reading the _session_id form the cookie and sending it together with the fileupload POST from the flashplayer to the webserver. But how can i retrieve the session based on the session_id at my controller ? I tried to add this to my action: ::ActionController::CgiRequest::DEFAULT_SESSION_OP...

...and not > modifying the current file if they're the same - thus not invalidating > everything down the chain that depends on the tablegen output (not sure if > that's actually enough to convince a build system not to rebuild other > things - but worth a shot). This is a bit of a hackaround what the build > system itself could/should be doing, but in the absence of a content based > invalidation scheme - addressing this one particularly critical point in > LLVM's build seems like it could be worth such a workaround. (this would > speed up the build for even the times w...

Say I''m firing off an at(1) or cron(1) job to do scrubs, and say I want to scrub two pools sequentially because they share one device. The first pool, BTW, is a mirror comprising of a smaller disk and a subset of a larger disk. The other pool is the remainder of the larger disk. I see no documentation mentioning how to scrub, then wait-until-completed. I''m happy to be pointed

...o the current file, and not modifying the current file if they're the same - thus not invalidating everything down the chain that depends on the tablegen output (not sure if that's actually enough to convince a build system not to rebuild other things - but worth a shot). This is a bit of a hackaround what the build system itself could/should be doing, but in the absence of a content based invalidation scheme - addressing this one particularly critical point in LLVM's build seems like it could be worth such a workaround. (this would speed up the build for even the times when tablegen's r...

Having used JUnit and Test::Unit, I''m quite used to having the ability to insert a failure message, which helps when tests fail. For instance, the example RSpec that is generated for a model class specifies that the model class is valid. Assuming this were supposed to be true, and it failed, I''ve now got to duplicate the code in the test in order to find out why it

It would be better, because a debug tablegen is slower than an optimized tablegen, but it's still slow and it doesn't address the problem that tablegen runs *at all* when it doesn't really need to. I think if tablegen wasn't running all the time we could incremental builds down from 15 minutes (and that's on my really powerful machine) to under 5, which seemed like a big

...o the current file, and not modifying the current file if they're the same - thus not invalidating everything down the chain that depends on the tablegen output (not sure if that's actually enough to convince a build system not to rebuild other things - but worth a shot). This is a bit of a hackaround what the build system itself could/should be doing, but in the absence of a content based invalidation scheme - addressing this one particularly critical point in LLVM's build seems like it could be worth such a workaround. (this would speed up the build for even the times when tablegen's r...

...o the current file, and not modifying the current file if they're the same - thus not invalidating everything down the chain that depends on the tablegen output (not sure if that's actually enough to convince a build system not to rebuild other things - but worth a shot). This is a bit of a hackaround what the build system itself could/should be doing, but in the absence of a content based invalidation scheme - addressing this one particularly critical point in LLVM's build seems like it could be worth such a workaround. (this would speed up the build for even the times when tablegen's r...