On Thu, 20 Jun 2019 16:29:45 +0200
Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote:
> On Thu, Jun 20, 2019 at 10:54:21AM +0200, Sam Ravnborg wrote:
> > Hi Antony
> >
> > On Thu, Jun 20, 2019 at 11:25:09AM +0300, Antony Pavlov wrote:
> > > The commit b917f7864115a35 ("remove CONFIG_DEBUG_INFO")
> > > has dropped Kconfig DEBUG_INFO option however we
> > > still have very many DEBUG_INFO mentions in defconfig
> > > files. Drop them using sed:
> > >
> > > find -iname '*defconfig' -type f -exec \
> > > sed -i "/CONFIG_DEBUG_INFO=y/d" {} ';'
> > Another approach could be to regenerate all defconfigs.
> > A little scripting around savedefconfig should do it.
> >
> > Then we would get rid of all obsolete symbols in one go - for all
> > defconfigs.
> >
> > The generated defconfig would be the one that people would be using
> > anyway, so there should be only a little risk to introduce new issues
> > doing it this way.
> >
> > Willing to try this approcah - maybe across all architectures?
>
> I once thought the same and came up with this little thing:
Hi!
I propose to add two error handling features:
>
> #!/bin/bash
add 'set -e' here (or just use 'bash -e')
The -e option means "if any script command ever ends with a non-zero ('error') exit status, terminate the script immediately".
>
> for a in arch/*; do
> arch=$(basename $a)
> for c in $a/configs/*; do
> config=$(basename $c)
> export ARCH=$arch
> make $config && make savedefconfig && mv defconfig $c
add 'echo $config' or use 'mv -i' instead of 'mv'. It is reasonable to see which config
file processing lead to error situation.
> done
> done
>
> Just tested, still works. Maybe I should just run this from time to time
> and commit the result. What do you think?
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
