Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: willy@thepuffingroup.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HP-UX application support?
Date: Mon, 28 Feb 2000 14:55:49 -0800	[thread overview]
Message-ID: <200002282255.OAA07382@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 28 Feb 2000 17:04:46 PST." <20000228170446.Z9944@thepuffingroup.com>

willy@thepuffingroup.com wrote:

> > And, what about the install location of HP-UX shlibs required for these
> > 64-bit (and 32-bit?) HP-UX applications?
> 
> If we use a dynamically linked application, they would need to be placed
> in the same location that HP/UX requires them to be.

On HP-UX "SHLIB_PATH" envirment variables helps the dynamic linker
find shared libaries. Something equivalent for linux?

> However,
> it wouldn't be the recommended way; packaging products as rpm or dpkg
> (depending which distribution we pick) would be the preferred way to go.

If we can make .depot installs work, we could pull alot of stuff
from the porting center for starters. And it would also allow folks
to publish binaries for both OS's in a common format. That might not
be interesting to "real" linux hackers. But to folks using HP-UX, it
would make the transition to linux easier.

grant

Grant Grundler
Unix Development Lab
+1.408.447.7253

  parent reply	other threads:[~2000-02-28 23:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-28 21:14 [parisc-linux] HP-UX application support? MEYER,ALAN C. (HP-FtCollins,ex1)
2000-02-28 22:04 ` willy
2000-02-28 22:26   ` Philipp Rumpf
2000-02-28 22:55   ` Grant Grundler [this message]
2000-02-28 23:26     ` willy
2000-03-12  2:36 ` Steven Pritchard
2000-03-13  9:02   ` Corne Beerse
  -- strict thread matches above, loose matches on Subject: below --
2000-02-28 22:47 FINK,MARTIN (HP-FtCollins,ex1)
2000-02-28 23:04 ` willy
2000-02-29  0:08 MEYER,ALAN C. (HP-FtCollins,ex1)

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=200002282255.OAA07382@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@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