From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Cc: John Spencer <maillist-musl@barfooze.de>
Subject: Re: Hello
Date: Thu, 7 Jun 2012 23:18:31 +0800 [thread overview]
Message-ID: <20120607231831.66c78c33@sibserver.ru> (raw)
In-Reply-To: <4FD0A902.6070108@barfooze.de>
On Thu, 07 Jun 2012 15:13:38 +0200
John Spencer <maillist-musl@barfooze.de> wrote:
> On 06/07/2012 02:01 PM, orc wrote:
> > I'm not a developer, sorry (I have a basic-to-middle C knowledge
> > enough to understand why build fails), but still can help in areas
> > of application compatibility, testing and cross-compiling. Anyone
> > interested?
> >
> hello,
> as described on the webpage, the most helpful work you can do
> additionally to what you suggested is
> - spread the word
> - file bug reports against upstream software bugtrackers/maillists
> (such as the missing includes you encountered)
> - convince people not to use gnulib / gnu autocrap / cmake
> - you could help sabotage linux to get a proper X11 setup so that one
> could start to use musl on the desktop
> see https://github.com/rofl0r/sabotage
> if you want to look into that, i think its most helpful to look at
> the buildscripts alpine linux uses.
> -- JS
Okay, thanks for pointing the direction.
I already have X11 stuff in my TODO list for the musl-enabled system,
but now I feel it will just fail without any results with huge error
logs.
And I already see the X11 stuff in the sabotage tree. Does it builds
correctly?
At this time I think to take an older X release without some stuff I
don't need. X11R7.6 build requires python and weird xml libs for
example. Maybe even XFree86 (to test it in qemu for the micro desktop
system project).
next prev parent reply other threads:[~2012-06-07 15:18 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 ` orc [this message]
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
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=20120607231831.66c78c33@sibserver.ru \
--to=orc@sibserver.ru \
--cc=maillist-musl@barfooze.de \
--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).