All of lore.kernel.org
 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: Thu, 24 Nov 2011 14:26:42 +0000	[thread overview]
Message-ID: <4ECE5422.3070504@googlemail.com> (raw)
In-Reply-To: <4ECE4B0D.6030401@googlemail.com>


> Any ideas why OE can't find my ppl_c libs?
Further to my previous post, the gcc prerequisites are clearly stated 
here -> http://gcc.gnu.org/install/prerequisites.html. Both PPL and 
CLooG are in that list. I have just looked at my OE source directory and 
I could see that neither of these packages have been downloaded during 
the OE build. These are not present in the gcc svn tree either.

Is it possible that the OE build might have missed them and that is why 
it fails? I know that there are two ways to include them for the gcc 
build - either as a subdirectory to the main tree (libppl/ and 
libcloog/) in which case gcc builds them "automatically" or build them 
separately as static libs and then point to these during the actual gcc 
build.

Am I missing something here or is this a bug?



  reply	other threads:[~2011-11-24 14:33 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 [this message]
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
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=4ECE5422.3070504@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 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.