All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Cross building question
Date: Wed, 19 Jun 2013 15:03:17 +0100	[thread overview]
Message-ID: <51C1BA25.6080200@mlbassoc.com> (raw)

I'm asking on this list since this is a pretty general question.
If it's more appropriate for another venue, just let me know.

I'm trying to build a new package for my target which has never
been ported to OpenEmbedded/Yocto/...  (It's the Amanda backup
server if anyone has ever looked at this).  The code is a
giant mass that I'd hoped not to have to delve into very deeply.
Basic configuration (autoolized) went well, but one of the
first things it wants to do is run a [target] program which
has been linked against the [target] libraries that were just
built.  In this case, it's just a utility to interrogate the
libraries and CONFIG.h files and print a user summary.

What's the best way to handle this and how?  I recall in the
dark old days that there were many such things that relied on
running QEMU to actually execute target code.  Is this still
possible (and being done)?  If so, is that a solution and how
might I force it to happen?

It may turn out that this is just a small problem that I can
patch my way through, but I fear there may be other such utilities
that get built and used, so I'd like to understand my way forward.

Thanks for any pointers/ideas

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2013-06-19 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 14:03 Gary Thomas [this message]
2013-06-19 14:14 ` Cross building question Burton, Ross
2013-06-19 14:39   ` Gary Thomas
2013-06-19 14:52     ` Burton, Ross
2013-06-19 15:25       ` Gary Thomas
2013-06-19 15:32         ` Burton, Ross

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=51C1BA25.6080200@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@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.