From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laszlo Papp <lpapp@kde.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Specifying 32 bit dependency for 64 bit software
Date: Tue, 04 Nov 2014 11:48:41 +0000 [thread overview]
Message-ID: <1415101721.23396.20.camel@ted> (raw)
In-Reply-To: <CAOMwXhPbXCQ7ui+J0a8ryekeq5Yy5EXdgt-Qr26Z9w74=vyD5w@mail.gmail.com>
On Mon, 2014-11-03 at 17:29 +0000, Laszlo Papp wrote:
> we have a tool that we run during our make run, but this tool is
> hard-coded for 32 bit. It depends on software like ncurses. I could
> add ncurses-native in an ideal world; no problem.
>
> The problem is that my host environment is 64 bit currently and it is
> not possible to migrate the whole environment to 32 bit. I am happy to
> explain the details if needed, but I would love you to trust me about
> that. =)
>
> So, is it possible to say more than just DEPENDS = ncurses-native,
> something like DEPENDS = ncurses-native:x86 or something?
How much of a 32 bit system do you have? Do you at least have a 32 bit
capable compiler and C libraries?
If so, you could use our general class extension mechanism
(BBCLASSEXTEND) to allow 32 bit variants of the native recipes, e.g. a
"native32" form.
Alternatively, a more easier approach would be to build a target like
buildtools-tarball with SDKMACHINE="i686" and then install that onto the
system you're building on.
Cheers,
Richard
next prev parent reply other threads:[~2014-11-04 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 17:29 Specifying 32 bit dependency for 64 bit software Laszlo Papp
2014-11-03 17:32 ` Laszlo Papp
2014-11-04 11:48 ` Richard Purdie [this message]
2014-11-20 18:17 ` Laszlo Papp
2015-01-05 12:48 ` Laszlo Papp
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=1415101721.23396.20.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=lpapp@kde.org \
--cc=openembedded-core@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.