Re: autubuild failures in lxp

Thanks Thatcher,
I did some poking around those scripts just then (I should have done so 
long ago ;) )
I ended up using ./test_dist.sh as it seems straight forward and suited 
to local use.
If I saw it right it basically does these steps, which could be done by 
hand also:
* run all required autotools things
then do 'make dist' (which I was missing to understand all this time for 
some reason)
and finally configure and build what is in that new dist...

One main thing I always wish for with all these autotools and make & 
froends: some way of 'introspection'... how do I know what targets are 
availeable and what they are intended for? Only way I see is reading 
(and hopefully understanding) the Makefile... unghhh
It's okay once you know all the incantations, it seems evern easy 
then... But if you don't... bugger.

My pointz here is:
maybe this is a feature things like Hamster could strive for: self 
documenting build tools. Something like Pydoc inside the build script so 
that later you could do:
./myBuild --list-targets
and you get a nice list of availeable targets with (optional) description...

-Martin


Thatcher Ulrich wrote:

> On Mar 25, 2004 at 08:30 +0100, Martin Spernau wrote:
>  
>
> > now I'm sure there's a way to 'test' this packaging & building locally?
> >    
>
> Yes, there's a bash script in the root of the distro,
> "test_build_luacheia.sh".  It does the whole auto test, soup to nuts:
> determine current platform, make test directories (~/lc_test_cvs and
> ~/lc_test_dist), check out the whole tree from CVS into lc_test_cvs,
> make a tarball, unpack the tarball in the lc_test_dist directory, do a
> full ./configure && make, and run the self-tests.
>
> It takes a while :)
>
> It makes a file ~/lc_test_cvs/platform/report.txt with the results.
> It also tries to email the results to the luacheia-commit list, by
> ssh'ing to the SF compile-farm shell server, which may or may not work
> depending on whether you have configured access to that server.
> Anyway, that's not necessary; you can always just inspect the
> report.txt.  Personally, if it's a small change and I think it has a
> decent chance of succeeding, I often just wait for the nightly build
> results.
>
> There are some other scripts in there that are less comprehensive, but
> I don't use them anymore so I'm not sure if they still work.
>
>  




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click