From: David Huggins-Daines <dhd@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] userland test failure
Date: 29 Jun 2000 11:46:20 -0400 [thread overview]
Message-ID: <874s6csd6b.fsf@linuxcare.com> (raw)
In-Reply-To: Alan Modra's message of "Thu, 29 Jun 2000 14:44:30 +1000 (EST)"
Alan Modra <alan@linuxcare.com.au> writes:
> -fPIC and -shared are not supported at the moment, even with the newer
> binutils-2.10 module available from puffin CVS. With binutils-2.10,
> you'll get a different error if you compile with -fPIC, something like:
> "cannot handle relocation R_PARISC_DLTIND21L for .LC0 at 0x28 in .text"
Would I be correct in assuming that the GCC portion of supporting
-fPIC is more or less done, it's just that the linker can't handle the
relocations generated?
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-06-29 15:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0006270919200.16671-100000@front.linuxcare.com.au>
2000-06-28 18:36 ` [parisc-linux] Recipe Brian S. Julin
2000-06-28 23:21 ` Alan Modra
2000-06-29 3:28 ` [parisc-linux] userland test failure chester
2000-06-29 4:44 ` Alan Modra
2000-06-29 5:01 ` chester
2000-06-29 5:12 ` chester
2000-06-29 5:17 ` Alan Modra
2000-06-29 15:46 ` David Huggins-Daines [this message]
2000-06-29 16:16 ` David Huggins-Daines
2000-06-29 23:13 ` Alan Modra
2000-08-23 17:28 ` [parisc-linux] disk required? Andrew Park
2000-08-23 17:48 ` Andrew Shugg
2000-08-23 18:02 ` Andrew Park
2000-08-23 17:08 ` Matthew Wilcox
2000-08-23 18:10 ` Switch to serial console ( was Re: [parisc-linux] disk required? ) Matt Taggart
2000-08-23 19:05 ` Andrew Park
2000-08-23 19:21 ` Jack Perdue
2000-06-28 19:07 ` [parisc-linux] What? no /bin/uname? :-) Brian S. Julin
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=874s6csd6b.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=alan@linuxcare.com.au \
--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