[flashboot] flashboot build issue?

[Rickard Dahlstrand]

Hi Jason,

Sorry for the low attention on this lists, but for all I know the
Flashboot-community is a bit thin. ;-)

I haven't tried to build using 4.2 as I'm not running it anywhere, but
building 4.1 works like a charm. Other than that I can't help you until
I get my 4.2-snapshot going. Anyone else??

Rickard.

Jason George wrote:
> Damien asked me to forward this to the list.
>
> I'll also add that my system is running the Aug 23 snapshot:
>
> OpenBSD 4.2 (GENERIC) #374: Thu Aug 23 10:41:10 MDT 2007
>      deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2 cache) 898 MHz
> cpu0: 
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS
> R,SSE
>
>
> ---------- Forwarded message ----------
> Date: Thu, 30 Aug 2007 22:43:37 -0600 (MDT)
> From: Jason George <jbg at masterplan.org>
> To: djm at mindrot.org
> Subject: flashboot build issue?
>
>
> Hi -
>
> I was wondering if there is an issue with 4.2-based source tree and flashboot.
>
> I hadn't run any of the build scripts in about 3.5 months (around the time of 
> the hackathon) but noticed yesterday that my scripts from January were now 
> failing on the build-release portion.  (They'd been running fine in different 
> incarnations for well over a year)  Initially, they failed trying to install 
> the man page for ypclnt.3.  This caused me to start digging.
>
> I then downloaded the 20070830 snapshot and encountered the same issue.
>
> I tracked it down to the options in mk-mini.conf.  If I leave various options 
> of KERBEROS, YP, etc equal to NO, then the build fails in different places when 
> trying to install.
>
> My setup involves building a raw, clean source tree from fresh cvs tree from a 
> daily cvsync snapshot.  I merge my custom binaries in much later (nothing to do 
> with the build-release script) so that isn't the cause.
>
> Any thoughts?  A standard build-world from /usr/src works just fine.  It's the 
> mk-mini options that are crating the build for me.  Did something change in 
> "make" and how it handle its options in the last number of months that I've 
> missed?
>
> Commenting options below allows the build-release to run to completion, and the 
> followup scripts to build a compressed kernel, etc run, but the implication is 
> that Kerberos is now compiled in, etc...
>
> Thanks!
>
> --Jason
>
> # more mk-mini.conf
> # $Id: mk-mini.conf,v 1.1 2006/08/26 17:52:44 jakob Exp $
>
> WARNINGS=yes
> PIPE=-pipe
> STATIC=
> DEBUG=
>
> #KERBEROS=no
> #KERBEROS5=no
> #YP=no
> #AFS=no
> #TCP_WRAPPERS=no
>
>
>
>
>
> # more build-release.sh
> #!/bin/sh
> #
> # $Id: build-release.sh,v 1.2 2006/09/03 18:28:33 jakob Exp $
>
> set -xe
>
> ### PATH = /v00/embedded/src/ResourceChain/flashboot-20070830/
> BASE=`pwd`
>
> #BSDSRCDIR=${BSDSRCDIR:-/usr/src}
> BSDSRCDIR=${BSDSRCDIR:-/v00/embedded/src/OpenBSD/OpenBSD-current/src}
>
> #BSDOBJDIR=${BSDOBJDIR:-${BASE}/flash-obj}
> BSDOBJDIR=${BSDOBJDIR:-/v00/embedded/obj/flashboot/flash-obj}
>
> #DESTDIR=${DESTDIR:-${BASE}/flash-dist}
> DESTDIR=${DESTDIR:-/v00/embedded/obj/flashboot/flash-dist}
>
> _MINI=-mini
>
> RELEASEDIR=${BASE}/release${_MINI}
> MAKECONF=${BASE}/mk${_MINI}.conf
> SUDO=sudo
>
> export BSDSRCDIR BSDOBJDIR DESTDIR RELEASEDIR MAKECONF SUDO
>
> cd ${BSDSRCDIR}
> mkdir -p ${BSDOBJDIR} ${DESTDIR}
>
> if [ "x$1" != "xbuilt" ] ; then
>          rm -rf ${DESTDIR}/*
>          make -k cleandir
>          rm -rf ${BSDOBJDIR}/*
>
>          make obj
>          cd etc
>          make distrib-dirs
>          cd ..
>
>          make build
> fi
>
> cd etc
> make distribution-etc-root-var
> cd ..
> #
>
> _______________________________________________
> flashboot mailing list
> flashboot at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/flashboot
>