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 0000520]: gettext: seperate host and target installs
Date: Mon, 12 Feb 2007 05:45:18 -0800	[thread overview]
Message-ID: <44bf430f10ca93bd0ab2b7901c214619@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=520 
====================================================================== 
Reported By:                akvadrako
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   520
Category:                   Other
Reproducibility:            N/A
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             10-28-2005 09:49 PDT
Last Modified:              02-12-2007 05:45 PST
====================================================================== 
Summary:                    gettext: seperate host and target installs
Description: 
Currently it's only possible to install the complete gettext on the target.
 this patch allows that with a new configure option, but it changes the
LIBINTL option to only install that needed at runtime for gettext
programs.  This is probably what most people want, not usually doing
development on a buildroot target.
====================================================================== 

---------------------------------------------------------------------- 
 akvadrako - 10-28-05 09:51  
---------------------------------------------------------------------- 
Sorry about the duplicate - please delete me 

---------------------------------------------------------------------- 
 prpplague - 05-24-06 07:54  
---------------------------------------------------------------------- 
duplicate case 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-28-05 09:49  akvadrako      New Issue                                    
10-28-05 09:49  akvadrako      Status                   new => assigned     
10-28-05 09:49  akvadrako      Assigned To               => uClibc          
10-28-05 09:51  akvadrako      Note Added: 0000645                          
05-24-06 07:54  prpplague      Note Added: 0001378                          
05-24-06 07:54  prpplague      Status                   assigned => closed  
02-12-07 05:45  vapier         Status                   closed => assigned  
02-12-07 05:45  vapier         Assigned To              uClibc => buildroot 
======================================================================

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 13:45 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-20 17:27 [Buildroot] [buildroot 0000520]: gettext: seperate host and target installs 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=44bf430f10ca93bd0ab2b7901c214619@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