From: Daniel Jacobowitz <drow@false.org>
To: Brendan J Simon <Brendan.Simon@ctam.com.au>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dynamic binaries not working.
Date: Wed, 5 Jan 2000 03:34:01 -0500 [thread overview]
Message-ID: <20000105033401.A18896@drow.res.cmu.edu> (raw)
In-Reply-To: <3872ECED.6E46EBF6@ctam.com.au>; from Brendan.Simon@ctam.com.au on Wed, Jan 05, 2000 at 06:04:14PM +1100
On Wed, Jan 05, 2000 at 06:04:14PM +1100, Brendan J Simon wrote:
>
> Momchil 'Velco' Velikov wrote:
>
> > Brendan J Simon wrote:
> > > I am having problems getting simple shared executalbes to work on my embedded powerpc system
> > > (MPC860). I am using an egcs-1.1.2 cross compiler and have cross-compiled linux-2.2.5 kernel,
> > > glibc-2.1 and some simple test applications. I have an app that outputs a string every second
> > > using puts(). If I compile with "powerpc-linux-gcc -m860 -static" it works, but if I compile
> > > with "powerpc-linux-gcc -m860 -shared" it doesn't work. I am mount root via nfs and the nfs
> >
> > -shared is used to *create* a shared library. You need -Bdynamic in
> > order to force the executable to be linked against shared libraries.
>
> I removed the -shared argument and the executable now looks a lot better interms of the vaddr and
> program headers etc. I used "powerpc-linux-gcc -Wall -mcpu=860 -fpic -o bjs1 bjs1.c". I tried
> with -fPIC, -fpic and without either. The program still does not run however. The output of
> objdump -p is below.
You should not need -fpic in any form for the binary.
Also, you're using old versions of tools - I really strongly recommend
upgrading. GCC 2.95.2 is worlds better than egcs 1.1.2 was, and the
new binutils (2.9.5.0.x) fix many nasty little bugs.
Nothing below looked wrong to my inexperienced eye...
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-05 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-04 23:00 Linux ABI documents and powerpc supplements Brendan J Simon
2000-01-05 0:23 ` Franz Sirl
2000-01-05 5:08 ` Brendan J Simon
2000-01-05 6:46 ` Momchil 'Velco' Velikov
2000-01-05 6:21 ` Brendan J Simon
2000-01-05 10:19 ` Michael Schmitz
2000-01-05 7:04 ` dynamic binaries not working Brendan J Simon
2000-01-05 8:34 ` Daniel Jacobowitz [this message]
2000-01-05 12:47 ` Kenneth Johansson
2000-01-05 22:24 ` MPC860 patches for glibc Brendan J Simon
2000-01-05 23:36 ` Graham Stoney
2000-01-06 13:18 ` Jesper Skov
2000-01-07 1:44 ` Brendan J Simon
2000-01-08 8:46 ` Jesper Skov
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=20000105033401.A18896@drow.res.cmu.edu \
--to=drow@false.org \
--cc=Brendan.Simon@ctam.com.au \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).