public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Cannot run Qt5 applications.
Date: Tue, 03 Mar 2015 09:04:00 -0000	[thread overview]
Message-ID: <20150303090407.GA31622@calimero.vinschen.de> (raw)
In-Reply-To: <1425339264.7292.8.camel@cygwin.com>

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

On Mar  2 17:34, Yaakov Selkowitz wrote:
> On Fri, 2015-02-13 at 18:32 +0000, Jon TURNEY wrote:
> > On 05/02/2015 01:40, Jon TURNEY wrote:
> > > On 04/02/2015 23:20, David Stacey wrote:
> > >> I'm having difficulty running any Qt5 application. These are the
> > >> commands I'm issuing:
> > >> [snip]
> > >> and I see the clock, so X is up and running. Then:
> > >> [snip]
> > >
> > > Possibly you need to install and start cygserver (See [1])
> > >
> > > If so, this is because Qt5 is assuming shared memory is available, which
> > > could possibly be handled in a better way...
> > 
> > This looks like a portability problem in Qt5, where it only handles 
> > shmget() failing with a return value of -1, not with SIGSYS, to fallback 
> > to using an image in unshared memory.
> > 
> > Patch attached.
> 
> Or is it a problem with our shmget()?
> 
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/shmget.html
> http://man7.org/linux/man-pages/man2/shmget.2.html
> 
> Perhaps we should be just returning -1 with an errno (ENOSYS?) instead
> of raise(SIGSYS)?

Or you just add signal(SIGSYS, SIG_IGN) prior to calling shmget.
SIGSYS is raised when calling a system call which isn't available.
That's perfectly valid.

Of course, it would be nice if Qt5 used POSIX shared memory objects
iunstead, but that's asked too much, probably.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-03  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 23:20 David Stacey
2015-02-05  1:40 ` Jon TURNEY
2015-02-06 14:57   ` David Stacey
2015-02-13 18:32   ` Jon TURNEY
2015-03-02 23:34     ` Yaakov Selkowitz
2015-03-03  9:04       ` Corinna Vinschen [this message]
2015-03-03 14:49         ` Jon TURNEY
2015-03-03 17:11           ` Corinna Vinschen

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=20150303090407.GA31622@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-xfree@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).