Re: [yocto] Forcing GCC version for native compilation
On Thu, Nov 22, 2018 at 12:32 PM Burton, Ross wrote: > > On Thu, 22 Nov 2018 at 07:33, Teemu K wrote: > > I have project made for Yocto 1.7, but I'd like to compile it on newer > > Linux distribution that default GCC version is 5.x. GCC version itself > > causes some problems, because some things have changed. > > > > There is also GCC 4.8 available, but it's not called 'gcc', but 'gcc-4.8'. > > > > The question is that is there way to force yocto use 'gcc-4.8' instead > > of 'gcc'? I did some searching and couldn't find any options how to do > > it. I tried to making link to ~/bin/gcc pointing gcc-4.8 and having > > that first in PATH, but that didn't quite work. I'm guessing path got > > re-set at some point. > > > > And before someone says. Updating Yocto to solve problem is not > > solution. System is being updated, but current system still needs to > > be able to compile. > > The modern solution is to set BUILD_CC and so on, see bitbake.conf. > > Note that in such an old release this might not work as well as you'd > hope because I don't think it was fully tested. In which case your > options in preferred order: > 1) Some distributions let you change what the default compiler, for > example /usr/bin/gcc might be a symbolic link you can just change. > 2) PATH fiddling as you did. You'll most likely need to replace more > than just gcc, for example cpp. > 3) Just mv /usr/bin/gcc to /usr/bin/gcc-5 (and cpp, and anything > else), and symlink gcc -> gcc-4.8 > > Ross 1) There is BUILD_CC also in this version of Yocto. Doesn't seem to do anything. I modified poky/meta/conf/bitbake.conf for testing purposes to have BUILD_CC pointing those 4.8 versions yet the sources are compiled with 'gcc' not 'gcc-4.8' so either something else overrides those settings and/or source packages ignore that setting. 2) I also tried making links go gcc/g++/cpp and adding them to PATH first. This seemed to work, bit better, but now compilation failed to this: /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc.a when searching for -lgcc Which is interesting since I can use the gcc-4.8 just fine manually and it creates working binary. 3) /usr/bin/gcc is actually link to gcc-5, but I don't want to change that because then it would be system wide change and I want to avoid that. I'll dig bit deeper why the second option didn't work. Any other suggestions are welcome as well. -Teemu -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA cycle report for 2.4.4 RC1
Hello All, This is the full report for 2.4.4 RC1: https://wiki.yoctoproject.org/wiki/WW46_-_2018-11-14_-_Full_Test_Cycle_2.4.4_RC1 Summary All planned tests were executed. Total Test Executed - 3330 Passed Test - 3318 Failed Test - 8 Blocked Test - 4 There were zero high priority defect. Team had found 2 new defects. New Bugs [1] Bug 13033 - [2.4.4RC1] [Bitbake] [Case 142] PR number is not getting increased with remote server/local client mode https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033 [2]Bug 13038 - [2.4.4RC1][Package Management][Getting Error Message "Failed to synchronize cache for repo 'repository'"] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13038 Thanks & Regards, Sangeeta Jain -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto on Atmel SAME70?
I believe YOCTO currently don't support MMU less like SAME70 MCU. If someone have YOCTO with MMU less I'm very interested :D GFB Em qui, 22 de nov de 2018 às 04:46, Khem Raj escreveu: > atmel boards are supported through meta-atmel BSP layer > > see > > https://github.com/linux4sam/meta-atmel > > sample images > https://github.com/linux4sam/meta-atmel/tree/sumo/recipes-atmel/images > On Wed, Nov 21, 2018 at 8:30 PM rz charger wrote: > > > > Hi everyone, > > > > Good day. > > > > Currently our team is using Yocto on CM3 Raspberry Pi. We are planning > to port our current Yocto project into Atmel SAME70. However we are not > sure whether it is possible or not. We have few questions hopefully someone > has some experience with this can enlighten us. > > > > 1. Is it possible and recommended to implement Yocto into Atmel SAME70 > for IoT application? (Single core CPU:300MHz, RAM: 384KB, Program Memory > Size: 2048 KB) > > 2. Any example/past project of Yocto running on Atmel SAME70? > > > > Appreciate your time.Thank you > > > > Regards, > > Rz Charger > > Malaysia > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mono: QA Error building mono-5.12.0.226
On 22/11/2018 15:46, Martin Townsend wrote:
Hi,
This one is probably for the meta-mono maintainer
I was getting quite a few file-rdeps QA errors.
I managed to get rid of them all except 1 using
RDEPENDS_${PN}-libs-2.0 += "mono"
RDEPENDS_${PN}-libs-3.5 += "mono"
RDEPENDS_${PN}-libs-4.0 += "mono"
RDEPENDS_${PN}-libs-4.5 += "mono"
RDEPENDS_${PN}-gac += "mono"
RDEPENDS_${PN}-configuration-crypto += "mono"
RDEPENDS_${PN}-xbuild += "mono"
RDEPENDS_${PN}-api-4.5.1 += "mono"
RDEPENDS_${PN}-api-4.5.2 += "mono"
RDEPENDS_${PN}-api-4.6 += "mono"
RDEPENDS_${PN}-api-4.6.1 += "mono"
RDEPENDS_${PN}-api-4.6.2 += "mono"
RDEPENDS_${PN}-api-4.7 += "mono"
The one remaining is
ERROR: mono-5.12.0.226-r0 do_package_qa: QA Issue:
/usr/lib/mono/4.5/Microsoft.CodeAnalysis.Scripting.dll contained in
package mono-libs-4.5 requires mono(System.Runtime.Loader), but no
providers found in RDEPENDS_mono-libs-4.5? [file-rdeps]
ERROR: mono-5.12.0.226-r0 do_package_qa: QA run found fatal errors.
Please consider fixing them.
ERROR: mono-5.12.0.226-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/ws/rufilla/oina/tools-oina-build-local/build_oxinst/tmp/work/armv7ahf-neon-poky-linux-gnueabi/mono/5.12.0.226-r0/temp/log.do_package_qa.15001
ERROR: Task
(/ws/rufilla/oina/tools-oina-build-local/build_oxinst/../meta-mono/recipes-mono/mono/mono_5.12.0.226.bb:do_package_qa)
failed with exit code '1'
It looks like the 4.5 lib package requires the System.Runtime.Loader
library but I'm not sure how to get it to build this or I see there is
an external directory which looks like it contains all the 4.5 libs so
maybe it hasn't been included in here?
Any Help appreciated,
Martin.
Hi Martin,
I've been doing some recent work here which might help
https://github.com/dynamicdevices/meta-mono/tree/master
Cheers,
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-mono: QA Error building mono-5.12.0.226
Hi,
This one is probably for the meta-mono maintainer
I was getting quite a few file-rdeps QA errors.
I managed to get rid of them all except 1 using
RDEPENDS_${PN}-libs-2.0 += "mono"
RDEPENDS_${PN}-libs-3.5 += "mono"
RDEPENDS_${PN}-libs-4.0 += "mono"
RDEPENDS_${PN}-libs-4.5 += "mono"
RDEPENDS_${PN}-gac += "mono"
RDEPENDS_${PN}-configuration-crypto += "mono"
RDEPENDS_${PN}-xbuild += "mono"
RDEPENDS_${PN}-api-4.5.1 += "mono"
RDEPENDS_${PN}-api-4.5.2 += "mono"
RDEPENDS_${PN}-api-4.6 += "mono"
RDEPENDS_${PN}-api-4.6.1 += "mono"
RDEPENDS_${PN}-api-4.6.2 += "mono"
RDEPENDS_${PN}-api-4.7 += "mono"
The one remaining is
ERROR: mono-5.12.0.226-r0 do_package_qa: QA Issue:
/usr/lib/mono/4.5/Microsoft.CodeAnalysis.Scripting.dll contained in
package mono-libs-4.5 requires mono(System.Runtime.Loader), but no
providers found in RDEPENDS_mono-libs-4.5? [file-rdeps]
ERROR: mono-5.12.0.226-r0 do_package_qa: QA run found fatal errors.
Please consider fixing them.
ERROR: mono-5.12.0.226-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/ws/rufilla/oina/tools-oina-build-local/build_oxinst/tmp/work/armv7ahf-neon-poky-linux-gnueabi/mono/5.12.0.226-r0/temp/log.do_package_qa.15001
ERROR: Task
(/ws/rufilla/oina/tools-oina-build-local/build_oxinst/../meta-mono/recipes-mono/mono/mono_5.12.0.226.bb:do_package_qa)
failed with exit code '1'
It looks like the 4.5 lib package requires the System.Runtime.Loader
library but I'm not sure how to get it to build this or I see there is
an external directory which looks like it contains all the 4.5 libs so
maybe it hasn't been included in here?
Any Help appreciated,
Martin.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto layers missing thud branches
Hi there, seems like meta-java also missing a thud branch?! git://git.yoctoproject.org/meta-java Regards, Matthias On 11/18/2018 12:50 AM, akuster808 wrote: > Can the maintainers of meta-qt3, meta-qt4, meta-selinux, and meta-cgl > please add a "Thud" branch > > kind regards, > Armin pEpkey.asc Description: application/pgp-keys -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Forcing GCC version for native compilation
On Thu, 22 Nov 2018 at 07:33, Teemu K wrote: > I have project made for Yocto 1.7, but I'd like to compile it on newer > Linux distribution that default GCC version is 5.x. GCC version itself > causes some problems, because some things have changed. > > There is also GCC 4.8 available, but it's not called 'gcc', but 'gcc-4.8'. > > The question is that is there way to force yocto use 'gcc-4.8' instead > of 'gcc'? I did some searching and couldn't find any options how to do > it. I tried to making link to ~/bin/gcc pointing gcc-4.8 and having > that first in PATH, but that didn't quite work. I'm guessing path got > re-set at some point. > > And before someone says. Updating Yocto to solve problem is not > solution. System is being updated, but current system still needs to > be able to compile. The modern solution is to set BUILD_CC and so on, see bitbake.conf. Note that in such an old release this might not work as well as you'd hope because I don't think it was fully tested. In which case your options in preferred order: 1) Some distributions let you change what the default compiler, for example /usr/bin/gcc might be a symbolic link you can just change. 2) PATH fiddling as you did. You'll most likely need to replace more than just gcc, for example cpp. 3) Just mv /usr/bin/gcc to /usr/bin/gcc-5 (and cpp, and anything else), and symlink gcc -> gcc-4.8 Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
