Bug 84813 - --with-internal-glib does not build on cygwin64
Summary: --with-internal-glib does not build on cygwin64
Status: RESOLVED MOVED
Alias: None
Product: pkg-config
Classification: Unclassified
Component: src (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Cygwin
: medium normal
Assignee: pkg-config
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-08 20:20 UTC by vincent.laporte
Modified: 2018-08-25 12:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
cygwin_conv_path instead of cygwin_conv_to_posix_path (375 bytes, text/plain)
2014-10-08 20:20 UTC, vincent.laporte
Details

Description vincent.laporte 2014-10-08 20:20:59 UTC
Created attachment 107582 [details]
cygwin_conv_path instead of cygwin_conv_to_posix_path

When building pkg-config with the internal glib on cygwin64, there are two errors:

In file glib/glib/gutils.c, the identifier `glib_dll` is not declared.

In file glib/glib/gwin32.c, the function `cygwin_conv_to_posix_path` no longer exists. See http://www.cygwin.com/cygwin-api/func-cygwin-conv-path.html Attached is a patch suggestion for this second problem.
Comment 1 Dan Nicholson 2014-11-11 21:11:42 UTC
Hmm, these both seem to be bugs in glib itself. The second one seems fine and should go to glib upstream (https://bugzilla.gnome.org/enter_bug.cgi?product=glib). Would be great if you can open a bug there, but I can do that if you'd like. Seems this has some good background - https://cygwin.com/ml/cygwin/2011-01/msg00408.html.

For the first issue, can you show a build log? I'd like to see exactly where it's failing.
Comment 2 GitLab Migration User 2018-08-25 12:53:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pkg-config/pkg-config/issues/15.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.