From: Bruno Thomsen <bth@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2019.07.0 released
Date: Thu, 18 Jul 2019 06:38:17 +0000 [thread overview]
Message-ID: <HE1PR04MB313095CB0B9057C7EF59082CDCC80@HE1PR04MB3130.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190705131302.dijhen3kjgcbxx5d@pengutronix.de>
Hi,
> I'm happy to announce that I've just released ptxdist-2019.07.0.
>
> This release contains several bigger changes.
I have discovered a bug in ptxdist-2019.07.0 when running it in docker.
As this always starts without a ~/.ptxdist directory and therefore no old ptxdistrc-xxxx.xx configuration file.
When running ptxdist-2019.07.0 it creates the ~/.ptxdist directory and then exits with an error as it's unable to find an old ptxdistrc configuration file.
$ ptxdist-2019.07.0
/usr/local/bin/ptxdist-2019.07.0: line 2261: /home/developer/.ptxdist/ptxdistrc-2010.01: No such file or directory
/usr/local/lib/ptxdist-2019.07.0/scripts/libptxdist.sh: line 105: /home/developer/.ptxdist/ptxdistrc-2010.01: No such file or directory
cp: cannot stat '/home/developer/.ptxdist/ptxdistrc-2010.01': No such file or directory
PTXdist: fatal error ... cannot start, sorry!
The workaround I currently use is to call the ptxdist-2018.12.0 version inside the same docker image, used for compiling OSELAS.Toolchain, before calling the new ptxdist version. As this creates ~/.ptxdist/ptxdistrc-2018.12 configuration file which then allows ptxdist-2019.07.0 to start and create ~/.ptxdist/ptxdistrc-2019.07 successfully.
$ ptxdist-2018.12.0
PTXdist 2018.12.0 Build System for Embedded Linux Systems
$ ptxdist-2019.07.0
PTXdist 2019.07.0 Build System for Embedded Linux Systems
/Bruno
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-07-18 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 13:13 Michael Olbrich
2019-07-18 6:38 ` Bruno Thomsen [this message]
2019-07-18 8:24 ` 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=HE1PR04MB313095CB0B9057C7EF59082CDCC80@HE1PR04MB3130.eurprd04.prod.outlook.com \
--to=bth@kamstrup.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