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 0000438]: The libfl.a library is not installed in staging_dir.
Date: Mon, 12 Feb 2007 05:47:13 -0800	[thread overview]
Message-ID: <f7c4483f18d34b9ea393303d4ee02435@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=438 
====================================================================== 
Reported By:                steelman
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   438
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             09-19-2005 05:08 PDT
Last Modified:              02-12-2007 05:47 PST
====================================================================== 
Summary:                    The libfl.a library is not installed in staging_dir.
Description: 
The libfl.a is installed under root directory of target system but not
under staging_dir which IMHO suits better for static libraries.

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

---------------------------------------------------------------------- 
 steelman - 09-19-05 05:12  
---------------------------------------------------------------------- 
The dupa.patch was a wrong file, dupa1.patch is the correct for this issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-19-05 05:08  steelman       New Issue                                    
09-19-05 05:08  steelman       Status                   new => assigned     
09-19-05 05:08  steelman       Assigned To               => uClibc          
09-19-05 05:08  steelman       File Added: dupa.patch                       
09-19-05 05:12  steelman       File Added: dupa1.patch                      
09-19-05 05:12  steelman       Note Added: 0000556                          
01-23-06 13:21  prpplague      Status                   assigned => resolved
01-23-06 13:21  prpplague      Resolution               open => fixed       
01-23-06 13:21  prpplague      Additional Information Updated                   

03-08-06 16:54  vapier         Status                   resolved => closed  
02-12-07 05:47  vapier         Status                   closed => assigned  
02-12-07 05:47  vapier         Assigned To              uClibc => buildroot 
======================================================================

                 reply	other threads:[~2007-02-12 13:47 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=f7c4483f18d34b9ea393303d4ee02435@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox