From: Amy Fong <amy.fong@windriver.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: question on App bitsize - need the same as the kernel (multilib situation)
Date: Wed, 13 Mar 2013 09:50:33 -0400 [thread overview]
Message-ID: <20130313135033.GA31648@windriver.com> (raw)
In-Reply-To: <CF5E1B15-C4C2-454C-82E1-A5214320C4CA@gmail.com>
On Tue, Mar 12, 2013 at 08:25:55PM -0700, Khem Raj wrote:
>
> On Mar 12, 2013, at 8:13 PM, Amy Fong <amy.fong@windriver.com> wrote:
>
> > It may be a combination of kernel ppc64 + userspace ppc (32);
> > or kernel x86-64 + userspace x86-32.
>
>
> I think you to ship ppc64 C runtime at least and same is true for x86_64
> and by bit size you mean machine word length right ? like sizeof(long)
Uhhhh no, what I mean is,
e.g.
For userspace, if 32bit:
root@localhost:~# file /bin/bash
/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.34, stripped
For kernel, if 64bit:
(in kernel config)
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
Take for example, I want to run crash to do some kernel debugging, in this case,
I would want crash to be 64bits.
> > On Tue, Mar 12, 2013 at 03:41:29PM -0700, Khem Raj wrote:
> >>
> >> On Mar 12, 2013, at 2:19 PM, Amy Fong <amy.fong@windriver.com> wrote:
> >>
> >>> I need to build an application that has the same bitsize as the kernel. But in
> >>> my multilib configuration, the default usersapce bitsize is not the same as
> >>> the kernel's bitsize. How do you do this?
> >>
> >> which arch is this ?
> >> since generally we have one in multilib combo that matches kernel bit size
> >> but you might have left it out.
> >>
> >>>
> >>> Thanks!
> >>> Amy
> >>>
> >>> _______________________________________________
> >>> Openembedded-devel mailing list
> >>> Openembedded-devel@lists.openembedded.org
> >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >>
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2013-03-13 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 21:19 question on App bitsize - need the same as the kernel (multilib situation) Amy Fong
2013-03-12 22:32 ` Khem Raj
2013-03-12 22:41 ` Khem Raj
2013-03-13 3:13 ` Amy Fong
2013-03-13 3:25 ` Khem Raj
2013-03-13 13:50 ` Amy Fong [this message]
2013-03-13 16:27 ` Mark Hatle
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=20130313135033.GA31648@windriver.com \
--to=amy.fong@windriver.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