public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc1 broke OSF binaries on alpha
Date: Mon, 01 Jul 2002 12:17:10 -0400	[thread overview]
Message-ID: <3D208086.7070603@mandrakesoft.com> (raw)
In-Reply-To: 20020701075418.GA13908@gum01m.etpnet.phys.tue.nl

Kurt Garloff wrote:
> Hi Ivan, Alan, Marcelo,
> 
> On Sun, Jun 30, 2002 at 03:50:58AM +0400, Ivan Kokshaysky wrote:
> 
>>On Sat, Jun 29, 2002 at 03:28:50AM +0100, Alan Cox wrote:
>>
>>>Please back it back in. The bug is the Alpha port. Alpha needs its own OSF
>>>readv/writev entry point which masks the top bits.
>>
>>Ouch. The new entry point just because of this?!
>>Marcelo, if you're going to back in that patch, please apply
>>the following on the top of it.
> 
> 
> This patch indeed makes acroread & netscape work again on my alpha. Nice
> spotting.
> Don't we know about the type of binary? (Like personality ...)
> So we could use something like
>    ssize_t len
>  #ifdef __alpha__
>    if (current->personality == DEC_OSF_OLD)
>      len = (int) iov[i].iov_len;
>    else
>      len = (ssize_t) iov[i].iov_len;
>  #else
>    len = (ssize_t) iov[i].iov_len;
>  #endif
> 
> Not really beautiful, but working for all cases.


That's a good point.

FWIW we have Mozilla 1.0.x working just fine on Alpha, so I don't mind 
second-classing, or making optional, OSF/1 binary support.

It _should_ be possible to correctly support SuSv3 and OSF/1 binaries 
simultaneously.

	Jeff




  reply	other threads:[~2002-07-01 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 10:54 2.4.19-rc1 broke OSF binaries on alpha 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=3D208086.7070603@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=garloff@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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