Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: run snapshot and ng configs through "savedefconfig"
Date: Mon, 20 Apr 2015 15:27:45 +0000	[thread overview]
Message-ID: <1429543665.2756.26.camel@synopsys.com> (raw)
In-Reply-To: <20150420152520.GR27057@waldemar-brodkorb.de>

Hi Waldemar,

On Mon, 2015-04-20 at 17:25 +0200, Waldemar Brodkorb wrote:
> Hi Alexey,
> Alexey Brodkin wrote,
> 
> > Recently uClibc got support of "savedefconfig" target that allows
> > generation of compact configuration description which only lists
> > differences from default options.
> > 
> > That's uClibc commit -
> > http://git.uclibc.org/uClibc/commit/?id=e286a674419d31cb0757dd2f8307d8b4756cf1f9
> > 
> > This change represents post-processing of "uClibc-snapshot.defconfig"
> > and "uClibc-ng.config" with "make savedefconfig" made on current
> > uClibc/uClibc-ng master branches.
> > 
> > Unfortunately the most recent stable uClibc version 0.9.33.2 doesn't
> > have "savedefconfig" target so I'm leaving uClibc-0.9.33.config as it
> > is.
> 
> Please do not use master branch of uClibc-ng, as the config is no
> longer compatible to uClibc. Use uClibc-ng 1.0 branch for this.
> 1.0 will be compatible to existing uClibc config.
> Master has some symbols renamed and removed already.
> 
> Only 1.0.x support is included in buildroot.

Indeed I noticed some symbols were missing.
But I was under impression that 1.x are made from master so used master
as a base.

I'll send a re-spin with defconfig for uClibc-ng based on 1.0 branch.

Thanks a lot for prompt reply.
Alexey

      parent reply	other threads:[~2015-04-20 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 11:01 [Buildroot] [PATCH] uclibc: run snapshot and ng configs through "savedefconfig" Alexey Brodkin
     [not found] ` <20150420152520.GR27057@waldemar-brodkorb.de>
2015-04-20 15:27   ` Alexey Brodkin [this message]

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=1429543665.2756.26.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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