sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: "James A. Robinson" <jim.robinson@stanford.edu>
To: "sam Fans" <sam-fans@hawkwind.utcs.toronto.edu>
Subject: 24/32 bpp with 9libs vs. orig libXg
Date: Tue, 12 Dec 2000 02:23:33 -0500	[thread overview]
Message-ID: <00Dec12.174550edt.45081@hawkwind.utcs.utoronto.ca> (raw)

A few people have noted problems running sam and 9term on 24 bpp or 32
bpp displays (we would get the error 'libg: i/o error' when we tried to
open a menu in 9term or simply bring up samterm). It appears that my
problem may have stemmed from a problem specific to the 9libs port of
the original libXg library.

The other day I installed limbo, and found that wm/wm couldn't handle
16bpp depth. 8bpp was unacceptable to me, and I had not been able to
run sam and 9term in 24bpp mode before.

Today I installed the original samterm from Rob Pike's release, available
at ftp://netlib.bell-labs.com/netlib/research/sam.shar.gz, and found the
samterm compiled from that source works perfectly at 24bpp. I recompiled
my 9term against this original libXg, and found that it also works at
24bpp without any visible problems. Since the samterm works with the
latest sam (editor only) released a few months ago, I'm happy. =)

My original goal was to get a static version of libXg compiled so that I
could debug it with gdb. I was having great difficulty getting the 9libs
version working with gdb (perhaps because it uses this .la/.lo format
that I've never really understood).  Imagine my surpise when compiling
the original libXg fixed the problem. =)

Jim


                 reply	other threads:[~2000-12-12 22:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00Dec12.174550edt.45081@hawkwind.utcs.utoronto.ca \
    --to=jim.robinson@stanford.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /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 NNTP newsgroup(s).