Also a good solution.

I let it run today for target CPU Marvell Orion and found these
occurrences of "ERROR:" after 12 hours.
Script started on Wed 10 Jun 2009 12:16:08 PM CEST
ERROR: package/feeds/packages/classpath failed to build.
ERROR: package/feeds/packages/fluxbox failed to build.
ERROR: package/feeds/packages/ipmitool failed to build.
ERROR: package/feeds/packages/iptables-snmp failed to build.
ERROR: package/feeds/packages/ruby failed to build.
ERROR: package/feeds/packages/ntpd failed to build.
ERROR: package/feeds/packages/openswan failed to build.
ERROR: package/feeds/packages/rp-pppoe failed to build.
ERROR: package/feeds/packages/uhub failed to build.
ERROR: package/feeds/packages/weechat failed to build.
ERROR: package/feeds/packages/xsupplicant failed to build.
ERROR: package/kernel failed to build. (ide-core)
Script done on Thu 11 Jun 2009 12:27:40 AM CEST

That's great before it took me 1,5 days, because I had to manually
uninstall the packages and compile again.

Regards
Maddes

On 10.06.2009 10:57, Michael Geddes wrote:
> This is the script that I use to do a build.  It works nicely when
> packages
> break for mundane reasons.
>
> First it does a normal make, then reads that output and makes all the
> packages
> that failed, putting the errors into a logfile.
>
> Of course it's not perfect, but it works for me, and it means I can
> leave the
> script running overnight.
>
> //.ichael
>
> ------------8<---------------
> if [ "$1" != "-f" ] ; then
>         IGNORE_ERRORS=1 make 2>&1| tee errors.txt
>
>         rm build_*.txt
> fi
>
> for i in $(grep "failed to build" errors.txt | sed
> 's/^.*ERROR:[[:space:]]*\([^[:space:]].*\) failed to build.*$/\1/' ) ; do
>         if [ "$i" != "" ] ; then
>                 echo Compiling: ${i}
>                 make ${i}-compile V=99 > build_${i##*/}.txt 2>&1 ||
> echo ${i} : Build failed, see build_${i##*/}.txt
>         fi
> done
>
> On Tue, 9 Jun 2009 05:45:35 pm ZioPRoTo (Saverio Proto) wrote:
> >> is there an easy way to compile everything, where compilation errors do
> >> not stop the compilation process?
> >> As manually removing a problem package and manually restarting is
> >> wasting a lot of time.
> >> All compilation errors should be stored in a log so that they can be
> >> checked afterwards.
> > I know that if you call:
> >
> > make IGNORE_ERRORS=m
> >
> > all packages marked to compile as modules will not stop the compiling
> > process in case of errors.
> >
> > I have no idea if there are some logs somewhere ...
> >
> > Saverio
> > _______________________________________________
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to