From: Wolfgang Denk <wd@denx.de>
To: rekha gvv <rekhagvvc@yahoo.co.in>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Static linking /Shared Library Application Errors.
Date: Tue, 05 Aug 2003 15:21:20 +0200 [thread overview]
Message-ID: <20030805132125.82BB9C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 05 Aug 2003 06:11:12 PDT." <20030805131112.59750.qmail@web8007.mail.in.yahoo.com>
In message <20030805131112.59750.qmail@web8007.mail.in.yahoo.com> you wrote:
>
> I am trying to execute certain fileutils application
> like cp ,ls ..
> These applications are compiled using the Glibc 2.2.3
>
> The problem is if i compile the applications
> Statically
> and try to execute the command cp,ls ..i get the
> segmentation fault error.Please let me know the proper
> compiler options for static linking.
Please explain which toolchain you are yusing, which libraries, and
which versions of the tools listed above.
> OBJS = cat.o chgrp.o chmod.o chown.o cmp.o cp.o dd.o
> grep.o l.o ln.o ls.o \
> mkdir.o mkfifo.o mknod.o more.o mv.o rm.o
> rmdir.o sync.o touch.o vi.o
Where did you get these object files from?
I have a suspicion that these are in fact parets of the busybox
toolbox. If this is correct, then why don't you simply use the
Makefile that comes with busybox?
> Then i tried to eliminate the problem by using shared
> library that is put the ld.so.1 file and libc.so.6
> file in the /lib directory of the ramdisk .
> The problem is the library files are too big in size.
> libc is 5.1mb and ld.so.1 is .5mb
You can strip the shared libraries for the target.
> inorder to create a ramdisk image i have used the
> initrd.sudo scrip file form the denx SELF package.
> : ${IRD_SIZE:=4096k}
>
> dd if=/dev/zero of=$IMAGE bs=$IRD_SIZE count=1
> 2>/dev/null
Again, I have the suspicion that this code comes from our SELF
package. The scripts provided by SELF take care of all the problems
you are running in.
> 1.should i use statick linking
No, this will most probably just increasy your memory footprint.
> 2.shared library ..
Yes.
What I don't understand: there is a working set of tools and scripts.
You rip it apart, omit essential parts, and then complain that it is
not working any more.
What else did you expect?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It is surely a great calamity for a human being to have no ob-
sessions. - Robert Bly
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-05 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 13:11 Static linking /Shared Library Application Errors rekha gvv
2003-08-05 13:21 ` Wolfgang Denk [this message]
2003-08-07 6:53 ` kernel boot up without using PPCBOOT from flash rekha gvv
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=20030805132125.82BB9C59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rekhagvvc@yahoo.co.in \
/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;
as well as URLs for NNTP newsgroup(s).