mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Christian Neukirchen <chneukirchen@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Hello
Date: Thu, 07 Jun 2012 19:45:07 +0200	[thread overview]
Message-ID: <87fwa7ow2k.fsf@gmail.com> (raw)
In-Reply-To: <20120607161928.GE163@brightrain.aerifal.cx> (Rich Felker's message of "Thu, 7 Jun 2012 12:19:28 -0400")

Rich Felker <dalias@aerifal.cx> writes:

> On Thu, Jun 07, 2012 at 06:29:13PM +0200, John Spencer wrote:
>> >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).
>> >
>> what kept me from configuring X11 to work properly is its huge
>> freaking complexity.
>> if an older version is simpler and can do the job as well, i'm all for it.
>> i fear though that you won't get any up-to-date software compiled
>> against it.
>> probably not worth the effort.
>
> As far as the server goes, even the oldest X server versions should
> work fine with modern software (aside from possibly being really slow
> when the software wants to do 3D, etc.). That's how X was designed.

Reality is, applications simply won't work without XRENDER, XKB and other
2000'ish things.  E.g. GTK generally needs 8bpp or more, or it will not
even start.

-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org


  parent reply	other threads:[~2012-06-07 17:45 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         ` Christian Neukirchen [this message]
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=87fwa7ow2k.fsf@gmail.com \
    --to=chneukirchen@gmail.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).