From: jing han <jing_han_66@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] MSB vs LSB mips library files
Date: Thu, 2 Jul 2009 06:40:15 -0700 (PDT) [thread overview]
Message-ID: <147166.24870.qm@web53506.mail.re2.yahoo.com> (raw)
Hello,
I downloaded buildroot-2009.05.tar.gz and built a mips32r2, o32 environment in my machine (fedora core 5 2.6.15-1.2054_FC5).
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.
I compiled a simple program with mips-linux-gcc which only print "Hello World", the result of "file a.out" is as follows:
a.out: ELF 32-bit MSB executable, MIPS, MIPS64 version 1 (SYSV), dynamically linked (uses shared libs), not stripped
I don't want MSB executables, I want LSB executables. Can you tell me why I have MSB mips library files? What can I do in order to have LSB mips library files and to make my mips executables LSB files?
Could you tell me which option I could choose in order to avoid MSB library files?
Thank you in advance and I'm looking forward to hearing from you soon.
Best Regards
jing
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
next reply other threads:[~2009-07-02 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 13:40 jing han [this message]
2009-07-02 15:34 ` [Buildroot] MSB vs LSB mips library files Thomas Petazzoni
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=147166.24870.qm@web53506.mail.re2.yahoo.com \
--to=jing_han_66@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox