From: "Christoph Rüdiger" <christoph@ruediger.engineering>
To: ptxdist@pengutronix.de
Cc: "Rüdiger, Christoph" <christoph.ruediger@thyssenkrupp.com>
Subject: Re: [ptxdist] OSELAS.Toolchain 2019.09.0 - incorrect install path
Date: Wed, 02 Oct 2019 22:37:40 +0200 [thread overview]
Message-ID: <164B1115-A936-43EA-BB4F-F47FC8015134@ruediger.engineering> (raw)
In-Reply-To: <20190920133819.gsrrfm6lag2hebka@pengutronix.de>
You are right. I was switching toolchain versions back and forth and didn't notice that 2019.09.0 does not have this behavior anymore.
Sorry for causing confusion.
Christoph
-----Ursprüngliche Nachricht-----
Von: ptxdist <ptxdist-bounces@pengutronix.de> im Auftrag von Michael Olbrich <mol@pengutronix.de>
Antworten an: <ptxdist@pengutronix.de>
Datum: Freitag, 20. September 2019 um 15:39
An: <ptxdist@pengutronix.de>
Cc: Rüdiger, Christoph <christoph.ruediger@thyssenkrupp.com>
Betreff: Re: [ptxdist] OSELAS.Toolchain 2019.09.0 - incorrect install path
On Fri, Sep 20, 2019 at 07:55:52AM +0200, Juergen Borleis wrote:
> Hi Christoph (hope, this time its correct :) ),
>
> On Thursday 19 September 2019 21:01:30 Rüdiger, Christoph wrote:
> > that was the key. For everyone else running into this issue, the command
> > to install the toolchain to /opt/OSELAS... is now
> >
> > ptxdist make install
>
> \o/
>
> > However, ptxdist still checks the existence of /opt/OSELAS.Toolchain...
> > at the very beginning of the build. Shouldn't it do that as part of the
> > make install step, given that it never touches /opt/ during ptxdist go?
>
> Hmm, seems some old code still remains... Michael?
I've not seen anything like this when I built the toolchains. What exactly
happens for you?
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
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-10-02 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 3:56 Rüdiger, Christoph
2019-09-19 6:50 ` Juergen Borleis
2019-09-19 19:01 ` Rüdiger, Christoph
2019-09-20 5:55 ` Juergen Borleis
2019-09-20 13:38 ` Michael Olbrich
2019-10-02 20:37 ` Christoph Rüdiger [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=164B1115-A936-43EA-BB4F-F47FC8015134@ruediger.engineering \
--to=christoph@ruediger.engineering \
--cc=christoph.ruediger@thyssenkrupp.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