public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Application not working in 64-bit cygwin cygwin/X
Date: Fri, 11 Mar 2016 23:10:00 -0000	[thread overview]
Message-ID: <56E3504C.4030805@tiscali.co.uk> (raw)
In-Reply-To: <CAGX=k3FLakLze4XzYy7kQ8=xQQ=jKrUiZDPsvmR33OXE9eFdsQ@mail.gmail.com>

On 11/03/16 14:23, Girish Joglekar wrote:
> I have cleaned up the test example based on X-Windows/Motif which crashes
> on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
> warnings are of the type 'variable set but not used'.
>
> Here is the link to the tar file.
>
> https://www.dropbox.com/s/lknuoac64hfql4s/test.tar?dl=0
>
> Hope you can reproduce the behavior and fix the problem.

I tried this on Fedora 23 64-bit and it works. I had to add an empty 
utcrcu.h file, as the code tries to #include this, and it doesn't exist 
in the tar file. Given that it runs in 64-bit Linux, the problem is 
unlikely to be an issue associated with porting 32-bit applications to 
64-bit.

Dave.


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

  reply	other threads:[~2016-03-11 23:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 14:23 Girish Joglekar
2016-03-11 23:10 ` David Stacey [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2016-11-27 22:30 Girish Joglekar
2016-11-28  7:07 ` Ken Brown
2016-03-16 21:38 Girish Joglekar
2016-03-10 15:58 Girish Joglekar
2016-03-10 16:06 ` Marco Atzeri
2016-03-10 17:05   ` Jon Turney
2016-02-23 16:35 Girish Joglekar
2016-02-23 15:12 Girish Joglekar
2016-02-23 15:51 ` Marco Atzeri

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=56E3504C.4030805@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --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).