public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hagood <david.hagood@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Bug? Older 32 bit program (CivCTP) no longer works under 64 bit kernel
Date: Thu, 15 May 2014 20:24:05 -0500	[thread overview]
Message-ID: <537568B5.9060208@gmail.com> (raw)

I have an old native Linux 32 bit copy of Civilization: Call to Power. 
It used to work under a 64 bit environment back in the 3.0.x days. 
However, under recent versions (>3.5) it no longer runs - it complains 
that it cannot find certain files in the directory. The exact same code 
will run just fine under a 32 bit version of 3.11. I have a Pentium II 
as well as the Core 2 Duo, both running Ubuntu 14.04, same version of 
the kernel other than one is 32 bit and one is 64 bit. I've copied the 
files over from the 32 bit machine, where it runs, to the 64 bit 
machine, where it does not. I've even gone so far as to copy all the 
system 32 bit libraries into the CivCTP directory, and forced the 
program to use them (including using the ld-linux.so loader from that 
directory) - so in theory it's all the same user space libraries running 
- the only difference that I can see is that one kernel is 64 bit and 
one is 32 bit.

Running strace on the program shows that the directories being searched 
for game assets are corrupted:

16218 stat64("/home/wowbaggr/CivCTP/ctdata/englisish/uidata/keymap.txt", 
  <unfinished ...>

Note the "englisish" rather than "english".

I'm looking for any suggestions on where to look for what might cause 
such an issue - what can I do to start tracking this down.

             reply	other threads:[~2014-05-16  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  1:24 David Hagood [this message]
2014-05-16  3:36 ` Bug? Older 32 bit program (CivCTP) no longer works under 64 bit kernel Ken Moffat
2014-05-29 19:04   ` Pavel Machek

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=537568B5.9060208@gmail.com \
    --to=david.hagood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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