2013-03-15 08:00:35 by chort
I'm all for having safe defaults in security software, i.e. erring on the side of turning on protection, and leaving it up to the user to disable it if they feel it's too restrictive. Recently I had an experience with a particular anti-virus program that went well beyond this. Every time I turned me head, the program had overridden my choices.
- Comments (6)
2013-01-25 21:16:27 by chort
If you still run Ubuntu 10.04 (or another OS that can't upgrade automake past 1.11), you'll find that Yara 1.7 (last SVN version) won't build. You'll probably get something like this:
configure.ac:3: unknown warning category `no-extra-portability'
This is a quick post to show you how to get the latest 1.6 bugfixes (i.e. updated past the 1.6 tarball release) without breaking the build.
First off, I recommend installing RE2 for better performance (allegedly, I cannot confirm). Once you've done that, follow these easy steps (don't miss -r 162, that's the critical bit!):
$ rm -rf yara-project-read-only $ svn checkout -r 162 http://yara-project.googlecode.com/svn/trunk/ yara-project-read-only $ cd yara-project-read-only $ ./configure --with-re2 $ ./bootstrap.sh $ make $ sudo make install $ cd yara-python $ python setup.py build $ sudo python setup.py install $ sudo ldconfig
- Comments (0)
2010-02-02 00:03:47 by chort
It took nearly 7 hours, that's right SEVEN HOURS to build the GIMP.app port (on a 2.33GHz C2D w/4GB RAM), which inexplicably included a full build of gcc4.3. Is that reeeeeeeeeeally necessary when 4.2.1 is included with Xcode? Did those 5 hours of my life have to be wasted? WHY WAS IT YOU COULDN'T JUST UPGRADE PERL???
That's not even the best part. The best part is it got all the way to the gimp-app port itself (after going through a quarter of a day worth of dependencies), and it failed. Yes, apparently there were incompatible functions, which were found three months ago! Diffs were uploaded 3 weeks ago, and 9 days ago instructions were posted for manually applying them, yet today the port was still broken when I tried to install it. Outstanding. Really nice work guys, seriously. Three months?
In case my warning didn't come in time and you actually tried to build this abomination, you need to go here for the solution. If you're even thinking about trying to install gimp-aDON't! There, it's like I just bought you enough time to say goodbye to half a dozen more relatives on your deathbed.
- Comments (0)
2010-02-01 20:13:12 by chort
I've been a long-time user of MacPorts, from back when it was Darwin Ports and I was still using a PowerBook, in fact.
The "upgrade" for Snow Leopard is making me seriously think about looking for alternatives. Originally their site said it might be possible to use the usual selfupdate method, or to be safe do a total uninstall/reinstall. As I've been using it for years and have piles of software installed through MacPorts I didn't exactly want to blow that all away and start over, so I tried the selfupdate method.
It "mostly" worked, with several broken packages that I forced a rebuild on. Today I found one I couldn't work around: PERL. I found bug reports for it on the MacPorts site and their solution was great: rm -rf and start over. Well, that's fun! Couldn't be bothered to roll a PERL rebuild into the update script, huh?
I dutifully generated a list of all my installed packages, backed up all the existing files to an external drive, and did the rm -rf plunge...
- Comments (0)