In message <[EMAIL PROTECTED]>, Peter Naulls wrote: > 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'
I've just done an ./install-env, deleted the contents of riscos/env and anything related I could find, and tried to re-build Firefox, but got the same result as before. I think the best plan will be for me to wait and try again completely from scratch sometime so we know I'm starting from a clean slate. Is it possible to check in something to address the need for the autoconf symlink and the problem with autogen on Cygwin? > > > > [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? Well, I don't know how to "undo" my "solution", so the problem isn't appearing here now. When I do a clean build of everything hopefully I'll be able to investigate further, if the problem reoccurs. In general, I should say that while I'm happy to do testing and provide feedback as a user of GCC (native and cross) and the autobuilder, in general I don't have the skills to do significant fault-finding / development of the build system. (I also have no plans to explicitly develop those skills.) Thanks, Adam -- Adam Richardson Carpe Diem http://www.snowstone.org.uk/riscos/ _______________________________________________ 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
