Date: Tue, 07 Sep 1999 00:31:10 -0400 (EDT) From: John Baldwin <jobaldwi@vt.edu> To: Atsuo Kobayashi <akoba@ebina.hitachi.co.jp>, abial@FreeBSD.org Cc: freebsd-small@freebsd.org Subject: RE: build custom failed - [PATCH] Message-ID: <0FHO006UF9VSBO@gkar.cc.vt.edu> In-Reply-To: <199909010905.AA00017@akoba.ebina.hitachi.co.jp>
index | next in thread | previous in thread | raw e-mail
On 01-Sep-99 Atsuo Kobayashi wrote:
> Hi.
> I tried custom build of PicoBSD. and get followings.
> ======
> PicoBSD build -- Current parameters:
>
> 1. Type: custom (from /usr/home/akoba/terminal/pico_gen)
> 2. MFS size: 2400 kB
> 3. Language: en
> 4. Site-info:
> -> We'll use the sources living in /usr/src
>
> -> I hope you have checked the ../custom/PICOBSD config file...
>
>
>
> -> Checking if we have to build the PICOBSD kernel...
> make: cannot open ../build/Makefile.conf.
> =======
> I think,
> In custom build, the script once cd to the symbolic link
> "/usr/src/release/picobsd/custom" .
> Then "../build/Makefile.conf" not points to
> "/usr/src/release/picobsd/build/Makefile.conf".
> Except only case custom is linked to /usr/src/release/picobsd/xxxx.
>
> Is that so ?
> I would like to place custom build parameters on my home directry.
> How can i do it ?
>
> Thanks.
> Atsuo
This patch a) fixes /usr/src/release/picobsd/{build,stage1} to
support symbolic custom/ directories again, and b) adds a cosmetic fix
to build so that if an existing custom directory is used, then its name
is displayed in the main dialog box.
You can get the patch from http://www.freebsd.org/~jhb/pico.patch
---
John Baldwin <jobaldwi@vt.edu> -- http://www.cslab.vt.edu/~jbaldwin/
PGP Key: http://www.cslab.vt.edu/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0FHO006UF9VSBO>