linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Momchil 'Velco' Velikov" <velco@fadata.bg>
To: Brendan.Simon@ctam.com.au
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Linux ABI documents and powerpc supplements.
Date: Wed, 05 Jan 2000 08:46:13 +0200	[thread overview]
Message-ID: <3872E8B5.F088FE57@fadata.bg> (raw)
In-Reply-To: 3872D1EA.DF497905@ctam.com.au


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.

Regards,
-velco

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

  reply	other threads:[~2000-01-05  6:46 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 [this message]
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
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=3872E8B5.F088FE57@fadata.bg \
    --to=velco@fadata.bg \
    --cc=Brendan.Simon@ctam.com.au \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --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).