On 09/18/2015 09:41 PM, rod wrote: > 1) the installation we've done sets up a minimun "system" and things > like network config, wget, and other programs need to be copied into the > system to make them work?
I think you misunderstood. The chroot is solely used for *building* a package, not anything else. You usually don't need a fancy network configuration or additional tools installed for that. The idea of the chroot for a build server or porter box is to have a clean, well-defined minimum environment which is used to build packages. This guarantees that your package is only build against libraries and other binaries installed from unmodified Debian packages and is necessary to make sure your package is installable and usable on any standard Debian system. If you just built a package without a clean chroot, you might end up building a package which requires weird dependencies which are only present on your particular system and therefore make the packages unusable on other Debian installations. You also need a chroot in the special case when you run a 64-bit SPARC kernel with a 32-bit userland such that all packages in the normal system are "sparc" while you actually want to build on "sparc64" packages. Then you need the chroot to have a "sparc64" build environment. Also, once the chroot has been set up and sbuild has been configured, you don't have to change anything about the chroot configuration anymore. You merely need to update the chroots from time to time by chrooting into them and running "apt-get update && apt-get dist-upgrade". > 2) I downloaded the source for mozjs and attempted to build starting > with a ./configure and found python was missing. Is it better to install > the networking and such to do an apt-get install or should I manually > install python? That's not how Debian packages are built. You should work on the actual Debian package: $ apt-get source mozjs $ cd mozjs-XXX $ sbuild --source --arch-all --arch=sparc64 -d sid --source Again, read the manpage for sbuild. >From the top of my head, what needs to be done: 1) Edit js/src/configure.in, line 3025: sparc- => sparc*- This makes sure "sparc64-linux-gnu" is detected at this point. 2) Add dh-autoreconf to Build-Depends in debian/control 3) Modify debian/rules to run autoreconf. Steps 2) and 3) are necessary to have the configure script rewritten as you modified the configure.in autoconf template (configure is a machine-generated script which is created by autoconf by interpreting configure.in). See also: https://wiki.debian.org/Autoreconf > 3) The version of mozjs I downloaded was 31.2.0-rc0. Should I start > with the this one or should I try 1.8.5-1.0.0+dfsg-4.3? Take the one from Debian. Download the sources with apt-get source mozjs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913