Re: Compiling with gcc -march ix86
On Fri, Dec 24, 2010 at 05:34:38PM -0500, Stephane Russell wrote: I'm actually trying to compile asterisk on DFBSD. It needs to compile with the compiler option -march=ix86, with x3 (gcc spec). But DFBSD uname -m is returning systematically i386. Is their a workaround for that, that would allow me to compile without hacking the autotools scripts? Why don't you try asterisk18 from pkgsrc -head ? It builds fine out-of the box on DragonFly/i386. -- Francois Tigeot
Re: Random x86-64 seg-fault finally fixed
:How would this be different than jail(8)? : :not understanding the 'without virtualization' part - :I know some form of HW virt a-la kvm has been discussed a few times - : :do you mean like segmenting the 'machine' or somesuch? Jail has no ability to segment kernel resources. It is really nothing more than a glorified chroot. The idea here is to have actual separate copies of the kernel running in each partition. -Matt Matthew Dillon dil...@backplane.com
Re: Random x86-64 seg-fault finally fixed
On Sun, Dec 26, 2010 at 8:44 AM, Chris Turner c.tur...@199technologies.org wrote: Matthew Dillon wrote: Partitioning is already desireable for the current 48-core monster and I'd like to have some sort of DragonFly host guest solution that runs at full performance on the bare HW without virtualization. How would this be different than jail(8)? not understanding the 'without virtualization' part - I know some form of HW virt a-la kvm has been discussed a few times - I think that Matthew is talking about something like these : http://en.wikipedia.org/wiki/Logical_Domains http://en.wikipedia.org/wiki/Logical_partition_%28virtual_computing_platform%29 do you mean like segmenting the 'machine' or somesuch?
