OS: Oracle Solaris 11.3.1.5.2, CPU Arch : X86I recently installed Squid by doing$ pkg install squidThis went fine:root@darwin1:~# pkg info squid          Name: web/proxy/squid       Summary: Squid Web Proxy Cache   Description: Squid is a caching proxy for the Web supporting HTTP, HTTPS,                FTP, and more.      Category: Web Services/Application and Web Servers         State: Installed     Publisher: solaris       Version: 3.5.5 Build Release: 5.11        Branch: 0.175.3.0.0.30.0Packaging Date: Fri Aug 21 17:30:06 2015          Size: 51.84 MB          FMRI: pkg://solaris/web/proxy/squid@3.5.5,5.11-0.175.3.0.0.30.0:20150821T173006Zbut I cannot run Squid:root@darwin1:~# /usr/squid/sbin/squid -hIllegal Instruction (core dumped)The file command gives me this:root@darwin1:~# file /usr/squid/sbin/squid/usr/squid/sbin/squid:  ELF 32-bit LSB executable 80386 Version 1, dynamically linked, not strippedI'm inside a local (non-kernel) zone. It shouldn't matter, should it?Why the core dump?
squid: Illegal Instruction (core dumped)
solaris;virtual machine;vmware;squid
Sorry, I think I've found the answer myself: http://wiki.squid-cache.org/KnowledgeBase/IllegalInstructionError.(quote begin)Illegal Instruction errors on Squid 3.4Synopsis Squid 3.4 and later, running on certain paravirtualized  systems and even some claiming full virtualization (at least KVM, Xen,  and Xen derivatives are confirmed so far) crashes with an illegal  instruction error soon after startup.SymptomsSquid crashes with Illegal Instruction error immediately after startup on a virtual machine on Intel-compatible processors ExplanationThe Squid build system uses by default the -march=native  gcc option  to optimize the resulting binary. Unfortunately certain  (para-)virtualization systems don't support the whole instruction set  they advertise. The compiler doesn't know, and generates instructions  which trigger this error.WorkaroundThese optimizations are helpful but not necessary to have a fully  functional squid, especially on ia64/amd64 platforms. The detected  defaults can be overridden by supplying the --disable-arch-native  option to the configure script.(quote end)We're running Solaris inside VMware ESXi 6.0.  So I guess that's the reason.I won't delete my own question on the odd chance that someone else will run into this too.