From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Help needed with gobject-introspection
Date: Fri, 29 May 2020 16:54:00 +0100 [thread overview]
Message-ID: <62ba273e-4eed-6578-32e5-8cd24fe25c3f@dronecode.org.uk> (raw)
In-Reply-To: <c91cf7f0-2249-034e-0476-6bde7bc5d670@cornell.edu>
On 27/05/2020 21:32, Ken Brown via Cygwin-apps wrote:
> On 5/24/2020 11:56 AM, Jon Turney wrote:
>> So, yeah, this is a meson bug, which I will work on (if this command
>> ends up in the build.ninja, it's executed by ninja with 'sh -c', but
>> if it ends up in a pickle, it's executed by meson with execve())
>
> It looks like I've bumped into a variation of this bug. While
> attempting to build the documentation for the latest glib2.0 release, I
> got the following:
>
> FAILED: docs/reference/gobject/gobject-decl.txt
> /usr/bin/meson --internal exe --unpickle
> /home/kbrown/src/cygpackages/glib2.0/glib2.0-2.64.3-1.x86_64/src/glib-2.64.3/x86_64-pc-cygwin/meson-private/meson_exe_meson_1ed2fbe217cac49ae4affd274e0d4a729085a002.dat
>
> ['/usr/bin/meson', '--internal', 'gtkdoc',
> '--sourcedir=/home/kbrown/src/cygpackages/glib2.0/glib2.0-2.64.3-1.x86_64/src/glib-2.64.3',
> '--builddir=/home/kbrown/src/cygpackages/glib2.0/glib2.0-2.64.3-1.x86_64/src/glib-2.64.3/x86_64-pc-cygwin',
> '--subdir=docs/reference/gobject', '--headerdirs=gobject',
> '--mainfile=gobject-docs.xml', '--modulename=gobject', '--
>
> [...]
>
> /docs/reference/gobject/tut_tools.xml', '--cc=gcc', '--ld=gcc',
> '--cflags=-I@BUILD_ROOT@/gobject -I../gobject -pthread -I@BUILD_ROOT@/.
> -I../. -I@BUILD_ROOT@/glib -I../glib
> -I@BUILD_ROOT@/docs/reference/gobject/. -I../docs
>
> [...]
>
> So @BUILD_ROOT@ didn't get replaced by the build root after pickling and
> unpickling. Needless to say, this produced errors like:
>
> cc1: error: @BUILD_ROOT@/glib: No such file or directory
> [-Werror=missing-include-dirs]
>
> I can give you a precise recipe for reproducing this bug if it would
> help your debugging.
Definitely a bug. I'll see if I can take a look at it this weekend.
next prev parent reply other threads:[~2020-05-29 15:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 23:04 Ken Brown
2020-05-20 14:50 ` Ken Brown
2020-05-21 13:24 ` Jon Turney
2020-05-21 15:13 ` Ken Brown
2020-05-21 15:48 ` Jon Turney
2020-05-21 17:07 ` Ken Brown
2020-05-24 15:56 ` Jon Turney
2020-05-24 16:45 ` Ken Brown
2020-05-24 17:00 ` Ken Brown
2020-05-25 15:04 ` Ken Brown
2020-05-29 15:56 ` Jon Turney
2020-05-27 20:32 ` Ken Brown
2020-05-29 15:54 ` Jon Turney [this message]
2020-05-31 20:52 ` Jon Turney
2020-05-31 23:58 ` Ken Brown
2020-06-01 11:30 ` Jon Turney
2020-06-02 14:26 ` Jon Turney
2020-06-02 14:31 ` Ken Brown
2020-06-02 21:28 ` Jon Turney
2020-06-03 16:51 ` Jon Turney
2020-06-03 18:30 ` Ken Brown
2020-06-06 14:15 ` Ken Brown
2020-06-11 21:39 ` Jon Turney
2020-06-11 23:23 ` Ken Brown
2020-06-12 14:44 ` Jon Turney
2020-08-01 18:01 ` Ken Brown
2020-08-01 18:34 ` 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=62ba273e-4eed-6578-32e5-8cd24fe25c3f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).