To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54153 Issue #:|54153 Summary:|gccinstlib.pl fails Component:|utilities Version:|680m127 Platform:|All URL:| OS/Version:|Linux Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|PATCH Priority:|P3 Subcomponent:|code Assigned to:|hro Reported by:|kendy
------- Additional comments from [EMAIL PROTECTED] Fri Sep 2 05:09:30 -0700 2005 ------- Building project external ============= /local/ooo-build/ooo-build/build/src680-m127/external/gcc3_specific mkout -- version: 1.4 gccinstlib.pl libstdc++.so.5 /local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib gccinstlib.pl libgcc_s.so.1 /local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib copy /lib/libgcc_s.so.1 to /local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib /opt/icecream/bin/gcc: error while loading shared libraries: /local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib/libgcc_s.so.1: file too short Use of uninitialized value in scalar chomp at /local/ooo-build/ooo-build/build/src680-m127/solenv/bin/gccinstlib.pl line 81. Use of uninitialized value in concatenation (.) or string at /local/ooo-build/ooo-build/build/src680-m127/solenv/bin/gccinstlib.pl line 87. copy to /local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib Use of uninitialized value in concatenation (.) or string at /local/ooo-build/ooo-build/build/src680-m127/solenv/bin/gccinstlib.pl line 88. /bin/cp: missing destination file operand after `/local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib' Try `/bin/cp --help' for more information. copy failed: at /local/ooo-build/ooo-build/build/src680-m127/solenv/bin/gccinstlib.pl line 88. dmake: Error code 1, while making '/local/ooo-build/ooo-build/build/src680-m127/solver/680/unxlngi4.pro/lib/libstdc++.so.5' It is a multi-process build, so we agreed with ause that it may be the reason: <ause> kendy: ok, so the error may make sense: libgcc_s.so is written by copy while gcc tries to load libstdc++ (and inplicit libgcc_s?) I am not sure whether .SEQUENTIAL fixes the issue, because I cannot reproduce it ATM (which could support the idea of parallelism-related problem). Either way, it should make no harm. Second thing is that I use --with-system-stdlibs, so I guess this code should not be run at all anyway. I'll attach a patch. Pavel, could you have a look, please? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
