Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: "cannot find -lppl_c" link error
Date: Fri, 25 Nov 2011 05:32:55 +0000	[thread overview]
Message-ID: <4ECF2887.2040400@googlemail.com> (raw)
In-Reply-To: <20111125050922.GA30623@sakrah.homelinux.org>

>> That did not work, unfortunately - "perl ./Configure" doesn't like these:
> 
> well where did you add them ? they should ONLY be added for gcc-cross
> recipe
Well, considering my OE experience is just a few days old (if you can call it that), I placed this in my local.conf file. Then I realised I should put it with the failed task recipe (gcc-4.5-initial) and then by looking at the actual file itself I realised that the gcc-4.5.bb is the place to go. 

I have just finished my built - the whole lot and with a lot of warnings, mainly from unpackaged files - don't know whether these are important though.

I'll probably spend the weekend fine-tuning this as my build went over 25G in size - massive! Thanks for your help Raj, much appreciated!



  reply	other threads:[~2011-11-25  5:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 21:07 "cannot find -lppl_c" link error Mr Dash Four
2011-11-24  2:54 ` Khem Raj
2011-11-24 13:47   ` Mr Dash Four
2011-11-24 14:26     ` Mr Dash Four
2011-11-24 17:49       ` Khem Raj
2011-11-24 18:06         ` Mr Dash Four
2011-11-24 18:27           ` Khem Raj
2011-11-25  0:52             ` Mr Dash Four
2011-11-25  5:09               ` Khem Raj
2011-11-25  5:32                 ` Mr Dash Four [this message]
2011-11-25 17:26                   ` Khem Raj
2011-11-25 21:50                     ` Mr Dash Four
2011-11-28 20:41                     ` Mr Dash Four

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=4ECF2887.2040400@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox