Re: Benefit to cross-compile sparc on sparc64
Mouse <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.sparc |
|---|---|
| Message-ID | <[email protected]> |
> Subject: Benefit to cross-compile sparc on sparc64 > Is there any ? As opposed to what? As opposed to running on real sparc (ie, sparc32) hardware? As opposed to running under emulation on completely non-SPARC hardware? As compared to cross-compiling sparc from a non-SPARC (amd64, arm, whatever) port? In any case, some possible answers, depending on what the comparison is with, and in sokme cases on other things (such as what hardware you have available): - Speed? - Convenience? - Bug avoidance? - Bug anti-avoidance (ie, bug finding)? > My current workflow for building my own sparc packages involves an amd64 VM $ > I now have a v240 and was wondering if I would get any benefit from cross co$ Don't sparc64 kernels support sparc (ie, sparc32) userland? If that memory of mine is correct, you should be able to just plop a sparc userland in place and chroot to it, instead of cross-building. Of course, running under emulation means you _are_ running on a SPARC (of whatever architecture your emulation provides), just a macrocoded one instead of a microcoded or hardware one. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B