From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] doc: update link to toolchain download
Date: Wed, 6 Dec 2017 08:17:25 +0100 [thread overview]
Message-ID: <20171206071724.hpfnfntzgbaachqe@falbala.home.lespocky.de> (raw)
In-Reply-To: <20171205221854.31379-1-r.hieber@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
Hei hei,
On Tue, Dec 05, 2017 at 11:18:54PM +0100, Roland Hieber wrote:
> I'm not quite sure if this is the right place ("The content on
> public.pengutronix.de is mostly temporary, so it might vanish into thin
> air any time"), but the original link is now dead and this one works.
> Otherwise I did not find any reference to the toolchains on the new
> PTX homepage.
I always built this from Git in the past:
https://git.pengutronix.de/cgit/OSELAS.Toolchain/
Not sure if that's appropriate for the documentation, though.
Besides: does ptxdist work with other toolchains? Does anyone use
other toolchains on a regular basis?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-12-06 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 22:18 Roland Hieber
2017-12-06 7:17 ` Alexander Dahl [this message]
2017-12-06 8:50 ` Juergen Borleis
2018-02-05 1:30 ` [ptxdist] [PATCH v2] doc: environment: " Roland Hieber
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=20171206071724.hpfnfntzgbaachqe@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
--cc=r.hieber@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