From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] oselas-toolchain: fully automatic build / packaging
Date: Mon, 26 Jan 2015 14:56:31 +0100 [thread overview]
Message-ID: <20150126135631.GD30319@pengutronix.de> (raw)
In-Reply-To: <54C3A95D.7000404@gr13.net>
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
prev parent reply other threads:[~2015-01-26 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 14:17 Enrico Weigelt, metux IT consult
2015-01-26 13:56 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150126135631.GD30319@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox