From: Ken Brown <kbrown@cornell.edu>
To: Massi Alvioli <nocharge@gmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: unable to map cygSDL error
Date: Fri, 15 Jun 2018 19:45:00 -0000 [thread overview]
Message-ID: <7ae17db1-d84c-c966-00a0-cb79ede50fb4@cornell.edu> (raw)
In-Reply-To: <CAG0O4LuJ63tJgoThKyLmEVUceaPwdtu+NwszP7WuUoao_-hMuA@mail.gmail.com>
On 6/14/2018 11:22 AM, Massi Alvioli wrote:
> dear Ken,
>
> I found your post on the web
>
> http://cygwin.1069669.n5.nabble.com/gimp-crashes-due-to-libSDL1-2-0-problem-td140811.html
>
> but did not find it in the cygwin users mailing list
It's there:
https://cygwin.com/ml/cygwin/2018-05/msg00226.html
> , so I decided to
> write to your adress only.
It's better to keep the discussion on the mailing list, so that others
can benefit (and help) also.
> As you mention in your post, I ran into the same problem:
>
> https://cygwin.com/ml/cygwin/2018-05/msg00207.html
>
> so I would like to know if you can help me solve the problem.
Until someone figures out the underlying cause of the "unable to map"
error for cygSDL*.dll, my only suggestion is to try to work around the
problem as I did for gimp: avoid using SDL. In your case, I think SDL
is brought in via the package libwx_gtk3u3.0_0. If you look at the
source for that package, you'll see that it uses the configure option
--with-sdl. So you could try to rebuild it without that option.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2018-06-15 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG0O4LuJ63tJgoThKyLmEVUceaPwdtu+NwszP7WuUoao_-hMuA@mail.gmail.com>
2018-06-15 19:45 ` Ken Brown [this message]
2018-06-22 18:27 ` massimiliano
2018-06-22 20:12 ` Ken Brown
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=7ae17db1-d84c-c966-00a0-cb79ede50fb4@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=nocharge@gmail.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).