The fact that it doesn't seem to throw a warning if the library is
missing is a bit weird. Or if it does, I haven't noticed the message.
Gareth aka. Kit
On 26/11/2020 21:02, Sven Barth via fpc-devel wrote:
Am 26.11.2020 um 21:48 schrieb J. Gareth Moreton via fpc-devel:
I figured it was
Am 26.11.2020 um 21:48 schrieb J. Gareth Moreton via fpc-devel:
I figured it was something like that. I'm not sure which installer
put it there, or if moving it to the System32 directory will cause
something to catastrophically fail!
Given that it seems to just silently ignore the issue of
I figured it was something like that. I'm not sure which installer put
it there, or if moving it to the System32 directory will cause something
to catastrophically fail!
Given that it seems to just silently ignore the issue of the DLL doesn't
exist, would a warning be better for an invalid
Am 25.11.2020 um 00:37 schrieb J. Gareth Moreton via fpc-devel:
Hi everyone,
This might be my own configuration, but can people check that
i386-win32 works properly? I tried to build it to test one of my new
optimisations, but got a failure when building the trunk (without my
optimisations).
On 25.11.2020 4:37, J. Gareth Moreton via fpc-devel wrote:
Compiling .\oracle\src\oraoci.pp
oraoci.pp(1437) Error: Invalid DLL C:\windows\system32\common.dll,
invalid header size
oraoci.pp(1437) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted
From
On Wed, 25 Nov 2020 08:51:19 +, J. Gareth Moreton via fpc-devel
wrote:
> Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
> while C:\Windows\System is 64-bit. Question is, what can I do to
> resolve it? I'm not even sure what Common.dll is for.
SYSTEM32 has
On 25.11.2020 4:37, J. Gareth Moreton via fpc-devel wrote:
This might be my own configuration, but can people check that i386-win32
works properly? I tried to build it to test one of my new optimisations,
but got a failure when building the trunk (without my optimisations).
Building using
Well, I found a temporary solution. installing 32-bit Oracle libraries
didn't fix the problem, so I simply commented out the $linklib entry in
the culprit file. I didn't have any of the other files it listed anyway!
Gareth aka. Kit
On 25/11/2020 17:51, J. Gareth Moreton via fpc-devel wrote:
Sure thing - I'll give that a try.
Looks like this is my first true experience with DLL Hell!
Gareth aka. Kit
On 25/11/2020 17:13, Marco van de Voort via fpc-devel wrote:
Op 2020-11-25 om 18:10 schreef J. Gareth Moreton via fpc-devel:
That's the only useful stuff I found. Sorry to sound
Op 2020-11-25 om 18:10 schreef J. Gareth Moreton via fpc-devel:
That's the only useful stuff I found. Sorry to sound like such a
novice. I have never come across this error before and am not sure
how to resolve it without breaking something critical.
Easiest: do an install of the
Damn - I never thought to fully confirm that.
So what I've found so far - there's a copy in the following directories:
-
C:\Windows\System32\DriverStore\FileRepository\xtucomponent.inf_amd64_614515f4e6eb21a1
- C:\Windows\SysWOW64
Both seem to be identical, unless one is a simple mirror of
On 2020-11-25 09:51, J. Gareth Moreton via fpc-devel wrote:
Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
while C:\Windows\System is 64-bit. Question is, what can I do to
resolve it? I'm not even sure what Common.dll is for.
Well, I don't think that it works this way
J. Gareth Moreton via fpc-devel schrieb am
Mi., 25. Nov. 2020, 09:51:
> Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
> while C:\Windows\System is 64-bit. Question is, what can I do to
> resolve it? I'm not even sure what Common.dll is for.
>
Wrong.
System32 -> Host
Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
while C:\Windows\System is 64-bit. Question is, what can I do to
resolve it? I'm not even sure what Common.dll is for.
Gareth aka. Kit
On 25/11/2020 07:27, Marco van de Voort via fpc-devel wrote:
Op 2020-11-25 om 00:37
Op 2020-11-25 om 00:37 schreef J. Gareth Moreton via fpc-devel:
This might be my own configuration, but can people check that
i386-win32 works properly? I tried to build it to test one of my new
optimisations, but got a failure when building the trunk (without my
optimisations).
Building
Hi everyone,
This might be my own configuration, but can people check that i386-win32
works properly? I tried to build it to test one of my new optimisations,
but got a failure when building the trunk (without my optimisations).
Building using "make all install OS_TARGET=win32
16 matches
Mail list logo
