From: Matt Taggart <taggart@carmen.fc.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Native compiler doesn't work with new kernel
Date: Fri, 29 Dec 2000 18:06:46 -0700 [thread overview]
Message-ID: <20001230010646.750FF37C97@carmen.fc.hp.com> (raw)
In-Reply-To: Message from Matt Taggart <taggart@carmen.fc.hp.com> of "Wed, 27 Dec 2000 15:41:53 MST." <20001227224153.5F22637C97@carmen.fc.hp.com>
Matt Taggart writes...
> It seems to just be the xcompiled static bash I built. I xcompiled sash and it
> worked ok. I setup an nfsroot with a bunch of stuff I had cross-compiled and
> except for bash and a couple other things, it's working normally. I will try
> compiling bash native and see if that helps.
OK, since I have a mostly-working nfsroot and a cross-built toolchain I tried
running gcc. I just tried "gcc -o hello hellow.c" where hellow.c is the hello
world program from cvs->userspace. The compiler dies with signal 6(abort). The
system is also pretty erratic, sometimes the prompt takes a few minutes to
return.(once with an out-of-memory error)
Someone suggested that I try an older kernel from before the stack changes
were made eariler this month, so I tried an old kernel I had around(built with
an old xc). Now gcc gets a little further, but dies with,
------------------------------------------------------------------------------
do_page_fault() pid=18 command='ld'
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001011
r0-3 00000000 fffffff4 000368d7 00107060
r4-7 00000005 000ef790 00125368 00000000
r8-11 000e3438 00000000 00105ca0 00000031
r12-15 000d9ea8 00000000 00107060 000e3120
r16-19 000fa0c0 00106838 00000000 00000000
r20-23 001067e8 00000000 0002cc50 00107060
r24-27 000fa0c0 000d9ea8 000e3120 000d7770
r28-31 00105ca0 00000002 20020500 000368d7
sr0-4 00000000 00000004 00000000 00000004
sr4-8 00000004 00000004 00000004 00000004
IASQ: 00000004 00000004 IAOQ: 0002d5bf 0002d5c3
IIR: 0e752087 ISR: 00000004 IOR: 00000000
ORIG_R28: 00000000
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
------------------------------------------------------------------------------
I also wanted to try the older kernel bits built with the new xc but I
couldn't remember the -ffunction-section magic to make it work.
If other people want to play with this I have put my new nfsroots at,
ftp://puffin.external.hp.com/pub/parisc/debug/base-20001227.tar.gz [25MB]
ftp://puffin.external.hp.com/pub/parisc/debug/nfsroot-20001227.tar.gz [59MB]
--
Matt Taggart
taggart@fc.hp.com
next prev parent reply other threads:[~2000-12-30 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 1:07 [parisc-linux] Same boot problem on a 9000/720/50 HP machine as on 712/60 of Niskanen Christoph Plattner
2000-12-27 1:27 ` Matt Taggart
2000-12-27 4:34 ` Matt Taggart
2000-12-27 20:59 ` Matt Taggart
2000-12-27 22:41 ` Matt Taggart
2000-12-30 1:06 ` Matt Taggart [this message]
2000-12-27 19:05 ` Christoph Plattner
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=20001230010646.750FF37C97@carmen.fc.hp.com \
--to=taggart@carmen.fc.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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