mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Rüdiger, Christoph" <christoph.ruediger@thyssenkrupp.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] OSELAS.Toolchain 2019.09.0 - incorrect install path
Date: Thu, 19 Sep 2019 19:01:30 +0000	[thread overview]
Message-ID: <AM6PR05MB5639DB91C84E51B3F0190E3FE6890@AM6PR05MB5639.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <201909190850.53213.jbe@pengutronix.de>

Hi Jürgen,

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

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?

Thank you,
Christoph

-----Original Message-----
From: Juergen Borleis <jbe@pengutronix.de> 
Sent: Thursday, September 19, 2019 2:51 AM
To: Rüdiger, Christoph <christoph.ruediger@thyssenkrupp.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS.Toolchain 2019.09.0 - incorrect install path

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                   | https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&amp;data=02%7C01%7C%7C29312eab37c4454c978b08d73ccdb9a4%7Cd79555d18adb46eaaf6cb6b2a24e4fe7%7C0%7C0%7C637044726599373586&amp;sdata=VR%2BZaxTx5G0ErlXywoaiyd61pxFRRXIDMCTpySc7vS0%3D&amp;reserved=0  |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-09-19 19:01 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 [this message]
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=AM6PR05MB5639DB91C84E51B3F0190E3FE6890@AM6PR05MB5639.eurprd05.prod.outlook.com \
    --to=christoph.ruediger@thyssenkrupp.com \
    --cc=jbe@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