Thread overview
wxWindows 2.2.7
Nov 19, 2005
Cesar Rabak
Nov 19, 2005
Walter Bright
Nov 19, 2005
W³odzimierz Skiba
Nov 23, 2005
Walter Bright
Nov 25, 2005
Walter Bright
November 19, 2005
With a minor edit to "src\defs.h", wxWindows 2.2.7 almost compiles with DMC.

============================================================================================

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\robert>set WXWIN=D:\wxMSW-2.2.7

C:\Documents and Settings\robert>cd /d %WXWIN%\src\msw

D:\wxMSW-2.2.7\src\msw>make -f makefile.sc
copy D:\wxMSW-2.2.7\src\common\dosyacc.c D:\wxMSW-2.2.7\src\common\y_tab.c
        1 file(s) copied.
copy D:\wxMSW-2.2.7\src\common\doslex.c D:\wxMSW-2.2.7\src\common\lex_yy.c
        1 file(s) copied.
sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  -DUSE_DEFINE -Jm D:\wxMSW-2.2.7\src\common\y_tab.c -oD
:\wxMSW-2.2.7\src\common\y_tab.obj
                          while (input() != '*');
                                               ^
lexer.l(96) : Warning 7: possible extraneous ';'
    if ((yyn = yysindex[yystate]) && (yyn += yychar) >= 0 &&
                                   ^
y_tab.c(292) : Warning 2: possible unintended assignment
    if ((yyn = yyrindex[yystate]) && (yyn += yychar) >= 0 &&
                                   ^
y_tab.c(310) : Warning 2: possible unintended assignment
            if ((yyn = yysindex[*yyssp]) && (yyn += YYERRCODE) >= 0 &&
                                          ^
y_tab.c(333) : Warning 2: possible unintended assignment
    if ((yyn = yygindex[yym]) && (yyn += yystate) >= 0 &&
                               ^
y_tab.c(493) : Warning 2: possible unintended assignment

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\appcmn.cpp -oD:\wxMSW-2.2.7\
src\common\appcmn.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\choiccmn.cpp -oD:\wxMSW-2.2.
7\src\common\choiccmn.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\clipcmn.cpp -oD:\wxMSW-2.2.7
\src\common\clipcmn.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\cmdline.cpp -oD:\wxMSW-2.2.7
\src\common\cmdline.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\cmndata.cpp -oD:\wxMSW-2.2.7
\src\common\cmndata.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\config.cpp -oD:\wxMSW-2.2.7\
src\common\config.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\ctrlcmn.cpp -oD:\wxMSW-2.2.7
\src\common\ctrlcmn.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\ctrlsub.cpp -oD:\wxMSW-2.2.7
\src\common\ctrlsub.obj

sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
-ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\datetime.cpp -oD:\wxMSW-2.2.
7\src\common\datetime.obj
Internal error: cgcod 1489
--- errorlevel 1

--- errorlevel 1

D:\wxMSW-2.2.7\src\msw>

============================================================================================

Anyone have any hints?
November 19, 2005
On 11/18/2005 6:21 PM, Robert James Morales wrote:

> sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
> -ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\datetime.cpp -oD:\wxMSW-2.2.7\src\common\datetime.obj
> Internal error: cgcod 1489
> --- errorlevel 1
> 
> --- errorlevel 1

Could it be due to file size? datetime.cpp is well over 64KiB...
November 19, 2005
Robert James Morales escreveu:
> On 11/18/2005 6:21 PM, Robert James Morales wrote:
> 
>> sc -c -Jm -ml -W -D__WXMSW__ -D__DMC__ -D__WXDEBUG__ -D__WINDOWS__ -D__WIN16__
>> -ID:\wxMSW-2.2.7\include  D:\wxMSW-2.2.7\src\common\datetime.cpp -oD:\wxMSW-2.2.7\src\common\datetime.obj
>> Internal error: cgcod 1489
>> --- errorlevel 1
>>
>> --- errorlevel 1
> 
> 
> Could it be due to file size? datetime.cpp is well over 64KiB...

I think it is unlikely. Most probable cause is the combination of switches plus the particularity of the code.

Under this circumstances, we're left with:

1) do a binary seach (cutting datetime.cpp in syntatically valid slices) to see what part of the code triggers the symptom;

2) take out switches (although the object code will not be worth for the project) until the problem gets out.

Then report to Walter to see how to get the compiler work or an acceptable workaround.

HTH

--
Cesar Rabak
November 19, 2005
"Cesar Rabak" <crabak@acm.org> wrote in message news:dlnp5p$pt1$1@digitaldaemon.com...
> Robert James Morales escreveu:
> >> Internal error: cgcod 1489
> Under this circumstances, we're left with:
>
> 1) do a binary seach (cutting datetime.cpp in syntatically valid slices)
> to see what part of the code triggers the symptom;
>
> 2) take out switches (although the object code will not be worth for the
> project) until the problem gets out.
>
> Then report to Walter to see how to get the compiler work or an acceptable workaround.

Yes, please send me such and I'll be happy to fix it. Also, since it's been working, it would likely be in new code. -Walter



November 19, 2005
Robert James Morales <rmorales2005@gmail.com> wrote in news:dllr5u$2883$1@digitaldaemon.com:
> Anyone have any hints?

Is suggestion of using later wxWidgets version helpful? Is it possible? Later versions vere widely tested withDMC.

ABX

November 20, 2005
On 11/19/2005 3:02 PM, W³odzimierz Skiba wrote:

> Is suggestion of using later wxWidgets version helpful? Is it possible? Later versions vere widely tested withDMC.

I intend to develop a Win16 application; 2.2.7 is the last wxWindows which has Win16 support
November 23, 2005
"Robert James Morales" <rmorales2005@gmail.com> wrote in message news:dlojmv$1ik0$1@digitaldaemon.com...
> On 11/19/2005 3:02 PM, W³odzimierz Skiba wrote:
>
> > Is suggestion of using later wxWidgets version helpful? Is it possible?
Later versions vere widely tested withDMC.
>
> I intend to develop a Win16 application; 2.2.7 is the last wxWindows which
has Win16 support

I really need the bug report so I can fix it. -Walter


November 24, 2005
On 11/22/2005 10:36 PM, Walter Bright wrote:
> I really need the bug report so I can fix it. -Walter

Removing the "-A" option seems to have allowed it to compile now. I'm just having issues with wxGrid (which I know is not supported in Win16, but the code seems to keep assuming it's there...)
November 24, 2005
On 11/23/2005 11:31 PM, I incorrectly wrote:

> Removing the "-A" option [...]

Sorry, that was not "-A": it was "-ml". (the wxGrid issue remains)
November 25, 2005
"Robert James Morales" <rmorales2005@gmail.com> wrote in message news:dm3ks3$2ivd$1@digitaldaemon.com...
> On 11/23/2005 11:31 PM, I incorrectly wrote:
>
> > Removing the "-A" option [...]
>
> Sorry, that was not "-A": it was "-ml". (the wxGrid issue remains)

I still need a reproducible example. Try compiling with -e -l and then try to reproduce the error by compiling the resulting .lst file.