In message <[EMAIL PROTECTED]>
Adam <[EMAIL PROTECTED]> wrote:
[Firefox build breakage]
> However, I've /not/ made the changes you referred to doing "manually" -
> e.g. adding an autoconf symlink. Also, I don't know if old builds of
> dependencies might cause problems? As you've noted, starting from
> scratch is quite tedious so I only want to do that if it's worthwhile.
I presume that it's still broken for you, but you did get the
porting-tools updates. It should therefore be sufficient to run
'./install-env', which takes just a moment.
I would also note that the -D flag also keeps the source for the package
in question, and might also keep any bogus questions in config.cache.
You can for example delete firefox2/mozilla/config.cache.
If you want to redo everything in the autobuilder (which won't take a
huge amount of time for Firefox) you can delete everything under
/home/riscos/env and 'find autobuilder | grep last- | xargs rm'
> > > [1] I did solve one odd thing - the zip binary wasn't being found for
> > > some reason and causing builds to fail. I automade "native-zip" which
> > > seems to have solved that problem at least.
> >
> > That's not a solution, not at all.
>
> You're quite right. I should have been more careful with my language.
So do you think you can find out why?
--
Peter Naulls - [EMAIL PROTECTED] | http://www.chocky.org/
----------------------------------------------------------------------------
RISC OS Community Wiki - add your own content | http://www.riscos.info/
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
