From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Application not working in 64-bit cygwin cygwin/X
Date: Tue, 23 Feb 2016 15:51:00 -0000 [thread overview]
Message-ID: <56CC7FED.7070403@gmail.com> (raw)
In-Reply-To: <CAGX=k3GFDBLeZfP9S1KteF1kcO3p+BeGuYQ4gHedtx0Rw5bUfw@mail.gmail.com>
On 23/02/2016 16:12, Girish Joglekar wrote:
> I have created a test example based on X-Windows/Motif which crashes
> on 64-bit cygwin cygwin/X but runs on the 32-bit version.
>
> Here is the link to the tar file. Please download it before the link
> expires (I do not know now long it stays active)
>
> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>
> Hope you can reproduce the behavior and fix the problem.
>
Hi Girish,
May I suggest you add the -Wall flags to INFLAGS
and look at all the mismatched definitions ?
there are almost 200 warnings... not counting the unused variables
marco@GE-MATZERI-EU /pub/temp/X_test/test
64 $ grep warning make.log |wc -l
260
marco@GE-MATZERI-EU /pub/temp/X_test/test
64 $ grep "warning: unused" make.log |wc -l
72
Usually a test case is simple not 116 source files.
Regads
Marco
--
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:[~2016-02-23 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:12 Girish Joglekar
2016-02-23 15:51 ` Marco Atzeri [this message]
2016-02-23 16:35 Girish Joglekar
2016-03-10 15:58 Girish Joglekar
2016-03-10 16:06 ` Marco Atzeri
2016-03-10 17:05 ` Jon Turney
2016-03-11 14:23 Girish Joglekar
2016-03-11 23:10 ` David Stacey
2016-03-12 6:28 ` Marco Atzeri
2016-03-12 17:39 ` Kaz Kylheku
2016-03-12 18:50 ` Corinna Vinschen
2016-03-15 13:14 ` cyg Simple
2016-03-16 21:38 Girish Joglekar
2016-11-27 22:30 Girish Joglekar
2016-11-28 7:07 ` 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=56CC7FED.7070403@gmail.com \
--to=marco.atzeri@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).