All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Jeff Dike <jdike@karaya.com>
Cc: ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.60
Date: Thu, 13 Feb 2003 11:19:50 +0300	[thread overview]
Message-ID: <20030213111950.A1369@namesys.com> (raw)
In-Reply-To: <200302130412.XAA05507@ccure.karaya.com>

Hello!

On Wed, Feb 12, 2003 at 11:12:38PM -0500, Jeff Dike wrote:
 
> The only other solution I see is to rename the kernel sigprocmask.  Oleg Drokin
> has done with this with a 
> 	-Dsigprocmask=__sigprocmask
> on kernel code compiles, and I've done it at link time with objcopy.  This 

This is a bit incorrect.
I do -Dsigprocmask=__sigprocmask on user code part of UML. I found that glibc
(at least the one I have) defines sigprocmask as weak symbol, but there is
__sigprocmask already that has same address as sigprocmask.
Also this does not work for dynamic build for some reason.

> Anyway, if there's something better, I really want to know about it.

Yeah, someone please come up with the better way. Please!

Bye,
    Oleg

  reply	other threads:[~2003-02-13  8:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  4:12 Linux 2.5.60 Jeff Dike
2003-02-13  8:19 ` Oleg Drokin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-10 19:08 Linus Torvalds
2003-02-10 20:41 ` Maciej Soltysiak
2003-02-10 21:11   ` Stephen Hemminger
2003-02-10 21:25     ` James Lamanna
2003-02-10 22:54       ` Linus Torvalds
2003-02-10 22:21 ` John Cherry
2003-02-11  7:08 ` Oleg Drokin
2003-02-11  7:38   ` Linus Torvalds
2003-02-12  8:11     ` Eric W. Biederman
2003-02-12 11:49       ` Jeff Dike
2003-02-13 23:25         ` Werner Almesberger
2003-02-11 15:16 ` Zephaniah E. Hull
2003-02-11 22:47   ` Andrew Morton
2003-02-11 22:54     ` Andrew Morton
2003-02-14 16:56       ` Zephaniah E. Hull
2003-02-11 16:23 ` Russell King
2003-02-11 17:06   ` Linus Torvalds
2003-02-12  2:47     ` David S. Miller
2003-02-11 22:00 ` Rudmer van Dijk
2003-02-12 10:05 ` Ingo Oeser

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=20030213111950.A1369@namesys.com \
    --to=green@namesys.com \
    --cc=ebiederm@xmission.com \
    --cc=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.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.