public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Cc: john@fishtail-da.com
Subject: [Fwd: Re: building Insight on Red Hat 9.0]
Date: Tue, 16 Sep 2003 17:45:00 -0000	[thread overview]
Message-ID: <1063734476.1584.10.camel@lindt.uglyboxes.com> (raw)

[Forwarding to list for the record...]

Good news! This is the second time I've run across this with RHL9.
Fortunately for you, your pain was not nearly as bad as the previous
persons! (It took me quite a while to figure it all out...)

Keith
-----Forwarded Message-----

> From: John Hatfield <john@fishtail-da.com>
> To: Keith Seitz <keiths@redhat.com>
> Subject: Re: building Insight on Red Hat 9.0
> Date: 16 Sep 2003 10:03:16 -0700
> 
> 
> Hi Keith --
> 
> Sorry for the false alarm. After sending the email
> last night, I realized that I had not installed 
> the X developer RPM. Once I did that, Insight built
> and ran correctly.
> 
> Thanks for the prompt response.
> 
> 
> John
> 
> --- Keith Seitz <keiths@redhat.com> wrote:
> > On Mon, 2003-09-15 at 20:47, John Hatfield wrote:
> > > I've had some problems building Insight on Red Hat
> > 9
> > > --
> > > there are errors about missing X11 headers/libs.
> > Is
> > > this a known issue? I tried copying them over from
> > > a Red Hat 8 install (where Insight works
> > correctly),
> > > and managed to get it to link, but got runtime
> > errors
> > > about not being able to open the display.
> > > 
> > > Any help would be greatly appreciated.
> > 
> > Do you have the XFree86-devel RPM installed?
> > 
> > Keith
> > 
> > 
> 

                 reply	other threads:[~2003-09-16 17: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=1063734476.1584.10.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=john@fishtail-da.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).