All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1387] New: xlib_libX11-1.3.2 can's find libjpeg
Date: Mon, 22 Mar 2010 02:31:46 +0000 (UTC)	[thread overview]
Message-ID: <bug-1387-163@https.bugs.busybox.net/> (raw)

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

              Host: X86_64
            Target: ARM
             Build: buildroot-git
           Summary: xlib_libX11-1.3.2 can's find libjpeg
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: paul.jones at iwtech.com.au
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1357)
 --> (https://bugs.busybox.net/attachment.cgi?id=1357)
Buildroot config

X.Org should select jpeg, but for whatever reason it didn't. When I selected it
manually it didn't appear to get built before it was needed by X11.


-- 
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:[~2010-03-22  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  2:31 bugzilla at busybox.net [this message]
2010-03-22  2:35 ` [Buildroot] [Bug 1387] xlib_libX11-1.3.2 can's find libjpeg bugzilla at busybox.net
2010-03-24 10:53 ` bugzilla at busybox.net
2010-03-31  8:48 ` bugzilla at busybox.net
2010-03-31  9:52 ` bugzilla at busybox.net
2010-03-31 10:16 ` 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-1387-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.