[parisc-linux] glibc 2.3.3 is bug free, weekly regression build, mailed to cvs.p-l.org?

[Carlos O'Donell]

> 
> I certainly could (from hardware and shell scripting opint of view), but
> I might need some help with all the ./configury ...
> 
> Building a toolchain isn't allways a pleasuring task, esp. if you want a
> cross-toolchain. So if interested, I'd dedicate my b132l to that job:)

How about no toolchain build, and just a glibc build with checks for
regressions in the testsuite?

I just fixed glibc so you don't have to build a cross-toolchain, or any
toolchain for the matter. So now all you need to do is:

Initially:
(1) Pull down glibc cvs.

	echo Enter "anoncvs" as the password
	cvs -z 9 -d :pserver:anoncvs at sources.redhat.com:/cvs/glibc login
	cvs -z 9 -d :pserver:anoncvs at sources.redhat.com:/cvs/glibc co libc

(2) Pull down latest patch set.

	wget http://www.parisc-linux.org/~carlos/glibc-hppa-patches-latest.tar.gz
	(Symlinked to glibc-hppa-patches-2004-02-02.tar.gz)

(3) Apply patches, watch for rejects.

	tar zxvf $FILENAME.tar.gz
	cd $SRC/libc
	# How do you gr0k for pathname from a symlinked tar.gz that
	# unpacks to something else...
	for i in `ls $PATHNAME/*`; do patch -p1 < $i; done;
	find . -name '*.rej'

(4) Jump to "Weekely: (4)"

Weekly:
(1) Reverse out patches.

	for i in `ls $PATHNAME/*`; do patch -R -p1 < $i; done;

(2) Pull down latest patch set.

	= Same as above (2)

(3) Update glibc source tree.

	cd $GLIBCSRC
	cvs up >& ../cvs-up.log

(4) Apply new patches, watch for rejects.

	= Same as above (3)

(5) Configure, make, make -k check
	
	export CC=gcc
	export CFLAGS="-O2 -g"

	$BASE/$SRC/$LIBC/configure --host=hppa-linux
	--build=hppa-linux --target=hppa-linux --prefix=/usr
	--enable-add-ons=linuxthreads --disable-tls --disable-__thread
	--enable-all-warnings >& ../configure-hppa.log

	make >& ../build-hppa.log
	make -k check >& ../check-hppa.log

(6) Watch for regresssions.

	grep 'Error' check-hppa.log >& mailout.txt
	# Mail mailout.txt to cvs.parisc-linux.org?

(7) Wait a week, then go to (1)

	# Add to your weekly cron?

Is anyone opposed to having 'grep 'Error' check.log' posted to
cvs.parisc-linux.org on a weekly basis?

Is this enough information to lend a helping hand in writing the build
script? :)

c.