Hot answers tagged freebsd
Since FreeBSD 10 Clang is the new default compiler. So you could try to compiler your code with Clang or you need to install a GCC version like you did. But before the switch to Clang, FreeBSD used version 4.2 of GCC and the binary of this GCC was /usr/bin/gcc, so the newer ports of GCC needed to name there binary differently. So all GCC ports have a ...
Is your question whether LibreSSL is intended to be a drop-in replacement for OpenSSL? If so, yes. This is explicitly the intention stated by the developers. One point of the current release is to ensure that goal by letting the people responsible for binary packages and source repositories test it. There are a few problems still, but most of them are minor: ...
if you have spare memory increasing memory not working you should change the swappiness parameter. it tells the kernel how often use non physical memory (swap). check swappiness value: cat /proc/sys/vm/swappiness change the swappiness value temporary (lost on reboot) to value 10 (good value that decreases swap usage) sudo sysctl vm.swappiness=10 if you ...
It's caused by the process exiting between top getting the process list and top trying to get info on that particular process. It's more common on a very busy box but generally safe to ignore. You might consider it a bug, you might not.
No matter the fancy name used here, both are solutions to a specific problem: A better segregation solution than classic Unix chroot. Operating system-level virtualization, containers, zones, or even "chroot with steriods" are names or commercial titles that defines the same concept of userspace separation, but with different features. Chroot was introduced ...
ZFS currently has a 255 bytes limit on names. If you decide to use UTF-16 names, you will get a limit of 127 characters. UTF-8, OTOH might encode japanese/korean in 3-byte character, limiting you even further (255/3 = 85). I'm not aware of other concerns, aside from slower indexing of UTF-8 3-byte char strings compared to UTF-16 2-byte char strings. So - if ...
From what I see they have not changed the library and binary names. So every port that sets USE_OPENSSL should also work with libressl if you define WITH_OPENSSL_PORT in your make.conf Binary packages will still use the base system's openssl.
FreeBSD always includes a compiler, so there is no "build essential" type package.
memprof.c:37:3: error: #error "ZTS build not supported (yet)" memprof doesn't support ZTS builds of PHP. This means that PHP has been built with the --enable-maintainer-zts option, and memprof doesn't support this. You should build PHP without the --enable-maintainer-zts switch. This switch is only required if you use a PHP as server module in a ...
Only top voted, non community-wiki answers of a minimum length are eligible