public inbox for
help / color / mirror / Atom feed
From: "J. Offerman" <>
To: cygwin-xfree <>
Subject: Re: build error on 1.16.2-1
Date: Mon, 01 Dec 2014 23:37:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

This is an obvious source-header discrepancy. The source
file(auto-generated anyway) doesn't seem to be changed recently, while
the header file(glext.h) has a timestamp of Nov 16 now. So it looks
like only the header file got advanced here. Looking at the
announcements, it should be the Mesa update on Nov 17 that renewed it.
Should I just add the extra arguments for those 3 funcs in the source
file as defined in the new header file? That looks like working.

On Mon, Dec 1, 2014 at 11:09 AM, J. Offerman <> wrote:
> Can somebody help me overcome this error? What am I missing this time?
> Last time I tried to build X was 2 months ago and it was 1.16.1-1,
> which was built just fine. Thanks for your help.
> ====================================================
> make[5]: Entering directory
> '/usr/src/xorg-server-1.16.2-1.src/xorg-server-1.16.2-1.x86_64/src/xserver-cygwin-1.16.2-1/hw/xwin/glx'
>   CC       libnativeGLthunk_la-glthunk.lo
> In file included from glthunk.c:87:0:
> generated_gl_thunks.c: In function 'glVertex2bOESWrapper':
> generated_gl_thunks.c:7098:3: error: too few arguments to function 'proc'
>    ^
> generated_gl_thunks.c: In function 'glVertex3bOESWrapper':
> generated_gl_thunks.c:7110:3: error: too few arguments to function 'proc'
>    ^
> generated_gl_thunks.c: In function 'glVertex4bOESWrapper':
> generated_gl_thunks.c:7122:3: error: too few arguments to function 'proc'
>    ^
> Makefile:712: recipe for target 'libnativeGLthunk_la-glthunk.lo' failed

Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-12-01 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 19:09 J. Offerman
2014-12-01 23:37 ` J. Offerman [this message]
2014-12-05 14:19   ` Jon TURNEY
2015-01-31 14:22     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).