From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libnice-0.1.18-1
Date: Sun, 10 Jan 2021 22:36:31 +0900 [thread overview]
Message-ID: <20210110223628.43EF.50F79699@gmail.com> (raw)
In-Reply-To: <87y2h1t2mu.fsf@Rainer.invalid>
On Sun, 10 Jan 2021 12:46:43 +0100, Marco Atzeri via Cygwin-apps
> On 10.01.2021 01:07, Lemures Lemniscati via Cygwin-apps wrote:
> Building on my system I found that gobject-introspection will need
> a rebuild for python3.
>
> /usr/bin/meson --internal exe --unpickle /pub/tmp/libnice-0.1.18-1.src/libnice-0.1.18-1.x86_64/src/libnice-0.1.18/x86_64-pc-cygwin/meson-private/meson_exe_g-ir-scanner_2092638958d73a5ee2a2021f7aa8d2c979f4fd4e.dat
On Sun, 10 Jan 2021 13:09:13 +0100, Achim Gratz
> Lemures Lemniscati via Cygwin-apps writes:
> > * On x86, it failed to build.
>
> There's a SEGV killing gcc somewhere in the buils, but I am not sure
> where. Is it possible to serialize the build and see if that's
> reproducible still?
Thank you, Marco and Achim for review.
Failures are at same points as Marco's
* The first build:
https://ci.appveyor.com/project/cygwin/scallywag/builds/37187728/job/52dy26ao9sv0bedk#L924
> [71/150] /usr/bin/meson --internal exe --unpickle /cygdrive/c/projects/playground/libnice-0.1.18-1.i686/src/libnice-0.1.18/i686-pc-cygwin/meson-private/meson_exe_g-ir-scanner_cb3ca9af3f8a35f0ba5f42f29b14b723f34faffb.dat
> FAILED: nice/Nice-0.1.gir
* A serialized build by the following src_compile():
```
src_compile() {
cygmeson ${@}
cygninja -C ${CHOST} -j 1
}
```
https://ci.appveyor.com/project/cygwin/scallywag/builds/37191342/job/ldm5c0kigtj6tuxy#L916
> [65/150] /usr/bin/meson --internal exe --unpickle /cygdrive/c/projects/playground/libnice-0.1.18-1.i686/src/libnice-0.1.18/i686-pc-cygwin/meson-private/meson_exe_g-ir-scanner_cb3ca9af3f8a35f0ba5f42f29b14b723f34faffb.dat
> FAILED: nice/Nice-0.1.gir
And, I noticed that my /usr/bin/python is 2.7.18 (both of x86_64 and i686)...
Situations are:
* g-ir-scanner is contained in a package gobject-introspection.
* gobject-introspection requires python27, python27-mako
(cf. https://www.cygwin.com/packages/summary/gobject-introspection.html ).
* Packages python27-mako, python3-mako, python36-mako, python37-mako exists,
but python38-mako don't at present.
(cf. https://www.cygwin.com/packages/summary/python-mako-src.html )
Although I'm not sure...
We might need to rebuild gobject-introspection, as Marco said,
and python*-mako also.
Regards,
Lem
next prev parent reply other threads:[~2021-01-10 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 0:07 Lemures Lemniscati
2021-01-10 11:46 ` Marco Atzeri
2021-01-10 12:09 ` Achim Gratz
2021-01-10 13:36 ` Lemures Lemniscati [this message]
2021-01-14 2:53 ` Ken Brown
2021-01-14 6:41 ` Marco Atzeri
2021-01-14 15:11 ` Ken Brown
2021-01-14 15:29 ` Ken Brown
2021-01-15 9:16 ` Lemures Lemniscati
2021-01-15 9:37 ` Marco Atzeri
2021-01-14 8:53 ` ASSI
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=20210110223628.43EF.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--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).