https://bugs.freedesktop.org/show_bug.cgi?id=40359
--- Comment #35 from kyri...@alumni.princeton.edu 2012-01-04 06:45:35 PST --- > So maybe you could be that hero? :-) I spent about a day trying to build LibreOffice, and failed miserably. Using the sources from git (actually, the weekly tarball), I had to deal with an increasing amount of problems (mysterious hangs, syntax errors in unknown configuration files, resulting in erroneous commands, that I had to fix and run by hand), until, with less than 20 modules to go, I encountered some unresolved symbols during linking, which I had no idea how to resolve. Assuming that this was because the git sources may not be in a stable state right now, I tried compiling the 3.4.4 sources. I started getting a mysterious hang again, only this time restarting the build process would hang again at the same place. At this point, I have reached the point of diminishing returns: reinstalling windows is probably going to be quicker (not that I'm going to do it), and will likely fix the problem, so I give up. It would seem that building LibreOffice under windows is a black art. I may have gained more respect for those people who actually do it every day, but it is definitely not for someone who is not interested in developing LibreOffice, but only in producing a one-off debug build to see where a crash occurs. This makes it more imperative that automatic crash reporting is implemented in LibreOffice. I would appreciate it if the bug was left open, as fixing something else might fix this, as well. I got the impression that there has been quite a bit of restructuring between 3.4 and the git version (3.6!) so this is not unlikely. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
