Re: [parisc-linux] Users staying up to date.

["Carlos O'Donell Jr." <carlos@megatonmonkey.net>]

> 
> For an x86 -> hppa/hppa64 cross toolchain I use the palinux-autobuilder script 
> in the build-tools section of pehc cvs.
> 
> For a native hppa toolchain use the debian packages(which several people 
> worked very hard on in order to get working so we didn't have to deal with 
> building by hand).
> 

True, the native hppa toolchain is excellent. But in our case the systems we
are compiling for are much too slow.  Our cluster of 715's is great for 
proving and testing that your code works in parallel, but nothing short of
dead slow...

Thus we make extensive use of the toolchain on x86.
Ever try building MPICH on a 715/50? :}
Compared to make -j16 on our dual PIII...

> For hppa -> hppa64 cross compilers I still do it by hand.
> 
> Are you rolling your own toolchain for fun, or is the stuff on pehc not 
> meeting your needs?
>

The palinux-autobuilder, atleast the last one I saw, could not compile
the latest set of sources.  I haven't tried in a while.  This is really
the whole reason this thread got started... that palinux-autobuilder 
wasn't working properly for me :} And now Matthew almost has me signed on
as the maintainer for glibc on hppa!

Also, the notes on http://www.parisc-linux.org/toolchain/index.html should
be changed to reflect the fact that it's not possible to build a system
using said instructions ;)

It should probably be changed to include the steps required to:

a) Roll it by hand (what I was attempting)
b) Use the palinux-autobuilder

It goes without saying that I really _want_ the autobuilder to work.
Maybe I should grab it out of CVS... I had the ftp version.

I noted in my other email, that there are a few finiky things that
the autobuilder must do in order to work (set certain environment variables,
patch glibc, etc...).

Cheers,
Carlos.