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 0000625]: rootfs isn't updated with changes made in target_skeleton or device_table.txt as described in documentation
Date: Mon, 12 Feb 2007 05:49:17 -0800	[thread overview]
Message-ID: <2717315338eb8e869ea54d1c6f6efdff@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=625 
====================================================================== 
Reported By:                hagepe
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   625
Category:                   Documentation
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             01-06-2006 06:19 PST
Last Modified:              02-12-2007 05:49 PST
====================================================================== 
Summary:                    rootfs isn't updated with changes made in
target_skeleton or device_table.txt as described in documentation
Description: 
At least with the daily snapshot from 5.1.2006:
If I understand the documentation right,
changing files in /target/generic/target_skeleton 
and a simple make in the main directory should rebuild the
rootfs including the changes. 
In fact the rootfs is rebuild but without the changes. There
must be something else that has to be done between the changes
and the "make" or the major makefile needs some changes?




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

---------------------------------------------------------------------- 
 scott - 01-19-06 13:42  
---------------------------------------------------------------------- 
To fix this, we need to change the main Makefile.  It's a one liner...

buildroot/Makefile:

--- Old Line...
$(TARGET_DIR):

+++ New Line...
$(TARGET_DIR): $(TARGET_SKELETON) $(TARGET_SKEL_DIR) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-06-06 06:19  hagepe         New Issue                                    
01-06-06 06:19  hagepe         Status                   new => assigned     
01-06-06 06:19  hagepe         Assigned To               => uClibc          
01-19-06 13:42  scott          Note Added: 0000957                          
01-23-06 06:29  prpplague      Status                   assigned => closed  
01-23-06 06:29  prpplague      Resolution               open => no change
required
01-23-06 06:29  prpplague      Additional Information Updated                   

02-12-07 05:49  vapier         Status                   closed => assigned  
02-12-07 05:49  vapier         Assigned To              uClibc => buildroot 
======================================================================

                 reply	other threads:[~2007-02-12 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2717315338eb8e869ea54d1c6f6efdff@bugs.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.