X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=39MFKdfIgmntoCYcqIGIZQlvPNRX5SPUsuZXQoc4FEk=;
        b=bGJdcI1P+UHj1AvpjWEwtryCah14CmxR891hTShBasQyGWYHnE1TFkH6eYL2I/bIcx
         mcdKmZsvRLLf+ABKCckM/xfcFRaYLmgpHryW/T0QECrjZAO0VZi5u+KHA62+2ZDHn5Sv
         CnLBdzRQgP10yF+HQbN6FVTDP0TYcuNFZNR3crUVUGXXmr9etzqViddLfWvG/qDJslqK
         dUb3YY/D/jdN1CJDjLYrOivQhH7GuAlFgh2by3iQegDnB4ODCO0mKX9ezzQI1628ZvHf
         XIDC2oDuBp8OBSyrnBmEUCLwpTf0H87S9eD4UN1SVMXF3AzmSBVzStQBncimmAv3Jqgg
         lhPw==
X-Received: by 10.107.136.38 with SMTP id k38mr20524177iod.56.1434142580383;
        Fri, 12 Jun 2015 13:56:20 -0700 (PDT)
Message-ID: <557B4772.3070900@gmail.com>
Date: Fri, 12 Jun 2015 16:56:18 -0400
From: "Frank Sapone (emoaddict15 AT gmail DOT com)" <djgpp AT delorie DOT com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: DJGGP 2.05 upgrade problems.
References: <201506091712 DOT t59HCPci004068 AT delorie DOT com>	<557739E0 DOT 6070608 AT gmail DOT com>	<CAB9Rao93XrKFBpUDnZdjCz+rEXHGOU2RNKdou2oMLJOk802LnA AT mail DOT gmail DOT com>	<55775E64 DOT 2090901 AT gmail DOT com>	<CAB9Rao-Njdr-CB=vqHnb+TVDmXu3eXqsB5CHB7V0kDwBEsM-WQ AT mail DOT gmail DOT com>	<5579ED42 DOT 6070309 AT gmail DOT com> <CAB9Rao8cvu3hLEf=KsRWn7woXka0F9Aax7uM9Jj5QqCO=1bL8w AT mail DOT gmail DOT com> <5579FE8D DOT 3080501 AT gmail DOT com> <557B436F DOT 1050101 AT gmx DOT de>
In-Reply-To: <557B436F.1050101@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com


> First I would seriously suggest that you add the -save-temps flag to 
> you CFLAGS.
> This saves the intermediary files for inspection.
>
Okay, I will try that next time while using 2.05.
> Second, you are using programs from the /beta directory compiled with 
> djdev204
> or djdev205.  Some of them have been compiled with NLS support 
> enabled.  The NLS
> support is provided by the gettext and iconv libraries that have been 
> compiled
> as DXE3 modules.  This means that the programs like make or grep have 
> been linked
> with these DXE3 modules or dlls.  No mather if you 
> like/use/enable/disable NLS on
> your system the libraries MUST be installed because the programs 
> linked with them
> try to find them at start.  If they cannot be found then the program 
> aborts with
> an error output like this:
>
> H:\q2dos>make
> libintl.DXE: module loading failed (No such file or directory (ENOENT))
> Abort!
> Exiting due to signal SIGABRT
> Raised at eip=00027604
> eax=000ed9b8 ebx=00000120 ecx=00000008 edx=00000000 esi=00025334 
> edi=000252d9
> ebp=000ee598 esp=000ed9a4 program=C:\DJGPP-2.04\BIN\MAKE.EXE
> cs: sel=01a7  base=02990000  limit=000fffff
> ds: sel=01af  base=02990000  limit=000fffff
> es: sel=01af  base=02990000  limit=000fffff
> fs: sel=017f  base=00008f00  limit=0000ffff
> gs: sel=01bf  base=00000000  limit=0010ffff
> ss: sel=01af  base=02990000  limit=000fffff
> App stack: [000ee608..0006e60c]  Exceptn stack: [0006e52c..0006c5ec]
>
> Call frame traceback EIPs:
>   0x000323ea
>
> Installing gettext and iconv is mandatory.
>
These are installed now, but like I said i was getting SIGILL now. Not 
sure if these utilites need to be recompiled with 2.05 to work properly.
> The important issue here is to understand that the inclusion of 
> sys/cdefs.h
> provides the definition of the macro _EXTERN_INLINE.  An inspection of 
> the
> preprocessor file shows that the WATT32 package provides its one 
> version of
> sys/cdefs.h stored in C_INCLUDE_PATH=/dev/env/DJDIR/net/watt/inc
> and this version seems to inhibit the expansion of _EXTERN_INLINE,
> causing the compiler abort.  Futher investigations needs to be done to 
> see
> how the headers of WATT32 port needs to be fixed.
>
>
Do you think yo ucould take a closer peek at WATT32?  If you do, can you 
put it in GIT or some other versioning utility so I can learn how you 
changed it to make it work.  I'm fairly new to playing around
with fixing up utilities to work on newer compilers.