From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Failure in using OSELAS 2016.06.1 toolchain with PTXdist 2017.03.0
Date: Tue, 28 Mar 2017 14:24:11 +0200 [thread overview]
Message-ID: <20170328122410.GA878@archie.localdomain> (raw)
In-Reply-To: <201703280934.38906.jbe@pengutronix.de>
Hi,
On Tue, Mar 28, 2017 at 09:34:38AM +0200, Juergen Borleis wrote:
> Hi Ojas,
>
> On Tuesday 28 March 2017 01:17:30 Ojas Kulkarni wrote:
> > I am trying to build 2016.06.1 toolchain with PTXdist 2017.03.0 version.
> > I am getting error in glib package while building toolchain shown below,
> > My questions are,
> >
> > 1) Is any compatibility issues observed with specified versions?
> >
> > 2) Which version of OSELAS toolchain is best suitable to use with
> > PTXdist 2017.03.0 version?
>
> The OSELAS-Toolchain-2016.06.1 is intended to be built with PTXdist-2016.06.
> After building, you can use this toolchain with whatever PTXdist version in
> your projects. All PTXdist versions can co-exist on your host and do not
> interfere.
I can also reproduce this with my toolchains - based on OSELAS.Toolchain
but with newer GCC, glibc, etc. - if I build them with ptxdist
2017.03.0.
With ptxdist 2017.01.0, they build fine though and I think I found the
culprit in 2017.03.0:
https://git.pengutronix.de/cgit/ptxdist/commit/?id=8cd525b95616ee8e2e9f982c04a1fcb0c745c521
If I add the ptxd_make_world_patchin.sh script from before this commit
to my toolchain project, ptxdist 2017.03.0 successfully builds the
toolchain.
Regards,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-03-28 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 23:17 Ojas Kulkarni
2017-03-28 7:34 ` Juergen Borleis
2017-03-28 12:24 ` Clemens Gruber [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=20170328122410.GA878@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--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