tried to make Asterisk on vmware but when i tried to start Asterisk, then I got illegal instruction.
and by checking some other topics out here i figured out i should just disable build_native while rebuilding asterisk again, so yes it worked fine.
but m just curious about disabling build_native option and what it really does and how much is the performance affected by disabling it.
any thoughts?
It causes the C compiler to generate instructions that may only be implemented on the specific processor type on which it is compiled, whereas it would otherwise generate instructions that are available on any machine using the same general type of processor. I would expect the main impact to be on codecs, as most of the other code is not going to be amenable to optimisation. As such, any performance benefit will depend on exactly how you are using Asterisk.
I doubt anyone has done any controlled experiments to see exactly what difference it makes.
I’m not sure if the problem with VMWare is that it may get compiled on a different machine, or whether it is a virtualisation problem: either VMWare incorrectly reports the processor capabilities, or it doesn’t virtualise some instructions properly.
If you run “cat /proc/cpuinfo”, at a shell prompt, you will see all the sorts of options that might be considered by the compiler, although many of these will not be relevant to user space programs.
1 Like
that was helpful, thank you.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.