From: Juergen Borleis <jbe@pengutronix.de>
To: "Rüdiger, Christoph" <christoph.ruediger@thyssenkrupp.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS.Toolchain 2019.09.0 - incorrect install path
Date: Thu, 19 Sep 2019 08:50:52 +0200 [thread overview]
Message-ID: <201909190850.53213.jbe@pengutronix.de> (raw)
In-Reply-To: <VI1PR05MB5648EB67C79C2CE968D92C7DE6890@VI1PR05MB5648.eurprd05.prod.outlook.com>
Hi Rüdiger,
On Thursday 19 September 2019 05:56:48 Rüdiger, Christoph wrote:
> I discovered an issue in the 2019.09.0 OSELAS toolchain where the
> installation does not happen into the correct path at
> /opt/OSELAS.Toolchain-2019.09.0/... What happens instead is that
> everything gets installed into a package in the platform-... directory,
> but the things never make it from there into the /opt/ directory.
>
> I've attached the logfile for building and installing just the
> cross-binutils in a clean OSELAS-2019.09.0 project.
>
> From what I see, ptxdist creates the packages as it usually does, but for
> whatever reason does not install it on the host.
>
> How is this supposed to happen? What is going wrong here?
configure; make; make install… ;)
Due to regular permission issues in "opt/", the install step is now a
separate step: "ptxdist make install" if I remember correctly.
Refer 00d88a79453255ec56439af359aa3e805f1176dd
"add make target to install the toolchain"
in the OSELAS.Toolchain repository for details.
Cheers,
Jürgen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-19 6:50 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 [this message]
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
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=201909190850.53213.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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