Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 829] New: Webkit r44552 needs libXt
Date: Sun, 27 Dec 2009 17:47:53 +0000 (UTC)	[thread overview]
Message-ID: <bug-829-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=829

              Host: i686-linux-gnu
            Target: i686-linux-uclibc
             Build: i686-linux-uclibc
           Summary: Webkit r44552 needs libXt
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: dandart at googlemail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


I tried to compile (host has Xt with dev headers), but Webkit still doesn't
compile, maybe due to it being compiled before X (I specified TinyX).

checking for XtOpenDisplay in -lXt... no
configure: error: X Toolkit Intrinsics library (libXt) not found
make: ***
[/home/dan/xenon/buildroot/output/build/webkit-r44552/.stamp_configured] Error
1


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-12-27 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-27 17:47 bugzilla at busybox.net [this message]
2010-02-21 18:51 ` [Buildroot] [Bug 829] Webkit r44552 needs libXt bugzilla at busybox.net
2010-02-21 18:54 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-23  7:04 ` bugzilla at busybox.net
2010-07-27 21:27 ` bugzilla at busybox.net

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=bug-829-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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