Hi guys,
Regina's problem comes down to a corrupt .d file.
Any ideas how that could happen ? are these generated by a pipeline ?
are we failing to delete them if a compile fails mid-flow ?
Then again, Regina didn't abort the build manually, so the
ctrl-c-in-mid-flow case is not at issue.
Thoughts,
Michael.
On Fri, 2012-03-30 at 11:30 +0200, Regina Henschel wrote:
workdir/wntmsci12/Dep/CxxObject/extensions/source/propctrlr/browserlistbox.d
looks bad, I see
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/stdexcept \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/exception \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/xstddef \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/cstddef \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/eh.h \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/malloc.h \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/xstring \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/xmemory \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/new \
/c
workdir/wntmsci12/Dep/LinkTarget/Library/ipcr.lib.d
looks good, I see
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/ymath.h \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/cfloat \
/cygdrive/c/PROGRA~1/MICROS~1.0/VC/include/cmath
/cygdrive/c/git/LO36APR/solver/wntmsci12/inc/offapi/com/sun/star/xsd/WhiteSpaceTreatment.hdl:
/cygdrive/c/git/LO36APR/solver/wntmsci12/inc/offapi/com/sun/star/xsd/WhiteSpaceTreatment.hpp:
/cygdrive/c/git/lo36apr/extensions/source/propctrlr/xsdvalidationpropertyhandler.hxx:
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.