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 0001197]: UCLIBC_HAS_RPC should be part of the default config
Date: Tue, 13 Feb 2007 09:49:29 -0800	[thread overview]
Message-ID: <8af55025d6228f77ccfe0672ea877261@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1197 
====================================================================== 
Reported By:                smithj
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1197
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             02-05-2007 17:48 PST
Last Modified:              02-13-2007 09:49 PST
====================================================================== 
Summary:                    UCLIBC_HAS_RPC should be part of the default config
Description: 
Busybox's default config should be buildable with uclibc's default config.
Busybox's default has CONFIG_FEATURE_MOUNT_NFS=y, which requires
UCLIBC_HAS_RPC=y. However, the default "defconfig" in uclibc has this
feature undefined.
====================================================================== 

---------------------------------------------------------------------- 
 smithj - 02-05-07 17:50  
---------------------------------------------------------------------- 
Sorry, obviously this is not arch-specific, but i can't seem to change it
now... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-05-07 17:48  smithj         New Issue                                    
02-05-07 17:48  smithj         Status                   new => assigned     
02-05-07 17:48  smithj         Assigned To               => uClibc          
02-05-07 17:48  smithj         Issue Monitored: smithj                      
02-05-07 17:50  smithj         Note Added: 0002123                          
02-13-07 09:49  vapier         Project                  uClibc => buildroot 
02-13-07 09:49  vapier         Assigned To              uClibc => buildroot 
02-13-07 09:49  vapier         Category                 Architecture Specific =>
Other
02-13-07 09:49  vapier         version                  0.9.28 =>           
======================================================================

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 17:49 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-17 17:59 [Buildroot] [buildroot 0001197]: UCLIBC_HAS_RPC should be part of the default config 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=8af55025d6228f77ccfe0672ea877261@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