Search results

That's weird, it seems like a package problem. I use PKGNG and I didn't experience this problem. Maybe it was a just a pkg_* hiccup. Install www/nginx again and then immediately remove it. Try # make -C /usr/ports/www/nginx reinstall clean deinstall a couple of times to see if it's removed...

Do you get a kernel panic or something? Post the kernel message or some other interesting things. Are you booting from an installed system, or a LiveCD? Pehaps a USB stick?

Well, I've tried (been using it for a few years) Slackware 13.37 + KDE, the default (complete) installation, which installs around 6 GB of programs. Just to run idle it was consuming 1 GB of RAM (yes, I disabled those background file checks). I switched to x11-wm/fluxbox -- still it was using...

Today I've had some problems with my system. Spending a few hours without X.Org have convinced me. Time to install tmux!

I suggested that port fails to build due to MAIL flag, because after I disabled it from @NuLL3rr0r and it built normally. @ShelLuser, as you suggested, I crosschecked with your results, and I seem to have found another problem with the port. # ./configure --with-ipv6...

OK, I tried with @ShelLuser's suggestion to build without patches, and there is indeed the same problem. The problem persists with @NuLL3rr0r's config flags, indicating it's not the MAIL_SSL that needs HTTP_SSL enabled, but another one -- MAIL flag itself, (it enables IMAP4/POP3/SMTP proxy...

Great job @ShelLuser for tackling this problem! @NuLL3rr0r, good to hear that you have generic settings. I just wanted to make sure, so I could exclude them as the source of the problem. It's weird though, since I can build fine with just MAIL_SSL and no HTTP_SSL enabled, but I didn't try with...

Instead of seeing out-of-the-box performance, I'd like to see both systems tuned properly, and see some tests of binary performance of both. Something like benchmarks on benchmarksgame, so memory usage comparison, user time, CPU time ... Each test would be a numerically difficult problem to...

I like the article and links that were there. I agree with @NewGuy, that the kernel itself probably cannot decrease RAM usage by 50 %.

I would recommend to browse directly from svnweb to get the latest information (these are the ports tree sources). It's more robust; it doesn't have all the functionality as others do, but you can navigate yourself pretty quickly with clickable history information (you can get all that if you...

You can report bugs here. OK, now that's weird. I enabled MAIL_SSL option, but it still builds fine. Before building, it outputs this configuration summary for me: ... checking for sha1 in system md library ... found checking for zlib library ... found creating objs/Makefile Configuration...

Oh, for me portupgrade -rf perl only updated ~100 ports. ~500 ports is like all I have installed.

This is a very good ZFS how-to, I suggest you start from there, and then compare with what you already have. Here's a link to these forums which I googled with freebsd ssd zfs. As for the Intel graphics, I think the intel driver that comes with x11/xorg works fine, but you have to enable KMS...

You can also use script(1) to do save the output of your compilation process (I have a bad experience with portupgrade -l), like # script /var/tmp/mycompile.out # portupgrade -Rf graphics/libwpg # exit and then inspect its contents with your favorite text editor. I would also suggest removing...

Then you should post a question regarding your make buildworld failure in the Base System section of the forums, specifically, Installing & Upgrading, since both question and the answer would be more suited there. Don't forget to include your /etc/make.conf and /etc/src.conf. In most cases it's...

In most such cases there are workarounds, that are not related to *WERROR, but for starters, you could try the -fpermissive flag (for more, read the gcc manpage). Perhaps you could also include which port is the one giving you the problems, since your report is pretty generic. Note, that not...

Thanks, @cpu82! That explanation was exactly what I was looking for!

I had the same question -- clang man page cannot even hold the candle to that of the gcc. However, since clang aims to be gcc-4.2 compatible, and at the same time offer tricks for newer CPUs/gcc-s (like -mssse3 for example), it should have the same flags. IMO it's safe to use gcc flags (except...

@@sossego: LOL :e hahahaha. Perhaps the squirrel demanded clothes from the opposite party, which in turn offered the squirrel to have an enlightening discussion with "The Hand". BTW, my girlfriend said he should consider auditioning for the role of "The Terminated" and not "The Terminator".

Well, you can always try setting the driver manually (just replace "vesa" with "intel", at least that's what I think the driver name is). xorg sometimes makes a wrong guess when creating the config file, and you have to fix that manually. If it doesn't work, well, then just rebuild the ports...