From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released
Date: Sun, 18 Feb 2018 15:00:22 -0500 [thread overview]
Message-ID: <CAMwGMjzvrL_q8UZc2Ookm3rt=COkiH+2POA7thWfHUt+trb7vw@mail.gmail.com> (raw)
In-Reply-To: <20180212155154.gn3omnmv23djbw4u@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1935 bytes --]
I built the arm-v5te toolchain, and it built:
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo14.04+1_amd64.deb
But on https://debian.pengutronix.de/debian/pool/main/o/oselas.toolchain/ I
see:
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1_amd64.deb
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo8+1_amd64.deb
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
What is the cause for the difference in `bpo8+1`, `bpo9+1` and the
`bpo14.04+1` in the filename?
-Jon
On Mon, Feb 12, 2018 at 10:51 AM, Michael Olbrich <m.olbrich@pengutronix.de>
wrote:
> Hi,
>
> I'm happy to announce that I've just released OSELAS.Toolchain-2018.02.0.
>
> This is a major release with significant changes. All components of the
> primary toolchains have been updated to the latest versions. The highlights
> are:
> - gcc 7.3
> - glibc 2.27
> - binutils 2.30
> - kernel headers 4.15
> - gdb 8.1
>
> The Cortex-A8 toolchains have been removed. Please use the ARM v7a
> Toolchains instead. The Cortex-M3 and Cortex-M4 toochains have been
> replaces by the more general ARM v7m and v7em toolchains.
>
> Download the release here:
> https://public.pengutronix.de/oselas/toolchain/
>
> Enjoy,
> Michael Olbrich
>
> --
> 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
>
[-- Attachment #1.2: Type: text/html, Size: 3024 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-02-18 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 15:51 Michael Olbrich
2018-02-13 10:00 ` Roland Hieber
2018-02-13 10:04 ` Michael Olbrich
2018-02-13 12:41 ` Alexander Dahl
2018-02-13 13:30 ` Michael Olbrich
2018-02-13 13:59 ` Denis OSTERLAND
2018-02-13 14:37 ` Michael Olbrich
2018-02-19 9:38 ` Michael Olbrich
2018-02-13 14:05 ` Alexander Dahl
2018-02-13 14:44 ` Michael Olbrich
2018-02-18 20:00 ` Jon Ringle [this message]
2018-02-19 8:11 ` Alexander Dahl
2018-02-19 9:34 ` Michael Olbrich
2018-09-29 15:57 ` [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10 Andreas Pretzsch
2019-01-18 9:07 ` Roland Hieber
2019-01-18 10:34 ` Michael Olbrich
2019-01-18 13:23 ` Roland Hieber
2019-01-18 14:06 ` 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='CAMwGMjzvrL_q8UZc2Ookm3rt=COkiH+2POA7thWfHUt+trb7vw@mail.gmail.com' \
--to=jon@ringle.org \
--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