Mail Archives: djgpp-workers/1998/04/09/06:59:59
--Message-Boundary-6639
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Hi
Here are some notes about DJGPP port of gcc. Version currently
available from v2gnu/alphas still have some problems to be fixed to
final release (to be honest my previous build from March 31 was
better than released one). I'm giving way how to fix some of them in
attachment to this e-mail.
Andris
--Message-Boundary-6639
Content-type: text/plain; charset=US-ASCII
Content-disposition: inline
Content-description: Attachment information.
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any another MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: gcc281
Date: 9 Apr 1998, 13:57
Size: 2088 bytes.
Type: Text
--Message-Boundary-6639
Content-type: Application/Octet-stream; name="gcc281"; type=Text
Content-disposition: attachment; filename="gcc281"
Release notes about DJGPP port of gcc-2.8.1
Summary: version from March 31 (not released) was better than one uploaded
to delorie.com. Here are notes about some problems with uploaded version.
A.Pavenis 9 Apr 1998
----------------------------------------------------------------------------
1) duplicate files in archives (DJ Delorie, 98/04/07)
lib/gcc-lib/djgpp/2.81/include/typeinfo in gpp281b.zip and gcc281b.zip
lang/cxx/header.gcc in lgp2811b.zip and gpp281b.zip
I think that common files in between sources and binary archives
should still stay.
----------------------------------------------------------------------------
2) looks that it is necessary to remove
#define DIR_SEPARATOR "\\"
from config/i386/xm-go32.h (archive gcc281s.zip). And return to use
'/' (default) as directory separator. Using "\\" here breaks RHIDE
(Project->Includes) and maybe something else. To fixing this one currently
should rebuild gcc from sources. Should be fixed in final version
(98/04/08)
----------------------------------------------------------------------------
3) problem with link_command_specs if no output file is specified (no -o
parameter is specified, e.g. 'gcc hello.cc'). In this situation stubify
is called with incorrect parameters. A temporary workaround is to
patch %DJDIR/lib/gcc-lib/2.81/specs. In final version I'll change this
in internal specs of gcc. (98/04/09)
*** specs~ Wed Apr 1 12:09:18 1998
--- specs Thu Apr 9 12:36:12 1998
***************
*** 70,74 ****
%{!nostdlib:%{!nodefaultlibs:%G %L %G}}\
%{!A:%{!nostdlib:%{!nostartfiles:%E}}}\
-Tdjgpp.djl %{T*}}}}}}}
! %{!c:%{!M:%{!MM:%{!E:%{!S:stubify %{v} %{o*:%*} %{!o*:a.out}}}}}}
--- 70,74 ----
%{!nostdlib:%{!nodefaultlibs:%G %L %G}}\
%{!A:%{!nostdlib:%{!nostartfiles:%E}}}\
-Tdjgpp.djl %{T*}}}}}}}
! %{!c:%{!M:%{!MM:%{!E:%{!S:stubify %{v} %{o*:%*} %{!o*:a.out} }}}}}
----------------------------------------------------------------------------
--Message-Boundary-6639--
- Raw text -