Date: Thu, 7 Apr 2016 09:44:49 +0300 From: Boris Samorodov <bsam@passap.ru> To: Russell Haley <russ.haley@gmail.com>, Mark Millard <markmi@dsl-only.net> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Indication of Successful Build Message-ID: <570601E1.1080704@passap.ru> In-Reply-To: <CABx9NuScooxhv0VYAZr6DeWFzw5orvV4xQmcK3YSRVJTwLE1ig@mail.gmail.com> References: <A36D4A7F-FE23-4E99-A2CA-A0F085270DE9@dsl-only.net> <CABx9NuScooxhv0VYAZr6DeWFzw5orvV4xQmcK3YSRVJTwLE1ig@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
06.04.16 23:14, Russell Haley пишет: > Thanks for the input Mark. > > I'm currently looking into the cross build script on the developers Sees that you misunderstood Marks word "script". He uses SCRIPT(1) to save build script output to a log-file. > wiki, as well as considering updating crochet to use the u-boot ports > and adding hummingboard to it. I'm going to take all these suggestions > and see what I can come up with. In my mind it wouldn't be hard to use > the return codes indicated by Boris to create a running log of make > results and copy successful outputs to a different directory. What > raises my concern is that I can't be the first person to ever come up > with this idea, so where are all the other attempts at this? In my > mind that means I'm either way ahead of the curve (not) or I am going > down the wrong path and there is something else to this I haven't > considered. I'd say that most developers have different purposes, plus it's not hard to create a shell script to automate the task. So everybody have some of them at their armoury. Here is mine (written once in a hurry, but used to be helpful and used often). > Anyway, I keep telling myself to get on with my own project, but there > is just so much fun stuff to play with down in the guts of FreeBSD! I > was just trying to get booting from NFS to work. lolz. Okay, down the > rabbit hole... > > Thanks, > > Alice (Russ) > > On Wed, Apr 6, 2016 at 12:13 PM, Mark Millard <markmi@dsl-only.net> wrote: >> I use script to make a typescript/log file and keep the log file for as long as I care. So, for example, the script use in: >> >>> # more ~/sys_build_scripts.powerpc64-host/make_powerpc64vtsc_nodebug_incl_clang_xtoolchain-powerpc64-host.sh >>> script ~/sys_typescripts/typescript_make_powerpc64vtsc_nodebug_incl_clang_xtoolchain-powerpc64-host-$(date +%Y-%m-%d:%H:%M:%S) \ >>> env __MAKE_CONF="/root/src.configs/make.conf" SRC_ENV_CONF="/root/src.configs/src.conf.powerpc64-xtoolchain.powerpc64-host" \ >>> MAKEOBJDIRPREFIX="/usr/obj/xtoolchain/powerpc.powerpc64" \ >>> make $* -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?570601E1.1080704>