From: Mark Geisert <mark@maxrnd.com>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: inkscape installed but does nothing
Date: Sat, 25 Nov 2023 21:54:08 -0800 [thread overview]
Message-ID: <30fdf016-b9f5-14c5-32fd-cad81e00563f@maxrnd.com> (raw)
In-Reply-To: <6b44241b-fa2d-9832-b284-f5eefbc4b788@maxrnd.com>
Mark Geisert via Cygwin wrote:
> I'm now going through the laborious process of building inkscape on my test system
> to see if the same issue happens with my build. I'll give an update when I have
> something to report.
I've found that Cygwin's latest inkscape 0.92.3 cannot be built with either
gcc-g++ 11.4 or 11.2. There are incompatibilities with recent C++ include files.
Inkscape *can* be built with gcc-g++ 7.4; that version even seems to run okay.
So it seems that without finding and installing an intervening gcc-g++ I probably
cannot build an inkscape that shows the OP's issue for its investigative value:
building okay but not runnable.
In the meantime I will work towards an NMU (non-maintainer update) of inkscape
using the gcc-g++ that works... hopefully in the next couple of days or so.
..mark
next prev parent reply other threads:[~2023-11-26 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1219644356.4008002.1700795338917.ref@mail.yahoo.com>
2023-11-24 3:08 ` J.F. Huesman
2023-11-24 3:42 ` Backwoods BC
2023-11-24 5:10 ` Mark Geisert
2023-11-26 5:54 ` Mark Geisert [this message]
2023-12-01 6:11 ` Mark Geisert
[not found] <1567827764.3979915.1700782855144.ref@mail.yahoo.com>
2023-11-23 23:40 ` J.F. Huesman
[not found] <2032069619.3870454.1700713626880.ref@mail.yahoo.com>
2023-11-23 4:27 ` J.F. Huesman
2023-11-23 17:04 ` René Berber
2023-11-24 1:50 ` Mark Geisert
[not found] <390805164.3627445.1700626992321.ref@mail.yahoo.com>
2023-11-22 4:23 ` J.F. Huesman
2023-11-22 4:33 ` René Berber
2023-11-22 6:45 ` Brian Inglis
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=30fdf016-b9f5-14c5-32fd-cad81e00563f@maxrnd.com \
--to=mark@maxrnd.com \
--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).