mailing list of musl libc
 help / color / mirror / code / Atom feed
From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: Hello
Date: Sun, 22 Jul 2012 19:09:25 -0400 (EDT)	[thread overview]
Message-ID: <25387.50.0.229.11.1342998565.squirrel@lavabit.com> (raw)

I've been getting a little impatient waiting to see if anything happens,
so I started going through orc's patch and revising it.

1. It still applies cleanly.

2. __sigsetjmp is only added on x86(_64).
While looking at arm, I noticed that x86/mips gas uses @function while arm
uses %function...is there a reason for this?

3. splice() is added to fcntl.h with _GNU_SOURCE, but needs (s)size_t;
what I did was add
#ifdef _GNU_SOURCE
#define __NEED_size_t
#define __NEED_ssize_t
#endif

above where alltypes.h was included.

>> > - rawmemchr() was taken from uClibc
(I'm temporarily dropping that part...)
>> > - ioperm() and iopl() were not necessary to make glxgears work, just
>> >   added them because Xorg will want them
>> > Probably you will want to add:
>> > - weak_aliases for __underscores
>>
>> Except most of them should be in the opposite direction. Especially
>> for functions like strxfrm_l where we'll eventually want the ISO C
>> "foo" function to depend on the POSIX "foo_l" function, the latter
>> will need its real name to be the __-prefixed version.
Are there any of these that should not be the other way around?
>> > - weak_aliases __funcname_internal
>>
>> These are rather ugly and stupid, but seem harmless.

>>
>> > glibc-specific functions and objects required to make glxgears work:
...
>> > - gnu_get_libc_*()
>> return "not glibc";





             reply	other threads:[~2012-07-22 23:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22 23:09 idunham [this message]
2012-07-23  2:01 ` Hello Rich Felker
2012-07-23  3:49   ` Hello idunham
2012-07-23 21:01     ` Hello Rich Felker
  -- strict thread matches above, loose matches on Subject: below --
2012-06-07 12:01 Hello orc
2012-06-07 13:13 ` Hello John Spencer
2012-06-07 15:18   ` Hello orc
2012-06-07 16:29     ` Hello John Spencer
2012-06-07 16:19       ` Hello Rich Felker
2012-06-07 17:15         ` Hello orc
2012-06-08  3:31           ` Hello Rich Felker
2012-06-08  5:49             ` Hello Isaac Dunham
2012-06-08 12:28             ` Hello aep
2012-06-08 14:14               ` Hello Rich Felker
2012-06-08 16:17                 ` Hello aep
2012-06-08 16:11                   ` Hello Rich Felker
2012-06-09  2:05                   ` Hello Isaac Dunham
2012-07-05 17:24             ` Hello orc
2012-07-05 23:34               ` Hello Rich Felker
2012-07-06  6:06                 ` Hello orc
2012-07-06  6:26                   ` Hello Rich Felker
2012-07-06  8:22                     ` Hello orc
2012-07-06 23:14                       ` Hello idunham
2012-07-07  0:57                         ` Hello Rich Felker
2012-07-07  8:07                         ` Hello orc
2012-07-07 15:54                           ` Hello idunham
2012-07-08  9:09                             ` Hello orc
2012-06-07 17:45         ` Hello Christian Neukirchen
2012-06-07 18:03       ` Hello Jens Staal
2012-06-07 19:10         ` Hello John Spencer
2012-06-07 17:33     ` Hello Jens Staal
2012-06-07 17:59       ` Hello orc
2012-06-20  7:29     ` Hello orc
2012-06-23  1:43       ` Hello idunham
2012-06-23  1:51         ` Hello Rich Felker
2012-06-25 12:09           ` Hello orc
2012-06-25 11:59         ` Hello orc
2012-06-25 13:53           ` Hello idunham

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=25387.50.0.229.11.1342998565.squirrel@lavabit.com \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).