public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: john_watts@isoparix.com
Subject: Re: SIGSEGV in XopenDisplay in Cygwin64 X11
Date: Fri, 22 Jul 2016 12:54:00 -0000	[thread overview]
Message-ID: <7885f26b-f128-6a4f-518d-c3c62ca3737f@dronecode.org.uk> (raw)
In-Reply-To: <1d256cae-f585-b6e8-1d01-6bbd6551c11e@isoparix.com>

On 21/07/2016 17:25, John Watts wrote:
> cygcheck.out
[...]
> gamin                                   0.1.10-15                    OK
> gawk                                    4.1.3-1                      OK
> gdb                                     7.10.1-1                     OK
[...]
> mingw64-x86_64-binutils                 2.25.0.1.23f238d-1           OK
> mingw64-x86_64-gcc-core                 4.9.2-2                      OK
> mingw64-x86_64-gcc-fortran              4.9.2-2                      OK
> mingw64-x86_64-gcc-g++                  4.9.2-2                      OK
> mingw64-x86_64-headers                  4.0.6-1                      OK
> mingw64-x86_64-runtime                  4.0.6-1                      OK
> mingw64-x86_64-windows-default-manifest 6.4-1                        OK
> mingw64-x86_64-winpthreads              4.0.6-1                      OK

So, I don't see that you have cygwin gfortran installed, so I assume the 
gfortran below is mingw64-x86_64 targeted one?

> # Compile code with following flags
>
>     gfortran -g -fdollar-ok -c testxod.f
>     gfortran -g -I/cygdrive/c/cygwin64/usr/include -I/cygdrive/c/cygwin64/usr/include/X11 -c isox11.c
>     gfortran  testxod.o isox11.o defmap.o bmp_comms.o read_cmap_params.o isoflush.o -o ../ISOPARIX/testxod.exe -L/cygdrive/c/cygwin64/lib -lX11

So this doesn't seem right. Linking the cygwin libX11 with objects built 
with a mingw64 targeted compiler isn't going to work correctly.

I'm afraid we don't provide packages for mingw64 X libraries, so I guess 
your alternatives are to build those yourself, or to build everything 
using a cygwin targeted compiler.

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      reply	other threads:[~2016-07-22 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 16:25 John Watts
2016-07-22 12:54 ` Jon Turney [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=7885f26b-f128-6a4f-518d-c3c62ca3737f@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=john_watts@isoparix.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).