From: Grant Grundler <grundler@cup.hp.com>
To: Cary Coutant <cary@cup.hp.com>
Cc: law@redhat.com, "John David Anglin" <dave@hiauly1.hia.nrc.ca>,
"Alan Modra" <alan@linuxcare.com.au>,
bame@fc.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] where to put 64 bit libmilli?
Date: Thu, 04 Jan 2001 11:15:44 -0800 [thread overview]
Message-ID: <200101041915.LAA29838@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 04 Jan 2001 11:00:49 PST." <200101041902.LAA22273@adlmail.cup.hp.com>
Cary Coutant wrote:
> Linux shouldn't need to be concerned with either of these cases. If
> you're using $$dyncall for the 32-bit runtime, I strongly suggest that
> you change the compiler.
Where does support for HPUX built apps fit into the picture?
I thought a long term goal is to support HPUX built apps to run under
parisc-linux. Eg it would be really cool if we could run the HPUX
X11 server...
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
next prev parent reply other threads:[~2001-01-04 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 19:00 [parisc-linux] where to put 64 bit libmilli? Cary Coutant
2001-01-04 19:15 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 21:20 Cary Coutant
2001-01-02 19:25 Paul Bame
2001-01-02 19:39 ` John David Anglin
2001-01-02 19:58 ` Paul Bame
2001-01-02 20:17 ` Jeffrey A Law
2001-01-03 1:46 ` Alan Modra
2001-01-03 1:57 ` Matthew Wilcox
2001-01-03 2:34 ` Alan Modra
2001-01-03 3:37 ` Jeffrey A Law
2001-01-03 4:11 ` Alan Modra
2001-01-03 4:15 ` Jeffrey A Law
2001-01-03 4:44 ` Alan Modra
2001-01-04 4:04 ` Jeffrey A Law
2001-01-04 5:20 ` Alan Modra
2001-01-04 6:18 ` John David Anglin
2001-01-04 7:03 ` Alan Modra
2001-01-04 16:36 ` Paul Bame
2001-01-04 17:06 ` Jeffrey A Law
2001-01-04 17:29 ` Jeffrey A Law
2001-01-04 17:37 ` Jeffrey A Law
2001-01-04 17:41 ` Paul Bame
2001-01-04 23:52 ` 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=200101041915.LAA29838@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=alan@linuxcare.com.au \
--cc=bame@fc.hp.com \
--cc=cary@cup.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=law@redhat.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