From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: "MЕns RullgЕrd" <mru@users.sourceforge.net>
Cc: jlnance@intrex.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc1 broke OSF binaries on alpha
Date: Tue, 2 Jul 2002 19:05:44 +0400 [thread overview]
Message-ID: <20020702190544.A23788@jurassic.park.msu.ru> (raw)
In-Reply-To: <yw1xvg7z1bjz.fsf@gladiusit.e.kth.se>; from mru@users.sourceforge.net on Mon, Jul 01, 2002 at 09:40:48PM +0200
On Mon, Jul 01, 2002 at 09:40:48PM +0200, MЕns RullgЕrd wrote:
> Using the libraries from the tru64 5.0 install CD works fine for
> running programs on that CD. There does seem to be some problems with
> different library versions, though. Matlab 5 would not run with libc
> from the tru64 5.0 CD. I had to get some other ones. With the right
> libraries Matlab runs fine with both 2.4.19-rc1 and earlier.
Unfortunately the libraries _officially_ available for linux are
from v4. If HP would release something more up to date, the alpha
iov_len hack would go away.
It looks like in the Tru64 v5 readv/writev compatibility issues
are solved on the libc level. Default (SuS compliant) functions
are _Ereadv/_Ewritev, and readv/writev are just wrappers (clearing
top 32 bits of iov_len) for old binaries.
Ivan.
next prev parent reply other threads:[~2002-07-02 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 10:54 Ivan Kokshaysky
2002-06-28 20:31 ` Marcelo Tosatti
2002-06-29 2:28 ` Alan Cox
2002-06-29 23:50 ` Ivan Kokshaysky
2002-07-01 7:54 ` Kurt Garloff
2002-07-01 16:17 ` Jeff Garzik
2002-07-01 13:03 ` jlnance
2002-07-01 14:02 ` Ivan Kokshaysky
2002-07-01 19:40 ` Måns Rullgård
2002-07-02 15:05 ` Ivan Kokshaysky [this message]
2002-07-02 23:13 ` Richard Henderson
2002-07-03 0:31 ` Ivan Kokshaysky
2002-06-29 2:26 ` Alan Cox
2002-06-29 22:45 ` Ivan Kokshaysky
2002-07-02 20:56 ` Marcelo Tosatti
2002-06-29 4:39 Chris Adams
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=20020702190544.A23788@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=jlnance@intrex.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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
all inboxes | Powered by JetHome®