From: Matthias Reis <matthias.reis@hu-berlin.de>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: Crash in entry.S:resume on Atari ST
Date: Fri, 16 Sep 2016 15:53:08 +0200 [thread overview]
Message-ID: <20160916135307.GA6030@hu-berlin.de> (raw)
In-Reply-To: <7d38f54e-4b7a-af7b-3cc8-15be7369f0e4@linux-m68k.org>
Hi Greg,
On Fri, Sep 16, 2016 at 04:39:06PM +1000, Greg Ungerer wrote:
> What procedure did you follow to build your apps?
In short, I used the -m68000 gcc switch and set the following options:
uClibc .config:
TARGET_ARCH="m68k"
# UCLIBC_FORMAT_FLAT is not set
UCLIBC_FORMAT_FLAT_SEP_DATA=y
# UCLIBC_FORMAT_SHARED_FLAT is not set
busybox .config:
CONFIG_STATIC=y
# CONFIG_PIE is not set
CONFIG_NOMMU=y
The full details can be found under:
https://ford.biologie.hu-berlin.de/matze/linux-m68k-atarinommu/uploads/22f7c78b30c92605adcc8dc40af3220e/build-binutils-gcc-uClibc-busybox.tar.bz2
In the tarball, you can there is a script that should include all steps,
including the ./configure options, as well as all .config's.
> Are you using flat format binaries?
$ ./flthdr ../busybox/busybox_unstripped
../busybox/busybox_unstripped
Magic: bFLT
Rev: 4
Build Date: Mon Sep 5 16:26:38 2016
Entry: 0x44
Data Start: 0x20eb4
Data End: 0x25238
BSS End: 0x27ae0
Stack Size: 0x3e80
Reloc Start: 0x25238
Reloc Count: 0x73
Flags: 0x2 ( Has-PIC-GOT )
> So is this crashing at the step of trying to load and run the
> first user app?
It happens after run_init_process() is called.
Thanks!
Matthias
next prev parent reply other threads:[~2016-09-16 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 22:35 Crash in entry.S:resume on Atari ST Matthias Reis
2016-09-16 6:39 ` Greg Ungerer
2016-09-16 13:53 ` Matthias Reis [this message]
2016-09-16 9:29 ` Andreas Schwab
2016-09-16 14:23 ` Andreas Schwab
2016-09-16 14:47 ` Matthias Reis
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=20160916135307.GA6030@hu-berlin.de \
--to=matthias.reis@hu-berlin.de \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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.