iMX6 LTIB glibc-devel

cancel
Showing results for 
Search instead for 
Did you mean: 

iMX6 LTIB glibc-devel

1,666 Views
JohnCannizzo
Contributor III

Hi All,

I'm building ltib on the iMX6 SDB to get kernel headers for drivers. I'm building on the board (not on the PC) for many reasons, mainly due to several 100K lines of legacy code.  I installed all the packages, including build-essential.  I modified Ltibutils.pm to add -f '/lib/arm-linux-gnueabi/libm.so' to the glibc-devel line.  libc.so.6 and libm.so.6 exist in /lib/arm-linux-gnueabi, so it looks like glibc-devel is installed.  Yet, when I run ./ltib -m config, it still shows glibc-devel not installed, Died at ./ltib line 1409.  Did I make the change in Ltibutils.pm incorrectly (I searched the forum before making the change), or is there possibly something else wrong?  Making the similar change for zlib did solve the issue with that library.  Any help would be most appreciated.

As an additional question, I'm seeing much discussion on the forums about the switch to Yocto.  When is the right time to switch?  It appears to be an easier development environment, but I've already built my app under previous ltib versions.  Is the kernel the same?  Is the performance better under Yoctu?  If there is already a discussion comparing ltib and Yacto, could you please point me to it?  Thanks...


Labels (2)
7 Replies

506 Views
robertzhang
Contributor I

what's different yacto and ltib?on the last yesterday, i hear about the yacto can get package that lastest, but the ltib only get it at special place and old.

0 Kudos

506 Views
LeonardoSandova
Specialist I

Robert, I did not get your question. Yocto (not Yacto, in fact it should be written Yocto Project :smileyhappy: )  has much more community members, so you will find recent version on most common packages compared to LTIB. Is that what you mean? A good place to find layers/recipes/machines is here:

OpenEmbedded metadata index - layers

Leo

0 Kudos

506 Views
FranciscoCarril
Contributor V

LeonardoSandovalGonzalez Has some documents regarding ltib  and Yocto comparations.

In summary,  BSPs will only be released  as Yocto in the near future, so it is a good time to switch.

0 Kudos

506 Views
LeonardoSandova
Specialist I

My document is more command line related (engine's parameters oriented). It is incomplete, but here is it

https://community.freescale.com/docs/DOC-94874

0 Kudos

506 Views
LeonardoSandova
Specialist I

Q When is the right time to switch?

A is your product already on the market? if no, then it would be worth trying your code with yocto.

Q It appears to be an easier development environment, but I've already built my app under previous ltib versions.

A Neither Yocto nor LTIB are development environments; the development cycle should be done separate and once you have something solid, then create a tiny recipe indicating the build system how to bake your stuff. bitbake likes git, so try to keep your code controlled with it. Also, create a new layer for all your stuff.

Q Is the kernel the same?

A You can tell Yocto which one you want. For iMX6, it has 3.0.35, 3.5.7 and 3.10.9. More info on http://freescale.github.io/doc/release-notes/1.5/

Q Is the performance better under Yoctu?

A What do you mean? Build, boot, system performance?

Q If there is already a discussion comparing ltib and Yacto, could you please point me to it?

A https://lists.yoctoproject.org/pipermail/meta-freescale/2013-October/005206.html

506 Views
sinanakman
Senior Contributor III

Hi John, as an alternative you can just compile the mainline recent kernel 3.11+ and have root file system built with buildroot. This is what I am running on my sabre sd board. I didn't include any video or graphic packages but for an headless configuration it works fine for me. Let me know if you need more info or if I can be of any further help.

Thanks

Sinan Akman

0 Kudos

506 Views
JohnCannizzo
Contributor III

Hi Sinan,

Thank you for the reply.  My application requires an X server be running, so I can't go headless.  Partially, it renders to windows on the attached display.  I know this is a simple problem with a simple fix, but I have yet to find that answer...

Thanks again...

0 Kudos