Dan

dave@dave-Inspiron-1110:~/angstrom-socfpga$ bitbake -e | grep GCCVERSION=
GCCVERSION="linaro-4.9%"
SDKGCCVERSION="linaro-4.9%"
dave@dave-Inspiron-1110:~/angstrom-socfpga$ printenv | grep 2014.*
OE_BUILD_TMPDIR=/home/dave/angstrom-socfpga/build/tmp-angstrom_v2014_12
DISTRO_DIRNAME=angstrom_v2014_12
DISTRO=angstrom-v2014.12


this could have occurred because I was looking at v13.1 compilation which 
probably used the earlier tool  versions.

I  googled updating environment for angstrom 2014.12 to 2015 and ended on a 
rocketboards page "compiling Linux-Angstrom v2015.12-Yocto 2.0" which tells you 
how to upgrade via the repo command.


I did a fresh install on another PC at Uni yesterday. When I left uni the 
compilation was running so I'll check later today if that ran ok and update 
this thread later. I'll also try the update on this machine via the repo and 
add that to the thread as well if it's successful.


Charles


Thanks for the buildroot lead. I've just had a quick look at that and it looks 
interesting, so I'll have a digest once I've checked the previous topics.


Regards


Dave

________________________________
From: Charles Manning <[email protected]>
Sent: 09 June 2016 20:54:07
To: Dan Negvesky
Cc: Dave Burke (PGR); [email protected]
Subject: Re: [Rfi] Issues with setting up Yocto build for SoCkit

You might also want to look at buildroot.

It is way, way simpler and faster than Yocto.


On Fri, Jun 10, 2016 at 6:03 AM, Dan Negvesky 
<[email protected]<mailto:[email protected]>> wrote:
Dave,

I rebuilt everything following the rocketboards instructions just to make sure 
nothing broke and mine completed with no errors.

I’ve Google’d your error and what I found leads me to believe it might be 
toolchain version related.  I built with linaro-4.9.  Assuming you still have 
your bitbake environment setup in your terminal, can you run

bitbake –e | grep GCCVERSION=

and see what it reports?

I believe it’s pulling this from 
/sources/meta-angstrom/conf/distro/angstrom-v2014.12.conf.  I’ve used variables 
in my local.conf to set the GCCVERSION for Angstrom 2015.12 using Yocto 2.0 but 
I’ve not done that for 2014.12/1.7.  Maybe someone smarter than me can chime in 
here and tell me if I’m off in the weeds.

Dan

From: Dave Burke (PGR) 
[mailto:[email protected]<mailto:[email protected]>]
Sent: Monday, June 06, 2016 5:11 AM
To: Dan Negvesky; [email protected]<mailto:[email protected]>
Subject: Re: [Rfi] Issues with setting up Yocto build for SoCkit


Hi Dan



Thanks for that! I had originally intended to use v15.1 but when I checked the 
user guides, I didn't twig that the web page format had changed! When I only 
saw the section headings, I thought that the documentation was incomplete! 
After your suggestion to look at the User Guide I then realised there were tabs 
along the top of the page that give the further detail! Duh!!



Anyway I have got far further along with the compilation Pseudo runs and 
compiles to completion at least but I'm left with one error and one warning. 
The error looks to be a double declaration of a hashtable iterator  variable! 
I'll attach the relevant log file.



Your help is greatly appreciated! I feel that I'm finally starting to get 
somewhere. All I have to do now is understand how this all works!![??]



Regards



Dave Burke





________________________________
From: Dan Negvesky <[email protected]<mailto:[email protected]>>
Sent: 03 June 2016 14:24:55
To: Dave Burke (PGR); 
[email protected]<mailto:[email protected]>
Subject: RE: [Rfi] Issues with setting up Yocto build for SoCkit

Dave,

Can I suggest starting with the latest SoCKit GSRD v15.1 available here:

https://rocketboards.org/foswiki/view/Documentation/GSRD151UserManualArrowSoCKitEdition

and kernel/rootfs build instructions here:

https://rocketboards.org/foswiki/view/Documentation/GSRD151UserManualArrowSoCKitEdition

Let us know if you still encounter problems using the latest version.

Dan

From: Dave Burke (PGR) [mailto:[email protected]]
Sent: Friday, June 03, 2016 5:52 AM
To: [email protected]<mailto:[email protected]>
Subject: [Rfi] Issues with setting up Yocto build for SoCkit


Hi



I'm currently working my way through familiarisation with the software build 
process for the Altera Cyclone V SoCkit, with the aim of getting it all under 
the control of EDS in order to move on to compiling software to be run as a 
linux app on the SoCkit.



I was following the recipe as in the documentation GSRDv13.1 - Yocto user 
manual.

Got the source package ok.

Setup the Yocto environment OK.

Tried to build with "bitbake virtual/kernel" and got the following

"Pseudo is not present but is required, building this first before the main 
build
ERROR: Failed to obtain external Linaro toolchain version: Execution of 
'/opt/altera-linux/linaro/gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux/bin/arm-linux-gnueabihf-gcc
 -v' failed with exit code 127:
/opt/altera-linux/linaro/gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux/bin/arm-linux-gnueabihf-gcc:
 error while loading shared libraries: libstdc++.so.6: cannot open shared 
object file: No such file or directory
"

I searched for "Pseudo is not present" and got various web based solutions of 
incantations which didn't work and eventually tracked it down to 
https://rocketboards.org/foswiki/view/Documentation/YoctoDoraBuildWithMetaAltera.

I trustingly followed the incantations to install poky as given in the section 
"Yocto 2.0 Jethro" finishing with

"source poky/oe-init-build-env ./build", got all the correct messages back and 
therefore ran "bitbake virtual/kernel"

This ran to completion after two or three hours and all seemed ok. I tried 
"bitbake altera-gsrd-image" and ended up with an error.

I realised from the following part of the document that I needed to configure 
the bblayers.conf. I then also realised that in configuring Pseudo that I had 
generated an extra /build directory below the existing /build , ie 
~/yocto/build/build! I had a conf directory in both build dirs. Checking the 
bblayers showed the upper one set for fpga and the lower one for x86. I tried 
to correct this by running "source poky/oe-init-build-env ." from ~/yocto/build 
but it came back with a message that the Pseudo environment is already set up!



How can I get out of this?



I archived the yocto directory in case I need to go back to it. I reasoned that 
I might need to install Pseudo before installing the yocto source package, so 
started again with a fresh yocto directory. That was unsuccessful as I think 
there may be things set in the etc/ path that thinks everything is already 
installed!!



Help!!



Regards



Dave Burke

MSc, C Eng, MIET

[email protected]<mailto:[email protected]>

[email protected]<mailto:[email protected]>


_______________________________________________
Rfi mailing list
[email protected]<mailto:[email protected]>
http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi


_______________________________________________
Rfi mailing list
[email protected]
http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi

Reply via email to