All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: "Neulinger, Nathan" <nneul@umr.edu>
Cc: "'Matthew Wilcox'" <willy@debian.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Status of hp-ux binary compatibility?
Date: 01 Oct 2001 11:51:37 -0400	[thread overview]
Message-ID: <m3elonmk8m.fsf@trained-monkey.org> (raw)
In-Reply-To: "Neulinger, Nathan"'s message of "Mon, 1 Oct 2001 10:40:47 -0500"

>>>>> "Nathan" == Neulinger, Nathan <nneul@umr.edu> writes:

Nathan> As far as I know, flexlm should be a pretty basic socket
Nathan> server, nothing fancy, other than it's retrieval of the HP
Nathan> host id, which I presume is just a syscall of some
Nathan> sort. Unfortunately, it does require use of shared lib libc
Nathan> since that's how it was linked.

Hmmm, admittedly I know little about the HPUX shared linker. However
even then I don't think it should be too big of a problem, provided
Linux/HPPA is able to map binaries at the same place as HPUX.

Jes

  reply	other threads:[~2001-10-01 15:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 15:40 [parisc-linux] Status of hp-ux binary compatibility? Neulinger, Nathan
2001-10-01 15:51 ` Jes Sorensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-01 15:30 Neulinger, Nathan
2001-10-01 13:35 Neulinger, Nathan
2001-10-01 15:33 ` Matthew Wilcox
2001-10-01 13:31 Neulinger, Nathan
2001-10-01 13:41 ` Matthew Wilcox
2001-10-01 15:33 ` Alan Cox
2001-10-01 15:38 ` Jes Sorensen
2001-10-01 13:17 Neulinger, Nathan
2001-09-28 19:02 Neulinger, Nathan
2001-09-29 12:10 ` Richard Hirst
2001-09-28 17:35 Nathan Neulinger
2001-09-28 18:31 ` Richard Allen
2001-10-01  4:19 ` Matthew Wilcox
2001-10-01 12:47   ` Nathan Neulinger
2001-10-01 13:25     ` Matthew Wilcox

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=m3elonmk8m.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=nneul@umr.edu \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.