All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Voltz <andy.voltz@timesys.com>
To: "Petr Kubizňák" <kubiznak.petr@elnico.cz>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	max.oss.09@gmail.com
Subject: Re: [meta-fsl-arm] libmcc sysroot issues
Date: Tue, 6 Jan 2015 11:00:24 -0500	[thread overview]
Message-ID: <20150106160024.GA21555@timesys.com> (raw)
In-Reply-To: <54AAE22A.7070905@elnico.cz>

On Mon, Jan 05, 2015 at 02:12:42PM -0500, Petr Kubizňák wrote:
> I'm experiencing sysroot issues with the libmcc library on the latest revision of branch dizzy (2014-12-30, commit 7539a694f3d01f1ab5162bfee16b0327f827c4f7). Not all required files are populated into the SDK, so the library cannot be further used in the application development without manually manipulating the sysroot.
> 
> First of all, compilation of such application fails on the dependency on <linux/mvf_sema4.h> include file, coming from <linux/mcc_config.h>. The mvf_sema4.h file is a part of linux-timesys (3.0.15) kernel (directory include/linux), and should be located in /usr/include/linux in the SDK sysroot. I wanted to create a patch, but did not find an automated solution (as I already described at https://community.freescale.com/message/466383). This issue is not just my case, as you can find for example at the following link: http://developer.toradex.com/how-to/colibri-vf61-real-time-demo-%28xy-pen-plotter%29#Building_the_Qt_User_Interface
> 
> Second (after fixing the first issue manually), linking of such application fails on "-lmcc" flag, as it cannot locate libmcc.so library. In sysroot's /usr/lib, there is only libmcc.so.1.0, but a libmcc.so link is missing. After creating the link manually, the application can build and run as expected.
> 
> I would like to ask for a patch of these two issues, or at least for pointing me to some *brief* resource where I might learn how to create the patch on myself (i.e. what meta-data say yocto how to generate sysroots). Sorry, but studying the whole yocto documentation is just too long run. I spent whole day trying to find a solution with no success.
> 

I'll try a build here to see if I can reproduce the issue you are seeing. Recently this commit b542d3ba472b04fd8759fc34baeda1e7bba31910 addressed some issues with the libmcc install recipes. Copying Max (the commit author) in case this is a familiar issue or perhaps the issue was introduced by that change. 

For docs, I recommend starting with the yocto developers guide.
-- 
Andy Voltz
Timesys Corporation


  reply	other threads:[~2015-01-06 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 19:12 [meta-fsl-arm] libmcc sysroot issues Petr Kubizňák
2015-01-06 16:00 ` Andy Voltz [this message]
2015-01-07 14:41   ` Max Krummenacher
2015-01-07 15:51     ` Otavio Salvador
2015-01-07 19:41       ` Max Krummenacher
2015-01-06 16:32 ` Otavio Salvador
2015-01-07 13:46   ` Petr Kubizňák

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=20150106160024.GA21555@timesys.com \
    --to=andy.voltz@timesys.com \
    --cc=kubiznak.petr@elnico.cz \
    --cc=max.oss.09@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.