All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001485]: DirectFB: Download site moved and x11 always required
Date: Tue, 4 Sep 2007 13:59:54 -0700	[thread overview]
Message-ID: <17ac266d02db25430f714153df726c4e@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1485 
====================================================================== 
Reported By:                HappyCactus
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1485
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             09-04-2007 08:03 PDT
Last Modified:              09-04-2007 13:59 PDT
====================================================================== 
Summary:                    DirectFB: Download site moved and x11 always
required
Description: 
The directFB main site has removed the 1.0.0 version.
Now 1.0.1 is the current stable version.
Also, configure do not specify either --enable-x11 or --disable-x11, so
that x11 is always required to compile the package.
Working patch attached.
====================================================================== 

---------------------------------------------------------------------- 
 bernhardf - 09-04-07 13:59  
---------------------------------------------------------------------- 
+ifeq ($(BR2_PACKAGE_XORG7),y)
+DIRECTFB_X := --enable-x11
+else
+DIRECTFB_X := --disable-x11
+endif
+
This is not really accurate:
If BR2_PACKAGE_XSERVER_none is y, then disable-x11, else --enable-x11.

Please send patches to the mailing list and only add them to the
bugtracker if it is not applied (or explicitely rejected) within a
reasonable amount of time, TIA 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-04-07 08:03  HappyCactus    New Issue                                    
09-04-07 08:03  HappyCactus    Status                   new => assigned     
09-04-07 08:03  HappyCactus    Assigned To               => buildroot       
09-04-07 08:03  HappyCactus    File Added: buildroot-directfb-x11.patch         
          
09-04-07 13:59  bernhardf      Note Added: 0002711                          
======================================================================

             reply	other threads:[~2007-09-04 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 20:59 bugs at busybox.net [this message]
2007-09-04 22:15 ` [Buildroot] [buildroot 0001485]: DirectFB: Download site moved and x11 always required Ulf Samuelsson
2007-09-04 22:23   ` Bernhard Fischer
2007-09-04 22:38     ` Ulf Samuelsson
  -- strict thread matches above, loose matches on Subject: below --
2008-10-31  9:12 bugs at busybox.net
2007-09-04 15:03 bugs 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=17ac266d02db25430f714153df726c4e@busybox.net \
    --to=bugs@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.