From: David Huggins-Daines <dhd@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Cary Coutant <cary@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Incompatibility of PIC and non-PIC
Date: 12 Sep 2000 23:17:18 -0400 [thread overview]
Message-ID: <87og1tkmkh.fsf@linuxcare.com> (raw)
In-Reply-To: Alan Modra's message of "Wed, 13 Sep 2000 11:30:18 +1100 (EST)"
Alan Modra <alan@linuxcare.com.au> writes:
> That's not too bad a hack. I took a different approach and generate
> import stubs when PIC code is detected during a static link. David, is
> there some problem with this (or was this a very old email that Cary was
> replying to)?
Very old email, I think. I don't see a problem with the way we do it
either, though. Half dozen of one, six of the other...
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-09-13 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-12 20:39 [parisc-linux] Incompatibility of PIC and non-PIC Cary Coutant
2000-09-13 0:30 ` Alan Modra
2000-09-13 3:17 ` David Huggins-Daines [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-17 22:25 David Huggins-Daines
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=87og1tkmkh.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=cary@cup.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