From: massimiliano <nocharge@gmail.com>
To: cygwin@cygwin.com
Subject: Re: unable to map cygSDL error
Date: Fri, 22 Jun 2018 18:27:00 -0000 [thread overview]
Message-ID: <1529686954576-0.post@n5.nabble.com> (raw)
In-Reply-To: <7ae17db1-d84c-c966-00a0-cb79ede50fb4@cornell.edu>
Ken Brown-6 wrote
> On 6/14/2018 11:22 AM, Massi Alvioli wrote:
>
>> 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.
>
> Hi Ken,
>
> I tried to compile the libwx_gtk3u3.0_0 package: I installed the package
> source using cygwin's setup, then cd /usr/src/wxWidgets3.0-3.0.3-1.src,
> edited wxWidgets3.0.cygport to remove --with-dsl, and issued the commands
> cygport wxWidgets3.0.cygport prep/compile/test/install. After installing
> loads of new cygwin packages required to build wxwidgets, I compiled
> GRASS GIS again but still I have no luck - same "unable to map
> cygSDL2xxx.dll
> error message at startup.
>
> Is there any obvious flaw in my procedure? any other idea?
>
> thanks in advance.
>
>
> Massi
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
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 prev parent reply other threads:[~2018-06-22 17:02 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
2018-06-22 18:27 ` massimiliano [this message]
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=1529686954576-0.post@n5.nabble.com \
--to=nocharge@gmail.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).