From: Dan Moulding <dan.moulding@rackwareinc.com>
To: buildroot@busybox.net
Subject: [Buildroot] What happened to uclibc-update-config?
Date: Mon, 28 Apr 2014 11:11:31 -0600 (MDT) [thread overview]
Message-ID: <1398705091.394515596@apps.rackspace.com> (raw)
Hi,
I am attempting to save my customized uclibc configuration using the methods prescribed in the Buildroot user manual. It mentions the existence of several "*-update-config" "make" targets. I've done "make busybox-update-config" and that seems to work just fine. But when I try "make uclibc-update-config" I get a "No rule to make target" error from "make".
Looking back in the history, I see that the "uclibc-update-config" target was removed when uClibc was converted to the package infrastructure (commit a5e92d9). Was it never added back? Is there an alternative? Or do I need to just manually copy the .config for uclibc for now?
Thanks!
Dan Moulding
Software Engineer
RackWare, Inc.
next reply other threads:[~2014-04-28 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 17:11 Dan Moulding [this message]
2014-04-30 18:58 ` [Buildroot] What happened to uclibc-update-config? Thomas De Schampheleire
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=1398705091.394515596@apps.rackspace.com \
--to=dan.moulding@rackwareinc.com \
--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