mailing list of musl libc
 help / color / mirror / code / Atom feed
From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: Hello
Date: Mon, 25 Jun 2012 06:53:34 -0700 (PDT)	[thread overview]
Message-ID: <26146.132.241.65.253.1340632414.squirrel@lavabit.com> (raw)
In-Reply-To: <20120625195923.23829e93@sibserver.ru>

> On Fri, 22 Jun 2012 21:43:13 -0400 (EDT)
> idunham@lavabit.com wrote:
>
>> > Some news from that point.
>> >
>> > I spent some time building the same X11 tree as my host system uses
>> > (X11R76) and now I can say that it works almost unmodified with musl
>> > 0.9.1. Some notes about it:
>> > - all libs compiled normally except xcb and Mesa. XCB deals with XML
>> >   and python that I did not installed, Mesa depends on g++.
>> >   (Unfortunately all X libs have now rpath hardcoded, thanks to
>> >   libtool's idiotic behavior. Oh.)
>> > - apps compiled normally (some failed due to unset CFLAGS, was too
>> > lazy to fix the build.sh)
>> > - xorg-server-1.11.2:
>> >     - did not linked with musl 0.9.1 (missing ioperm() and iopl()
>> >       syscall wrappers, added manually).
>> Are these wrappers available somewhere online (in a git tree or
>> something)?
>
> I added them manually, they are just one-line system call wrappers.
> Attached patch just adds them as an additional files, without declaring
> them in headers (I declared them in unistd.h, but not sure, maybe
> wrong place for linux-specific calls).
>
Wrong place: sys/io.h (not yet provided by musl) is where those go. _




  reply	other threads:[~2012-06-25 13:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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           ` idunham [this message]
2012-07-22 23:09 Hello idunham
2012-07-23  2:01 ` Hello Rich Felker
2012-07-23  3:49   ` Hello idunham
2012-07-23 21:01     ` Hello Rich Felker

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=26146.132.241.65.253.1340632414.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).