[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [PATCH] Halt build if ramdisk.image.gz on ppc64 is too large.



> diff --git a/scripts/mk-images.ppc b/scripts/mk-images.ppc
> index 47af389..ae81764 100644
> --- a/scripts/mk-images.ppc
> +++ b/scripts/mk-images.ppc
> @@ -29,6 +29,21 @@ makeBootImages() {
>  	    --loaderbin loader \
>  	    --modules "$INITRDMODS spufs viocd gpio_mdio"
>  
> +	if (( $(stat --format=%s $TOPDESTPATH/ppc/ppc64/ramdisk.image.gz) > 32*1024*1024 )); then
> +	    echo "***"
> +	    echo "*** PPC64 ramdisk.image.gz is larger than 32 MB, aborting"
> +	    echo "***"
> +	    echo "*** This file is generated by scripts/mk-images.ppc in anaconda, but the most"
> +	    echo "*** likely causes of this problem are:"
> +	    echo "***     kernel module set on ppc64 grew in size"
> +	    echo "***     dependent libraries or programs grew in size"
> +	    echo "***"
> +	    echo "*** Please contact the anaconda development team for help determining which"
> +	    echo "*** component in the distribution is at fault."
> +	    echo "***"
> +	    exit 1
> +	fi
> +
>  	cp $KERNELROOT/boot/vmlinuz-* $TOPDESTPATH/ppc/ppc64/vmlinuz
>          sed -e "s/%BITS%/64/" -e "s/%PRODUCT%/$PRODUCT/" -e "s/%VERSION%/$VERSION/" \
>  	    $BOOTDISKDIR/yaboot.conf.in > $TOPDESTPATH/ppc/ppc64/yaboot.conf

As long as we have stat in the environment mk-images runs, ack.

- Chris


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]