Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0004674]: The Openchrome package is br0ken..
Date: Fri, 22 Aug 2008 07:42:48 -0700	[thread overview]
Message-ID: <e96fe4be16f1f499ca5ae5378f2c6196@busybox.net> (raw)


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=4674 
====================================================================== 
Reported By:                antialize
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   4674
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             08-20-2008 01:37 PDT
Last Modified:              08-22-2008 07:42 PDT
====================================================================== 
Summary:                    The Openchrome package is br0ken..
Description: 
The openchrome package is broken. It needs, to do install instead of
install-exec just like ALL the other xorg vidio drivers do, currently only
extra libs are installed, not the actual graphics driver!

Index: openchrome.mk
===================================================================
--- openchrome.mk       (revision 23102)
+++ openchrome.mk       (working copy)
@@ -11,5 +11,6 @@

 OPENCHROME_AUTORECONF = YES
 OPENCHROME_CONF_OPT = --enable-shared --disable-static
+OPENCHROME_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR)/usr install

 $(eval $(call AUTOTARGETS,package/x11r7,openchrome))

====================================================================== 

---------------------------------------------------------------------- 
 jacmet - 08-22-08 07:42  
---------------------------------------------------------------------- 
A quick test seems to show that /usr isn't needed. Fixed in r23182. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-20-08 01:37  antialize      New Issue                                    
08-20-08 01:37  antialize      Status                   new => assigned     
08-20-08 01:37  antialize      Assigned To               => buildroot       
08-20-08 01:37  antialize      File Added: openchome.patch                    
08-22-08 07:42  jacmet         Status                   assigned => closed  
08-22-08 07:42  jacmet         Note Added: 0010684                          
======================================================================

             reply	other threads:[~2008-08-22 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 14:42 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-20  8:37 [Buildroot] [buildroot 0004674]: The Openchrome package is br0ken bugs at busybox.net
2008-08-20  8:44 ` Hans-Christian Egtvedt

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=e96fe4be16f1f499ca5ae5378f2c6196@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox