public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "J. Offerman" <jofferman@gmail.com>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: xserver compile err
Date: Thu, 27 Sep 2012 17:46:00 -0000	[thread overview]
Message-ID: <CA+2me80sAHLcYaRpgetOeZagYw+HbZyxPw=Vcyuc6Q_zSMW71A@mail.gmail.com> (raw)
In-Reply-To: <506448A9.5040305@dronecode.org.uk>

On Thu, Sep 27, 2012 at 5:38 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> On 27/09/2012 01:13, J. Offerman wrote:
>> I'm trying to compile 1.12.4 now.
>>   ...
> This is a failure building the unit tests

That's right. I didn't notice XWin.exe was compiled successfully.

> I'd guess you need to ./configure with --disable-unit-tests, or add a patch to
> link them with libglapi which provides that symbol.

Thanks. Let me try disabling the unit test option.

> I'm slightly curious to know if there is something wrong with the X server
> binary package I produce, since you always seem to want to build your own?

Nothing is wrong with your binaries and I'm grateful to you for
maintaining this wonderful thing called Cygwin X server. I just have a
few things about it that do not go well with my taste. But I'm not
foolish enough to say that the rest of the world should adapt to my
taste, so I keep them to myself and end up applying my own patch
everytime I build it. I think I've been doing this since Tears For
Fears tried to rule the world from your country. It used to be more
files, now it's only one file, winwndproc.c. I'm delighted the world
is catching up with me. :)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2012-09-27 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  0:14 J. Offerman
2012-09-27 12:38 ` Jon TURNEY
2012-09-27 17:46   ` J. Offerman [this message]
2012-10-24 13:14     ` Jon TURNEY

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='CA+2me80sAHLcYaRpgetOeZagYw+HbZyxPw=Vcyuc6Q_zSMW71A@mail.gmail.com' \
    --to=jofferman@gmail.com \
    --cc=cygwin-xfree@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).