public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	makaveli_0000@yahoo.com, nobody@sources.redhat.com
Subject: Re: insight/307: Insight 6.5 will not build on Linux Kernel 2.6.16
Date: Fri, 09 Mar 2007 15:38:00 -0000	[thread overview]
Message-ID: <20070309153824.11881.qmail@sourceware.org> (raw)

Synopsis: Insight 6.5 will not build on Linux Kernel 2.6.16

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Fri Mar  9 15:38:24 2007
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Fri Mar  9 15:38:24 2007
State-Changed-Why:
    When you say that X11/Xlib.h is in the source directory, do you mean src/tk/xlib/X11/Xlib.h? If so, that is not the proper Xlib.h that the build is looking for. Do you have Xlib.h in /usr/include/X11 (or somewhere else in /usr)?
    
    You need to have the -devel package for X installed. On Red Hat systems, this is currently in the xorg-x11-devel package.
    
    You didn't include the entire output of your build, so I can't see if configure complained about missing X headers/libraries, but your build certainly looks like it is missing the -devel package.

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=307


             reply	other threads:[~2007-03-09 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 15:38 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-10  1:33 makaveli_0000

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=20070309153824.11881.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=makaveli_0000@yahoo.com \
    --cc=nobody@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).