All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] MSB vs LSB mips library files
Date: Thu, 2 Jul 2009 17:34:01 +0200	[thread overview]
Message-ID: <20090702173401.6078dadf@surf> (raw)
In-Reply-To: <147166.24870.qm@web53506.mail.re2.yahoo.com>

Le Thu, 2 Jul 2009 06:40:15 -0700 (PDT),
jing han <jing_han_66@yahoo.com> a ?crit :

> After the make is finished, I checked through the mips files in my
> mips environment, I found that all the files in
> buildroot-2009.05/build_mips/staging_dir/usr/bin/* directory are LSB
> files, all the library files in
> buildroot-2009.05/build_mips/staging_dir/usr/lib/* directory are MSB
> files, which supprise me a lot and I don't want. 

Some of the files in build_mips/staging_dir/usr/bin/ are the
cross-compiler and other cross-compilation tools. So they are compiled
for x86 and generate code for MIPS. Or can you provide an example of a
binary in this directory that is LSB, but not for x86 ?

In build_mips/staging_dir/usr/lib/, are the libraries compiled to run
on the target, so compiled for the MIPS architecture.

> Could you tell me which option I could choose in order to avoid MSB
> library files?

Use mipsel instead of mips ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2009-07-02 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 13:40 [Buildroot] MSB vs LSB mips library files jing han
2009-07-02 15:34 ` Thomas Petazzoni [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=20090702173401.6078dadf@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.