|
From: Szakacsits S. <sz...@si...> - 2004-03-25 13:38:54
|
On Thu, 25 Mar 2004, Anton Altaparmakov wrote: > There is now a new snapshot with this fixed. At least works for me on > a RH9-ish box. This compiles, thanks. > The way I generated snapshots was (all scripted of course): > > bk export > cd to exported dir > edit configure.ac to add date to version number > ./autogen.sh > make distclean > tar > scp to sf.net > ssh to sf.net and run bin/add-snapshot > > This fails as you saw for me too unless I have the autoconf 2.59 > installed. > > The new script does instead of the autogen.sh this: > > autoreconf --verbose --install --warnings=all > ./configure > make libs > make > make extra > and then carries on with make distclean, etc. > > This seems to work fine now. No bk export? Then it's VERY dangerous. Imagine you have some write (or whatever) related experimental code in your own tree (quite possible IMHO :) and you can pack and release it accidently without realising. It would be extremely hard later to track down that the released package was different than the one thought to be released! autoreconf also seems to be a workaround for a bug (inconsistency) that you, and only you, have in your tree. For me it seems during the autotools upgrade things got mixed up. Or SUSE 9.1 BETA autotools are buggy and in that case you should report ;) Szaka |
