From: Grant Likely <glikely@gmail.com>
To: Theo Gjaltema <gjalt007@chello.nl>, linuxppc-embedded@ozlabs.org
Subject: Re: Dynamic libraries do not work
Date: Thu, 26 May 2005 16:30:01 -0600 [thread overview]
Message-ID: <528646bc05052615304d896b94@mail.gmail.com> (raw)
In-Reply-To: <429639D5.20609@chello.nl>
On 5/26/05, Theo Gjaltema <gjalt007@chello.nl> wrote:
> Hello,
>=20
> I have a linux 2.4.20 kernel running, but the files in the ramdisk fail
> to execute if they are dynamically build.
> The whole system stops (debuggers shows that it crashed while in an erea
> where no flash/ram is present.
> Anyone an idea?
> There is nog difference between the use of a ramdisk or an nfs mounted
> root filesystem.
>=20
More data please; Make sure you attach actual output when asking for help.
next prev parent reply other threads:[~2005-05-26 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 21:04 Dynamic libraries do not work Theo Gjaltema
2005-05-26 22:30 ` Grant Likely [this message]
2005-05-27 5:36 ` Theo Gjaltema
2005-05-27 6:53 ` Jaap-Jan Boor
2005-05-27 11:58 ` Theo Gjaltema
2005-05-28 0:50 ` Grant Likely
2005-05-31 20:29 ` Theo Gjaltema
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=528646bc05052615304d896b94@mail.gmail.com \
--to=glikely@gmail.com \
--cc=gjalt007@chello.nl \
--cc=linuxppc-embedded@ozlabs.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).