From: Mike Hearn <mh@codeweavers.com>
To: Paul Jackson <pj@sgi.com>
Cc: John Reiser <jreiser@BitWagon.com>,
akpm@osdl.org, pageexec@freemail.hu,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
ashok.raj@intel.com
Subject: Re: arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot
Date: Mon, 03 May 2004 22:29:03 +0100 [thread overview]
Message-ID: <1083619742.24587.3.camel@linux.littlegreen> (raw)
In-Reply-To: <20040503140459.10b9d3eb.pj@sgi.com>
On Mon, 2004-05-03 at 14:04 -0700, Paul Jackson wrote:
> Since I see Andrew dropped the patch for the moment, I'm thinking that
> the ball is back in you guys court.
We've been able to develop a (complex) workaround for the VM layout
problems in userspace by inserting a shim between the dynamic linker and
the kernel. It sets up the address space correctly before the linker
runs so, for now, Wine will be alright without the patch - assuming we
can get the shim merged with Wine CVS of course :)
It would be nice to get the bssprot patch in though, if only because a
GNU linker script would be about 100x smaller and less scary than the
shim code.
thanks -mike
--
Mike Hearn <mh@codeweavers.com>
Codeweavers, Inc
next prev parent reply other threads:[~2004-05-03 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 1:56 arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Paul Jackson
2004-04-27 5:17 ` John Reiser
2004-04-27 5:27 ` Paul Jackson
2004-05-01 8:33 ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson
2004-05-03 14:08 ` John Reiser
2004-05-03 17:57 ` Andrew Morton
2004-05-03 21:04 ` Paul Jackson
2004-05-03 21:29 ` Mike Hearn [this message]
2004-05-03 22:10 ` Paul Jackson
2004-05-03 22:20 ` Mike Hearn
2004-05-03 22:26 ` Paul Jackson
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=1083619742.24587.3.camel@linux.littlegreen \
--to=mh@codeweavers.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=jreiser@BitWagon.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=pj@sgi.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