public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: David Haworth <dave@fen-net.de>
To: insight@sources.redhat.com
Subject: Re: Compiling in 64 bits
Date: Thu, 06 Mar 2008 21:02:00 -0000	[thread overview]
Message-ID: <20080306210135.GC5888@fen-net.de> (raw)
In-Reply-To: <47D03D96.5010403@redhat.com>

Hi Keith,

On Thu, Mar 06, 2008 at 10:53:10AM -0800, Keith Seitz wrote:
> That is, of course, my fault (and I apologize): I do tend to make random 
> disappearances depending on what is happening with my work load. But I now 
> have access to an x86_64 box of my (wife's) very own, so I'll try to take a 
> look at this tonight.

What I said wasn't intended as criticism, so I'm sorry if it sounded like
that. I think those of us who run 64-bit Linux are aware that it's
still bleeding-edge. Yes, the mainstream stuff works OK, but stray a little
from the beaten track and you start finding programs that won't run, or that
appreas to run perfectly well but refuse to open perfectly good files,
claiming that they are not in the correct format. The usual culprit for
the former is an assumption that a pointer is 32-bits, for the latter that
a long is 32-bits.
I'm also aware that not everyone has access to an amd64 machine, and even
those who do may find that it has a 32-bit linux installed.

I did try (briefly) to fix the problems. I got rid of all the
compiler errors by careful type-changes and casts, but the GUI part
simply won't run. I fear there may be deeper problems in the tcl/tk
package. I recall you mentioning recently that insight has an old verison
of tcl/tk built-in and that you intended to try to get rid of it
and use a normal version. I have a feeling that supporting amd64
might force the issue :-O

Dave

  reply	other threads:[~2008-03-06 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 15:24 Walther
2008-03-06 17:55 ` David Haworth
2008-03-06 18:58   ` Keith Seitz
2008-03-06 21:02     ` David Haworth [this message]
2008-03-06 21:08       ` Keith Seitz
2008-03-07  7:48         ` Keith Seitz

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=20080306210135.GC5888@fen-net.de \
    --to=dave@fen-net.de \
    --cc=insight@sources.redhat.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).