From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.12.0 released
Date: Fri, 18 Jan 2019 09:07:04 +0100 [thread overview]
Message-ID: <20190118080704.vzeiwuwfydus5zd7@pengutronix.de> (raw)
In-Reply-To: <1547456650.5586.14.camel@diehl.com>
Hi,
On Mon, Jan 14, 2019 at 09:04:10AM +0000, Denis OSTERLAND wrote:
> I have tried to run busybox on STM32F469-disco board, but failed with OSELAS 2018.12.0.
> With OSELAS 2018.02.0 it works.
> The kernel complains about a reference to a shared library in the FLAT file.
> I had a look at busybox_unstripped.map to figure out why, but I cant find the
> address modulo page size.
> So I compiled a minimal program (int main() { return 0; }) and used it as
> /sbin/init. Same picture, kernel complains about a reference to a shared library.
> Is it possible that there is a bug in uclinux-ng-1.0.31?
>
> Has someone a hint, how to track down this issue?
I think the linker may be a candidate too. The strange thing is, that there
are no shared libraries in the uclibc toolchain.
I've not done anything with with the uclibc toolchains for some time. I've
just updated the versions for this release. I have no idea where else to
look. Maybe start downgrading the individual components to see which one
causes the problem. I'd start with the linker and uclibc.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-01-18 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 14:49 Michael Olbrich
2018-12-14 14:27 ` Michael Olbrich
2019-01-14 9:04 ` Denis OSTERLAND
2019-01-18 8:07 ` Michael Olbrich [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=20190118080704.vzeiwuwfydus5zd7@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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