linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@kieraypc01.p.y.ki.era.ericsson.se>
To: Brendan.Simon@ctam.com.au
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dynamic binaries not working.
Date: Wed, 05 Jan 2000 13:47:49 +0100	[thread overview]
Message-ID: <38733D74.93A9F24E@switchboard.ericsson.se> (raw)
In-Reply-To: 3872ECED.6E46EBF6@ctam.com.au




Brendan J Simon wrote:

> Momchil 'Velco' Velikov wrote:
>
>
> 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.
> Does this look OK ?
> Any suggestions for debugging the code or the shared libraries ?
>

Have you patched your glibc source so it can work on 860 ??


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-01-05 12:47 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
2000-01-05 12:47         ` Kenneth Johansson [this message]
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=38733D74.93A9F24E@switchboard.ericsson.se \
    --to=ken@kieraypc01.p.y.ki.era.ericsson.se \
    --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).