public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TeX Live 2018
Date: Sun, 06 May 2018 20:02:00 -0000	[thread overview]
Message-ID: <b3a6f806-9bb3-1720-ee1a-c0865b59d3ed@cornell.edu> (raw)
In-Reply-To: <3c916846-23e4-63ec-032d-b0e173e93778@cygwin.com>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On 4/29/2018 6:16 PM, Yaakov Selkowitz wrote:
> On 2018-04-29 08:33, Marco Atzeri wrote:
>> On 4/29/2018 11:25 AM, Lemures Lemniscati wrote:
>>> On each systems, there appeared a dialog telling something like that:
>>>
>>>     The procedure entry point 'glBegin' could not be located in the
>>>     dynamic link library 'cygOSMesa-8.dll'
>>
>> I would say that libOSMesa8 had a modification in the list of
>> exported symbols in the last version.
>>
>>
>> [TXT]    libOSMesa8-17.3.5-1    21-Feb-2018 09:50     267
>> [TXT]    libOSMesa8-17.3.8-1    05-Apr-2018 12:44     267
>> [TXT]    libOSMesa8-18.0.1-1    23-Apr-2018 07:35     267
>>
>> I do not see  glBegin in the last cygOSMesa-8.dll of 18.0.1-1
>> So it seems there is an issue on the last libOSMesa8 package
> 
> Indeed, investigating now.

Yaakov,

I don't know where your are in your investigation, but I think I found 
the problem.  The attached patch to the mesa sources seems to fix it

Ken


[-- Attachment #2: fix-mesa-meson-build.patch --]
[-- Type: text/plain, Size: 584 bytes --]

--- origsrc/mesa-18.0.1/src/gallium/targets/osmesa/meson.build	2018-04-18 10:47:54.000000000 -0400
+++ src/mesa-18.0.1/src/gallium/targets/osmesa/meson.build	2018-05-06 12:51:07.040841000 -0400
@@ -43,9 +43,9 @@ libosmesa = shared_library(
     inc_gallium_drivers,
   ],
   link_depends : osmesa_link_deps,
-  link_whole : [libosmesa_st],
+  link_whole : [libosmesa_st, libglapi_static],
   link_with : [
-    libmesa_gallium, libgallium, libglapi_static, libws_null, libtrace,
+    libmesa_gallium, libgallium, libws_null, libtrace,
     osmesa_link_with,
   ],
   dependencies : [

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


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

  reply	other threads:[~2018-05-06 20:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 20:02 Ken Brown
2018-04-29  1:25 ` Lemures Lemniscati
2018-04-29  6:44   ` Marco Atzeri
2018-04-29  9:25     ` Lemures Lemniscati
2018-04-29 13:33       ` Marco Atzeri
2018-04-29 20:02         ` Ken Brown
2018-04-29 21:50           ` Lemures Lemniscati
2018-04-29 22:16         ` Yaakov Selkowitz
2018-05-06 20:02           ` Ken Brown [this message]
2018-05-06 21:57             ` Ken Brown
2018-05-07 18:49               ` Yaakov Selkowitz

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=b3a6f806-9bb3-1720-ee1a-c0865b59d3ed@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@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).