incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andre Fischer ...@a-w-f.de>
Subject Re: Error 126
Date Thu, 12 Jan 2012 08:18:50 GMT
Hi,

On 11.01.2012 22:52, TJ Frazier wrote:
> Hi, Andre,
>
> On 1/11/2012 16:19, Facundo Cevey wrote:
>> HI!
>> Error 126 is usually displayed at run time when some of the DLLs on your
>> system are missing. The message with the error code 126 may also be
>> displayed when an application is trying to connect to a database and a
>> required DLL is not specified in your machine’s PATH.
>> many databases require that you install and configure a client side
>> library
>> to enable any client to connect. Some of the databases that require a
>> client side library are WinSQL Oracle Driver, Oracle ODBC Driver, and
>> Microsoft Oracle Driver.
>>
>> *reinstall the application or update it.*
>
> A simple case of this kind of 126 error would be permanent, but this one
> is transient. However . . . are you running parallel builds (-Pn or
> whatever)? Maybe some library isn't built / moved / installed yet, when
> another fork needs it. --/tj/

No, it happens regardless of the number of build processes.

>>
>> 2012/1/11 Andre Fischer<af@a-w-f.de>
>>
>>> Hi all,
>>>
>>> On Windows7 my build breaks frequently with an error 126. This happens
>>> apparently randomly, not tied to a specific module or file.
>>> Restarting the
>>> build in the module where it broke works fine.
>>>
>>> At the moment I suspect the virus scanner (different ones on different
>>> computers) to cause this.
>>>
>>> Does anybody *know* the reason for the build breaks?
>>>
>>> Regards,
>>> Andre
>>>
>>
>
>

Mime
View raw message