From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Nix <nix@esperi.org.uk>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] problems compiling 2.6.17 against glibc 2.4
Date: Sun, 25 Jun 2006 16:38:31 +0200 [thread overview]
Message-ID: <200606251638.31879.blaisorblade@yahoo.it> (raw)
In-Reply-To: <87sllyl2np.fsf@hades.wkstn.nix>
On Wednesday 21 June 2006 21:38, Nix wrote:
> The problem is that arch/um/os-Linux/sys-i386/registers.c
> messes around inside a jmp_buf, and in glibc 2.4 the glibc
> maintainers have helpfully removed the definitions that
> let you poke around in there (they were only there for the
> sake of one macro, _JMPBUF_UNWINDS, which is no longer
> user-visible.)
>
> This vile patch lets me compile but is almost certainly not good enough:
> however, I don't know what *is* good enough: now that glibc is blocking
> us from the layout of the jmp_buf, what's to stop them from changing it?
> (Well, other than that it would break the ABI ;) )
I made the same thought, but no, they have *already* changed it.
Search for the message from Ulrich Drepper (and if you understand
the "security reasons" I'd be curious to hear them); also the below patch is
available in Jeff's tree from some time.
I asked Jeff to #ifdef that code out for 2.6.17 release (since the below patch
was refused)... anyway Jeff found that we can take setjmp() implementation
from klibc and include it in UML.
> A temporary hack to make it compile is
>
> --- linux-orig/arch/um/os-Linux/sys-i386/registers.c 2006-06-20
> 08:17:47.000000000 +0100 +++
> linux/arch/um/os-Linux/sys-i386/registers.c 2006-06-21 07:54:52.000000000
> +0100 @@ -130,6 +130,14 @@
> HOST_FP_SIZE * sizeof(unsigned long));
> }
>
> +# define JB_BX 0
> +# define JB_SI 1
> +# define JB_DI 2
> +# define JB_BP 3
> +# define JB_SP 4
> +# define JB_PC 5
> +# define JB_SIZE 24
> +
> void get_thread_regs(union uml_pt_regs *uml_regs, void *buffer)
> {
> struct __jmp_buf_tag *jmpbuf = buffer;
>
> but that's hardly acceptable in the long run.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-06-25 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 19:38 [uml-devel] problems compiling 2.6.17 against glibc 2.4 Nix
2006-06-25 14:38 ` Blaisorblade [this message]
2006-06-25 19:19 ` Nix
2006-06-25 19:33 ` Blaisorblade
2006-06-26 16:26 ` Nix
2006-06-26 16:45 ` Blaisorblade
2006-06-26 17:09 ` Nix
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=200606251638.31879.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=nix@esperi.org.uk \
--cc=user-mode-linux-devel@lists.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