From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0] ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YFk9X-000671-4b for ptxdist@pengutronix.de; Mon, 26 Jan 2015 14:56:31 +0100 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80) (envelope-from ) id 1YFk9X-0002tT-3C for ptxdist@pengutronix.de; Mon, 26 Jan 2015 14:56:31 +0100 Date: Mon, 26 Jan 2015 14:56:31 +0100 From: Michael Olbrich Message-ID: <20150126135631.GD30319@pengutronix.de> References: <54C3A95D.7000404@gr13.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <54C3A95D.7000404@gr13.net> Subject: Re: [ptxdist] oselas-toolchain: fully automatic build / packaging Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Hi, On Sat, Jan 24, 2015 at 03:17:01PM +0100, Enrico Weigelt, metux IT consult wrote: > I'd like to build/package oselas toolchains fully automatically. > > I've got a little tool (*1) for such tasks (doing all the > git-buildpackage and pbuilder magic) - the idea is pretty simple: > It manages the local git clones for the individual packages > (eg. automatically syncs them when required), and within these > repos, I've got separate branches for the individual distros, > the target distro is guessed from the branch/tag prefix > (eg. for Ubuntu trusty, it's "trusty/"). All I now have to do > is checkout the proper branch and hit a button - after some > coffe cycle, I've got the ready-to-deploy package in a apt repo. > > Now the oselas problems: it wants to operate directly in /opt/OSELAS-... > Not only is it non-interactive (I have to enter my root pw, so it > can sudo to get access to that directory), even worse: I can't do > the usual non-privileged and DESTDIR-based install here, which is > required for the whole deb packaging machinery. Yes you can. The build_all_v2.mk does this as well, you can use it as an example. You just need to set PTX_AUTOBUILD_DESTDIR to the desired DESTDIR. > By the way: the build just failed: > > In file included from > /home/nekrad/metux/OSELAS.Toolchain/platform-arm-cortexa8-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized/build-cross/binutils-2.24/gold/script.cc:45:0: > /home/nekrad/metux/OSELAS.Toolchain/platform-arm-cortexa8-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized/build-cross/binutils-2.24/gold/script-c.h:221:7: > warning: 'yylex' initialized and declared 'extern' [enabled by default] > yylex(YYSTYPE*, void* closure); This looks like a flex version mismatch. Which version are you using ('flex --version')? Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list ptxdist@pengutronix.de