From:	ebling AT premiernet DOT net (Stuart Ebling)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Linking DJGPP v2.0 compiled libraries with v2.01 built executables
Date:	Wed, 01 Jan 1997 15:32:00 GMT
Organization:	PremierNET, Inc.
Lines:	50
Message-ID:	<32ca80fe.1166716@nntp.premiernet.net>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970101080836 DOT 15959E-100000 AT is>
NNTP-Posting-Host:	slip22.premiernet.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

>
>On Tue, 31 Dec 1996, Stuart Ebling wrote:
>
>> The question I have is, should I anticipate any problems mixing an
>> object module compiled with DJ 2.0 with an executable built using the
>> DJ 2.01 'suite'.
>
>I don't understand how an object file can be mixed with an executable 
>program, so I cannot really answer your precise question.  
Forgive my wording, I am executing a make that will perform many steps
... compiling, linking, etc.  This is all being done with 2.01
executables and all of the libraries being linked have previously been
compiled with 2.01, except for one object file for which I currently
do not have the source. This one object is being linked in also during
the process of building the executable file.

>However, in 
>general it's a bad idea to mix any components of v2.0 with any other 
>components from v2.01.  Most of the combinations will work most of the 
>time, but produce subtle, difficult-to-debug bugs in some rare cases.  If 
>you don't mind living dangerously, you can leave things as they are now 
>and upgrade when Gnat gets upgraded to v2.01.
>
>Here's a list of a few things that might make trouble:
>
>	1) Mixing objects/libraries compiled by different versions in a
>single executable.  
Gee, maybe we should forgive your wording also :-)
>This is an absolute no-no, because some functions
>defined by both versions have different parameters/return values, so you
>get bugs, crashes etc. 
>
>	2) Calling v2.0 programs from v2.01 programs (like when the 
>compilation driver calls the passes of the compiler/assembler/linker).  
>This will fail for some (but not all) long command lines, or when 
>wildcards are passed to the subsidiary programs.
>
>	3) LFN handling (if you work on Windows 95) is different, v2.0 
>programs might sometimes fail to support them.
>
>Bottom line: upgrade Gnat to v2.01 as fast as you can.

But you answered my question anyway, Thanks.


--
Stuart Ebling
ebling AT premiernet DOT net

- Raw text -