Added into gerrit:
https://review.linaro.org/11498https://review.linaro.org/11499
On 20 April 2016 at 19:53, Denys Dmytriyenko <denis(a)denix.org> wrote:
> From: Denys Dmytriyenko <denys(a)ti.com>
>
> With migration from crosstool-NG to ABE, libgcov.a changed path and is now
> available in ${libdir}. So, instead of being packaged into own libgcov-dev
> package, it gets picked up by "catchall" libc6-staticdev package. This mostly
> works, as long as nothing directly depends on libgcov-dev. Unfortunately,
> packagegroup-core-standalone-sdk-target does and is the one being used when
> building SDKs with -c populate_sdk. Correct path to generate libgcov-dev pkg.
>
> Signed-off-by: Denys Dmytriyenko <denys(a)ti.com>
> ---
> This is required for fido/jethro, but krogoth/master introduces single -dev
> package rule, so separate libgcov-dev package can be dropped entirely.
>
> .../external-linaro-toolchain/external-linaro-toolchain.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb
> index ea41179..531caf7 100644
> --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb
> +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb
> @@ -301,7 +301,7 @@ PKGV_gdbserver = "${ELT_VER_GDBSERVER}"
> ALLOW_EMPTY_${PN}-mtrace = "1"
> FILES_${PN}-mtrace = "${bindir}/mtrace"
>
> -FILES_libgcov-dev = "${libdir}/${TARGET_SYS}/${BINV}/libgcov.a"
> +FILES_libgcov-dev = "${libdir}/libgcov.a"
>
> FILES_libsegfault = "${base_libdir}/libSegFault*"
>
> --
> 2.2.0
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev(a)lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-dev
--
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs
Hi Koen,
I think you mentioned that issue already briefly at ELC, but I stumbled
upon it independently again:
We have issues with the versioning of the Linaro toolchain in Ångström.
While it happens with the Ångström package feed, I think it is actually
a problem of how the meta-linaro layer uses PV/PR.
It seems that the change to the 2015.11-2 release added yet another
hyphen, which gets interpreted wrong by opkg. When we build a new image,
and try to download something which just asks for linaro-5.2, we get the
following error:
Not downgrading libgcc1 from linaro-5.2-r2015.11-2 to
linaro-5.2-r2015.11.0 on root.
Downgrading? The "2015.11-2" release should be an upgrade...
This can be verified when checking the versions using the
compare-versions command:
$ opkg compare-versions "linaro-5.2-r2015.11-2" '>='
"linaro-5.2-r2015.11"; echo $?
1
Error code is set, hence the comparison is _not_ satisfied. Whether
there is another .0 at the end of r2015.11 does not matter (Btw, where
is that coming from?)
Things after the hyphen are interpreted by opkg as package revision...
This leads to the following akward situation (added some debug prints
into opkg's source):
$ ./src/opkg --offline-root . compare-versions linaro-5.2-r2015.11-2
'>=' linaro-5.2-r2015.11
parse_version, version linaro-5.2-r2015.11, revision 2
parse_version, version linaro-5.2, revision r2015.11
This change introduced the additional hyphen:
https://git.linaro.org/openembedded/meta-linaro.git/commitdiff/62333718e8f3…
I think everything should work if that additional -2 would be a .2...
However, hyphens in the main version number are actually quite frowned
upon, also the debian policy does not allow hyphens:
https://www.debian.org/doc/debian-policy/ch-binary.html#s-versions
So maybe even the hyphen in linaro-5.2 should be something else...
--
Stefan
On 19 April 2016 at 07:30, Koen Kooi <koen.kooi(a)linaro.org> wrote:
> On 18 April 2016 at 23:03, Denys Dmytriyenko <denis(a)denix.org> wrote:
>> On Fri, Apr 15, 2016 at 08:01:48AM +0200, Koen Kooi wrote:
>>> On 14 April 2016 at 18:27, Denys Dmytriyenko <denis(a)denix.org> wrote:
>>> > On Thu, Apr 14, 2016 at 10:04:18AM +0200, Koen Kooi wrote:
>>> >> On 14 April 2016 at 07:09, Fathi Boudra <fathi.boudra(a)linaro.org> wrote:
>>> >> > On 14 April 2016 at 00:05, Denys Dmytriyenko <denis(a)denix.org> wrote:
>>> >> >> Koen, et al,
>>> >> >>
>>> >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible to use the
>>> >> >> binary version with the external-linaro-toolchain recipe. Are there any
>>> >> >> immediate plans to provide corresponding recipes to build the same version of
>>> >> >> the toolchain from sources? Thanks.
>>> >> >
>>> >> > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next cycle.
>>> >>
>>> >> The test build is still running, but here's the gerrit:
>>> >>
>>> >> https://review.linaro.org/11376
>>> >
>>> > Thanks!
>>>
>>> It breaks grub, I'll sort that out with the toolchain folks later today.
>>>
>>> > What about glibc-2.21?
>>>
>>> Haven't looked at that one yet.
>>
>> Any updates on the above 2 items? It's not exactly blocking me currently, as I
>> have workarounds in place, but it would be nice to get these resolved in
>> krogoth/2.1... Thanks!
>
> For grub we need both a newer toolchain and a newer binutils. Still
> haven't looked at glibc 2.21 yet, sorry.
An update to the gcc situation: we've decided to move it to the next
cycle (2016.06) so we can use a newer gcc release with the fix
included. I've retracted https://review.linaro.org/#/c/11376/ to
reflect this.
--
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs