From: Jes Sorensen <jes@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Randolph Chung <randolph@tausq.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] segfaults with new binutils
Date: 12 Mar 2001 05:31:17 +0100 [thread overview]
Message-ID: <d3y9ub6222.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Alan Modra's message of "Mon, 12 Mar 2001 10:41:39 +1100 (EST)"
>>>>> "Alan" == Alan Modra <alan@linuxcare.com.au> writes:
Alan> Huh? My builds don't try to build crti.o for linuxthreads.
Alan> crti.o is built in csu/ from sysdeps/hppa/elf/initfini.c.
Alan> Perhaps you have a configuration problem. What options did you
Alan> pass to configure? Hmm, more importantly, what source are you
Alan> compiling? I don't have a pt-initfini.c in my source tree!
pt-initfini.c was added to glibc-2.2.2 recently, you need it to build
a working LinuxThreads library now. Unless someone has synced the
parisc tree recently it shouldn't be an issue, as long as noone tries
to compile the Cygnus tree for parisc.
Jes
next prev parent reply other threads:[~2001-03-12 4:31 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
2001-03-11 23:41 ` Alan Modra
2001-03-12 4:31 ` Jes Sorensen [this message]
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=d3y9ub6222.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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