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 11606] libjpeg has no Config.in
Date: Thu, 10 Jan 2019 18:56:19 +0000	[thread overview]
Message-ID: <bug-11606-163-2EIoQlNKdn@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11606-163@https.bugs.busybox.net/>

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

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
jpeg is a virtual package (provided either by libjpeg or libjpeg-turbo). Use
BR2_PACKAGE_JPEG / jpeg to ensure libjpeg or libjpeg-turbo is available. See
the many packages with a 'select BR2_PACKAGE_JPEG'

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2019-01-10 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 17:33 [Buildroot] [Bug 11606] New: libjpeg has no Config.in bugzilla at busybox.net
2019-01-10 18:56 ` bugzilla at busybox.net [this message]

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-11606-163-2EIoQlNKdn@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