Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Martin Ertsås" <mertsas@cisco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Moving pkg.m4 to the x86 sysroot instead of arm sysroot in toolchain
Date: Mon, 23 Jul 2012 11:43:30 +0200	[thread overview]
Message-ID: <500D1CC2.8090502@cisco.com> (raw)
In-Reply-To: <500D0F6D.70001@cisco.com>

The issue was quite simple. My thoughts were correct, but should add
pkgconfig-nativesdk-dev to task-sdk-host-nativesdk.

- Martin

On 07/23/12 10:46, Martin Ertsås wrote:
> Hi.
>
> When building meta-toolchain, pkg.m4 is put in the arm sysroot of the
> toolchain, instead of the x86 sysroot where it belongs. pkg-config is in
> the x86 directory, and when it is in the arm directory, we need to hack
> the aclocal flags to point to it for stuff to compile.
>
> I have tried a few things, like adding pkgconfig-nativesdk to the
> task-sdk-host-nativesdk and pkgconfig to task-core-standalone-sdk. From
> my understanding, the former should populate the x86 directory, but
> obviously it didn't. Any ideas to what I can do to fix this? It would be
> greatly appreciated.
>
> Best regard
> Martin Ertsaas
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




      reply	other threads:[~2012-07-23  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  8:46 Moving pkg.m4 to the x86 sysroot instead of arm sysroot in toolchain Martin Ertsås
2012-07-23  9:43 ` Martin Ertsås [this message]

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=500D1CC2.8090502@cisco.com \
    --to=mertsas@cisco.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