From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released
Date: Mon, 19 Feb 2018 10:34:19 +0100 [thread overview]
Message-ID: <20180219093419.ehwn4mdg53qzb6fu@pengutronix.de> (raw)
In-Reply-To: <20180219081123.egfd77c6k26ed3yg@falbala.home.lespocky.de>
Hallo,
On Mon, Feb 19, 2018 at 09:11:25AM +0100, Alexander Dahl wrote:
> On Sun, Feb 18, 2018 at 03:00:22PM -0500, Jon Ringle wrote:
> > 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
>
> So you probably used Ubuntu 14.04?
>
> > 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?
>
> From my personal analysis I think, this is spread over several files
> in OSELAS.Toolchain repository. In `rules/image-toolchain-deb.make`
> IMAGE_TOOLCHAIN_DEB_VERSION_EXT is set by a function defined in
> `scripts/lib/ptxd_make_debian_version_ext.sh`. This gets ${VERSION_ID}
> from your build host `/etc/os-version`, which is 8 for Debian jessie,
> 9 for Debian stretch and probably 14.04 for the Ubuntu you are using,
> so it depends on the build host. I would guess the 'bpo' means
> something like 'backports', at least Debian backports uses similar
> markings.
>
> The rest of those version numbers is like this: Something creates the
> file `.tarball-version`, maybe it's just included in the tarball, not
> in Git repository. In `rules/image-toolchain-deb.make` the script
> `scripts/setlocalversion` is called with that as a parameter, which
> probably outputs some version from Git, if using the Git repo instead
> of a tarball. This is assigned to IMAGE_TOOLCHAIN_DEB_VERSION in
> `rules/image-toolchain-deb.make` … yes I think this is it.
Right, the different debian packages are built from the same source but for
different Debian release. This is necessary because the new toolchains uses
Python 3 for gdb and jessie, stretch and buster all use different Python 3
minor release.
The versioning is set up in a way that it works correctly if you install
the toolchain on jessie and then update to stretch (provided you have the
correct sources.list entries).
Michael
--
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
next prev parent reply other threads:[~2018-02-19 9:34 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
2018-02-19 8:11 ` Alexander Dahl
2018-02-19 9:34 ` Michael Olbrich [this message]
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=20180219093419.ehwn4mdg53qzb6fu@pengutronix.de \
--to=m.olbrich@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