From owner-freebsd-hackers Tue Oct 2 8:48:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 095ED37B403; Tue, 2 Oct 2001 08:48:22 -0700 (PDT) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id f92FjXs25805; Tue, 2 Oct 2001 08:45:33 -0700 (PDT) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200110021545.f92FjXs25805@iguana.aciri.org> Subject: compiling kernels from readonly source trees ? To: hackers@freebsd.org Date: Tue, 2 Oct 2001 08:45:33 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Bcc to -small as someone there might have had similar problems] Hi, I was trying to modify the picobsd build scripts so that the source tree is entirely readonly. For the most part of it i think i managed, the only missing part seems to be compilation of new kernels. config supports the "-d" command to set the destination directory, but it appears that it insists on the config file being in ${SYS}/${ARCH}/conf/ as it derives other paths from the current directory, such as ... if (realpath("../..", srcdir) == NULL) ... (void) snprintf(fname, sizeof(fname), "../../conf/options"); and maybe more places like this. Am I wrong ? And if not, is there any plan to make config handle config files in other places than ${SYS}/${ARCH}/conf ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message