From: Mircea Ciocan <m.ciocan@ppc-ag.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Segmentation fault with ptxdist-2020.05.0
Date: Fri, 15 May 2020 10:07:17 +0200 [thread overview]
Message-ID: <42ea81ca-d8f9-b311-c5c1-2954a39d88f0@ppc-ag.de> (raw)
In-Reply-To: <20200515075948.jmxgtvhv6vwswrcf@falbala.internal.home.lespocky.de>
On 15.05.20 09:59, Alexander Dahl wrote:
> Hello Mircea,
>
> On Fri, May 15, 2020 at 09:40:45AM +0200, Mircea Ciocan wrote:
>> The main problem is that the older releases as 2020.05.0 doesn't compile the
>> toolchain correctly.
> Which toolchain? If you compile the OSELAS Toolchain by yourself
> (instead of e.g. using the prepackaged binary toolchains from [1]),
> you should use _exactly_ the ptxdist version the toolchain project is
> configured for. For example if you want to build OSELAS Toolchain
> v2019.09.1 you should use exactly ptxdist-2020.02.0 to build that
> toolchain.
This is exactly what I was doing, I've used 2020.02 because it was
around for the toolchain, but wanted the updated stuff in the newer
versions.
> You can (and probably should) use a newer ptxdist version to build
> your BSP then.
I've tried that and kind of failed as described :(, now I'll retry with
the hint from Michael for data collection and see what's coming of it.
Is not every day that one sees this kind of bug in bash.
> Greets
> Alex
Cheers,
Mircea
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-05-15 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:36 Mircea Ciocan
2020-05-15 7:40 ` Mircea Ciocan
2020-05-15 7:48 ` Michael Olbrich
2020-05-15 7:59 ` Alexander Dahl
2020-05-15 8:07 ` Mircea Ciocan [this message]
2020-05-15 7:46 ` Michael Olbrich
2020-05-15 13:02 ` Mircea Ciocan
2020-05-15 13:36 ` Mircea Ciocan
2020-05-29 9:21 ` Michael Olbrich
2020-05-29 11:03 ` [ptxdist] [PATCH] ptxd_lib_dopermissions: use 'set -e' instead of && Michael Olbrich
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=42ea81ca-d8f9-b311-c5c1-2954a39d88f0@ppc-ag.de \
--to=m.ciocan@ppc-ag.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