From: Theo Gjaltema <gjalt007@chello.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Dynamic libraries do not work
Date: Tue, 31 May 2005 22:29:29 +0200 [thread overview]
Message-ID: <429CC929.5060405@chello.nl> (raw)
In-Reply-To: <E6CEFEB5-1F03-45DA-8BA3-C1F1511950EA@aimsys.nl>
I 've found the problem, the ramdisk used contained executables as well
as dyn. libs from the mpc8260 instead of the mpc862.
I don't know why the whole system came to a halt without any message but
replacing the dyn. libs and executables with the correct ones solved the
problem of crashing.
Many thanks for your responses,
Theo.
Jaap-Jan Boor schreef:
> Theo,
>
> What type of processor are you using? 8xx?
> Did you build a tool-chain yourself and are
> you perhaps using floating point?
>
> Jaap-Jan
>
> On 26-mei-2005, at 23:04, Theo Gjaltema wrote:
>
>> Hello,
>>
>> 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.
>>
>> Greetings,
>> Theo.
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
> ____
> J.G.J. Boor Anton Philipsweg 1
> Software Engineer 1223 KZ Hilversum
> AimSys bv tel. +31 35 689 1941
> Postbus 2194, 1200 CD Hilversum jjboor at aimsys dot nl
>
>
>
prev parent reply other threads:[~2005-05-31 20: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
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 [this message]
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=429CC929.5060405@chello.nl \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.