From owner-freebsd-arm@freebsd.org Thu Apr 7 14:38:37 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5999B061F7 for ; Thu, 7 Apr 2016 14:38:37 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from erouter6.ore.mailhop.org (erouter6.ore.mailhop.org [54.187.213.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86CA310C6 for ; Thu, 7 Apr 2016 14:38:37 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 48cfd09f-fcce-11e5-827e-7d17a39bef25 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 7 Apr 2016 14:37:41 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u37EcYEc003811; Thu, 7 Apr 2016 08:38:34 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1460039914.1091.297.camel@freebsd.org> Subject: Re: Indication of Successful Build From: Ian Lepore To: Russell Haley , Boris Samorodov Cc: freebsd-arm , Mark Millard Date: Thu, 07 Apr 2016 08:38:34 -0600 In-Reply-To: References: <570601E1.1080704@passap.ru> Content-Type: text/plain; charset="koi8-r" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 14:38:37 -0000 On Thu, 2016-04-07 at 00:14 -0700, Russell Haley wrote: > On Wed, Apr 6, 2016 at 11:44 PM, Boris Samorodov > wrote: > > 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. > > Thank you, I understood what he was doing. I was refering to the > script here: > https://wiki.freebsd.org/FreeBSD/arm/crossbuild > > > > > > 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). > > Thank you for your script. This is precisely what I was looking for: > some input on how other people build! It would be fairly trivial to add automatic log generation to that script on the wiki page. I usually don't care, but when I want logs while I'm building I just add "2>&1 | tee make.log" (bash/sh syntax, it would be different for csh) when I launch the script. It would be easy enough to put that inside the script, perhaps with some logic to generate a log name that includes date and time. -- Ian