delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2004/04/18/13:58:13

X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Sun, 18 Apr 2004 20:51:30 +0200
From: "Eli Zaretskii" <eliz AT gnu DOT org>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <2719-Sun18Apr2004205129+0300-eliz@gnu.org>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
Subject: GCC source distribution
Reply-To: djgpp-workers AT delorie DOT com

I'm looking at gcc-3.3.3.tar.gz from ftp.gnu.org and at gcc333s2.zip,
and I see quite a few files that are patched before the DJGPP port of
GCC is built.  While I understand why this is done for files like the
configure script, other files, like config/i386/djgpp.h, are specific
to the DJGPP port, and so it would make sense to submit these changes
to the GCC maintainers for inclusion in a future official releases.

Is there any reason why this wasn't done?  The disadvantage of the
current situation is that one cannot easily say what defaults are
built into the DJGPP port of GCC by merely looking at the official GCC
tarball or the GCC CVS tree.  For an example of an ensuing confusion,
see the recent discussion on the GDB mailing list, in particular these
messages:

  http://sources.redhat.com/ml/gdb-patches/2004-04/msg00130.html
  http://sources.redhat.com/ml/gdb-patches/2004-04/msg00133.html

Andris, is it possible to include at least some of the diffs in the
official distro?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019