public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Massi Alvioli <nocharge@gmail.com>
To: cygwin@cygwin.com
Subject: Re: compiling GRASS GIS in Cygwin and Windows 10
Date: Fri, 14 Sep 2018 09:42:00 -0000	[thread overview]
Message-ID: <CAG0O4Lt=JRim5vQwEbo+Ms074pSoUfqGvF0i4e+HEE1rDZbDEQ@mail.gmail.com> (raw)
In-Reply-To: <CAG0O4LuTn_xROr6K3XBjJGJ3TtOFQcWwmOxmysnLu2XaYTxbbA@mail.gmail.com>

dear cygwin users,

just want to let you know that the problem was finally solved with the
latest Cygwin update. Thumbs up!
Now GRASS GIS can be compiled and used in Cygwin, again.

Massi

Il giorno ven 15 giu 2018 alle ore 00:13 Massi Alvioli
<nocharge@gmail.com> ha scritto:
>
> > It seems python failed to load cygSDL2-2-0-0.dll
> >
> > I assume that the output of
> >   cygcheck cygSDL2-2-0-0.dll
> > is fine, but probably one of the dependency was incorrectly updated.
> > Look if there is any /usr/bin/*.new file.
> >
> > For further dependency check you can use http://www.dependencywalker.com/ on
> > cygSDL2-2-0-0.dll
> > or run the python compiler under strace.
>
> Hi Marco,
>
> I still had no luck in solving this GRASS GIS+cygwin problem, but I
> see there is another
> post reporting a related problem:
>
> http://cygwin.1069669.n5.nabble.com/gimp-crashes-due-to-libSDL1-2-0-problem-td140811.html
>
> and it looks like the problem is .. unsolvable?
>
>
> Massi

--
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

      parent reply	other threads:[~2018-09-14  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 13:36 Massi Alvioli
2018-05-16 14:28 ` Marco Atzeri
     [not found]   ` <CAG0O4LuTn_xROr6K3XBjJGJ3TtOFQcWwmOxmysnLu2XaYTxbbA@mail.gmail.com>
2018-09-14  9:42     ` Massi Alvioli [this message]

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='CAG0O4Lt=JRim5vQwEbo+Ms074pSoUfqGvF0i4e+HEE1rDZbDEQ@mail.gmail.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).