On Friday, 23 August 2019 at 16:49:07 UTC, a11e99z wrote:
> right now problem exists with linker/libs only, compiler see all used VarXXX

First of all, thanks for your patient support.

But, that function is being used throughout.  Also, the same linker builds the whole project with D v1.046.

> u can download LDC (if it exists) for D1 and try to compile program for D1

Pardon my lack of knowledge here, but what is LDC going to do that dmd is not able to do?

> import std.stdio;
> // i dont know right Windows modules for D1 so import what u have
> void main() {
>  	VARIANT a, b;
>  	VarCmp( a, b, 0, 0 ); // D1 version cuz was VarCmp( ref VARIANT, ... )
> }

added

import juno.com.core;

to the above program, and still fails with the same error.  I also went and downloaded the latest D1 linker, and that also results in the same failure.

On Friday, 23 August 2019 at 17:03:24 UTC, jicman wrote:
> On Friday, 23 August 2019 at 16:49:07 UTC, a11e99z wrote:
>> right now problem exists with linker/libs only, compiler see all used VarXXX
>
> First of all, thanks for your patient support.
>
> to the above program, and still fails with the same error.  I also went and downloaded the latest D1 linker, and that also results in the same failure.

another try:
zip ur dmd 1.076 folder (for easy restoring it when something go wrong)
copy lib files from 1.046\lib\*.lib to 1.076\lib\*.lib
try to compile program again with dmd 1.076

On Friday, 23 August 2019 at 17:18:55 UTC, a11e99z wrote:
> On Friday, 23 August 2019 at 17:03:24 UTC, jicman wrote:
>> On Friday, 23 August 2019 at 16:49:07 UTC, a11e99z wrote:
>>> right now problem exists with linker/libs only, compiler see all used VarXXX
>>
>> First of all, thanks for your patient support.
>>
>> to the above program, and still fails with the same error.  I also went and downloaded the latest D1 linker, and that also results in the same failure.
>
> another try:
> zip ur dmd 1.076 folder (for easy restoring it when something go wrong)
> copy lib files from 1.046\lib\*.lib to 1.076\lib\*.lib
> try to compile program again with dmd 1.076

TA-DAH!  Weird stuff.  The 1.046 libraries worked.  Very weird stuff.  Now to try to figure out how that happened, since I took **all** 1.076 from the download site.  Which means, that it may be have outdated libraries.  That's for another day, though.  Muchas gracias, as we say in Spanish.  But, I'll translate for you, Thanks very much.

josé

On Friday, 23 August 2019 at 17:50:52 UTC, jicman wrote:
> On Friday, 23 August 2019 at 17:18:55 UTC, a11e99z wrote:
>> On Friday, 23 August 2019 at 17:03:24 UTC, jicman wrote:
>>> On Friday, 23 August 2019 at 16:49:07 UTC, a11e99z wrote:
>>>> right now problem exists with linker/libs only, compiler see
>>
>> another try:
>> zip ur dmd 1.076 folder (for easy restoring it when something go wrong)
>> copy lib files from 1.046\lib\*.lib to 1.076\lib\*.lib
>> try to compile program again with dmd 1.076
>
> TA-DAH!  Weird stuff.  The 1.046 libraries worked.  Very weird stuff.  Now to try to figure out how that happened, since I took **all** 1.076 from the download site.  Which means, that it may be have outdated libraries.  That's for another day, though.  Muchas gracias, as we say in Spanish.  But, I'll translate for you, Thanks very much.
>
> josé

oops!
better to restore 1.076 back
and copy only Windows libs (not all DRT and others)
one by one till compilation errors dissapear:
oleaut32.lib
ole32.lib
rpcrt4.lib
...

On Friday, 23 August 2019 at 19:35:52 UTC, a11e99z wrote:
> On Friday, 23 August 2019 at 17:50:52 UTC, jicman wrote:
>> On Friday, 23 August 2019 at 17:18:55 UTC, a11e99z wrote:
>>> On Friday, 23 August 2019 at 17:03:24 UTC, jicman wrote:
>>>> On Friday, 23 August 2019 at 16:49:07 UTC, a11e99z wrote:
>>>>> right now problem exists with linker/libs only, compiler see
>>>
>>> another try:
>>> zip ur dmd 1.076 folder (for easy restoring it when something go wrong)
>>> copy lib files from 1.046\lib\*.lib to 1.076\lib\*.lib
>>> try to compile program again with dmd 1.076
>>
>> TA-DAH!  Weird stuff.  The 1.046 libraries worked.  Very weird stuff.  Now to try to figure out how that happened, since I took **all** 1.076 from the download site.  Which means, that it may be have outdated libraries.  That's for another day, though.  Muchas gracias, as we say in Spanish.  But, I'll translate for you, Thanks very much.
>>
>> josé
>
> oops!
> better to restore 1.076 back
> and copy only Windows libs (not all DRT and others)
> one by one till compilation errors dissapear:
> oleaut32.lib
> ole32.lib
> rpcrt4.lib
> ...


WHAT!!! YOU MAKE ME MOVE ALL OF THE LIBS TO THE WRONG PLACE?  Just kidding. He he he he...

I actually have more problems.  After fixing that problem, others have surfaced.  How does one knows which which are the correct names of the undefined symbols?  For example:

OPTLINK (R) for Win32  Release 8.00.16
Copyright (C) Digital Mars 1989-2013  All rights reserved.
http://www.digitalmars.com/ctg/optlink.html
PMORpts.obj(PMORpts)
 Error 42: Symbol Undefined __d_arrayliteralTX
c:\D\import\juno\locale\core.obj(core)
 Error 42: Symbol Undefined __aaEqual

I have searched all over within the code for the project for '__d_arrayliteralTX' and various pieces of that (\Wd\Warray, d, literal, etc.), and have not found anything.  Just as 'Equal', and nothing.  Is there a way to know what is the reference within the code for those obscure symbols?

By the way, I have fixed all back to the way it was. ;-)  Thanks.  The only problem now is trying to figure out where do these symbols come from. Thanks again for the help.

josé

On Friday, 23 August 2019 at 20:33:30 UTC, jicman wrote:
> I actually have more problems.  After fixing that problem, others have surfaced.  How does one knows which which are the correct names of the undefined symbols?  For example:
>
> OPTLINK (R) for Win32  Release 8.00.16
> Copyright (C) Digital Mars 1989-2013  All rights reserved.
> http://www.digitalmars.com/ctg/optlink.html
> PMORpts.obj(PMORpts)
>  Error 42: Symbol Undefined __d_arrayliteralTX
> c:\D\import\juno\locale\core.obj(core)
>  Error 42: Symbol Undefined __aaEqual
>
> I have searched all over within the code for the project for '__d_arrayliteralTX' and various pieces of that (\Wd\Warray, d, literal, etc.), and have not found anything.  Just as 'Equal', and nothing.  Is there a way to know what is the reference within the code for those obscure symbols?
>
> By the way, I have fixed all back to the way it was. ;-)  Thanks.
>  The only problem now is trying to figure out where do these symbols come from. Thanks again for the help.
>
> josé

Ignore the error.  I still had an old 1.046 lib in the 1.076 lib folder.  After that, it compiled with 1.076.  I made changes to the code, it it stills compiles.  I am a happy guy. ;-)  Thanks for all your help.

josé