From: Randolph Chung <randolph@tausq.org>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] segfaults with new binutils
Date: Sun, 11 Mar 2001 09:55:48 -0700 [thread overview]
Message-ID: <20010311095548.W18113@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0103111254230.23407-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Sun, Mar 11, 2001 at 01:55:45PM +1100
> You've already started down the path to recovery:
> build and install binutils with --disable-shared,
> build and install gcc with --enable-languages=c --disable-shared,
> build and install glibc
trying to do this last step, but am getting some pretty odd results.
when trying to build linuxthreads, the glibc compile dies when trying to
assemble linuxthreads/crti.S
in particular, it doesn't like the first and last instructions in the
following fragment:
addil LT'.LC0,%r19
stw %r2,-20(%r30)
ldo 64(%r30),%r30
ldw RT'.LC0(%r1),%r1
i thought LT and RT were #define's of some sort, but i don't see them
defined any place.
it's also complaining about .init and .fini. From what I gather the
compile takes pt-initfini.c, translates it to a .S file, then does some
sed magic to remove some sections. This leaves a .S that has a .PROC and
.ENTRY for .init/.fini without a corresponding .EXIT and .PROCEND
i tried this both with gcc 2.96 and 2.97... wonder what's going on...
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-03-11 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 16:39 [parisc-linux] segfaults with new binutils Randolph Chung
2001-03-10 17:21 ` Randolph Chung
2001-03-11 2:55 ` Alan Modra
2001-03-11 3:31 ` Alan Modra
2001-03-11 12:50 ` Matthew Wilcox
2001-03-11 16:49 ` Randolph Chung
2001-03-11 23:44 ` Alan Modra
2001-03-11 16:55 ` Randolph Chung [this message]
2001-03-11 23:41 ` Alan Modra
2001-03-12 4:31 ` Jes Sorensen
2001-03-12 4:55 ` Alan Modra
2001-03-12 5:04 ` Randolph Chung
[not found] <Pine.LNX.4.21.0103141045320.27636-100000@front.linuxcare.com.au>
2001-03-14 0:22 ` Alan Modra
2001-03-14 4:24 ` Alan Modra
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=20010311095548.W18113@tausq.org \
--to=randolph@tausq.org \
--cc=alan@linuxcare.com.au \
--cc=parisc-linux@parisc-linux.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