Re: Question: removal of syscall macros?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Teunis Peters" <[email protected]>
Subject: Re: Question: removal of syscall macros?
From: "Ulrich Drepper" <[email protected]>
Date: Wed, 13 Dec 2006 12:01:14 -0800
Cc: [email protected]
In-reply-to: <[email protected]>
References: <[email protected]>
Sender: [email protected]

On 12/13/06, Teunis Peters <[email protected]> wrote:

Now that syscall macros have been pulled from the -mm tree, what method
is recommended to use syscalls?


glibc forever had a syscall() function for just that purpose.  It was
never a good idea to use the macros since they didn't work in PIC.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Question: removal of syscall macros?
  - From: Teunis Peters <[email protected]>

References:
- Question: removal of syscall macros?
  - From: Teunis Peters <[email protected]>

Prev by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
Next by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
Previous by thread: Re: Question: removal of syscall macros?
Next by thread: Re: Question: removal of syscall macros?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]

Powered by Linux