[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded egcs 1.0.3a-0.1 (source i386) to master



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.5
Date: Sat, 16 May 1998 17:41:44 +0200
Source: egcs
Binary: g++ libstdc++2.8-dev egcc libstdc++2.8 gobjc g77 egcs-docs libg++2.8-dev libg++2.8
Architecture: source i386
Version: 1.0.3a-0.1
Distribution: frozen unstable
Urgency: low
Maintainer: J.H.M. Dassen (Ray) <jdassen@wi.LeidenUniv.nl>
Description: 
 egcc       - The GNU (egcs) C compiler.
 egcs-docs  - Documentation for the egcs compilers (egcc, gobjc, g++).
 g++        - The GNU (egcs) C++ compiler.
 g77        - The GNU (egcs) Fortran compiler.
 gobjc      - The GNU (egcs) Objective-C compiler.
 libg++2.8  - The GNU C++ extension library - runtime version.
 libg++2.8-dev - The GNU C++ extension library - development files.
 libstdc++2.8 - The GNU stdc++ library (egcs version)
 libstdc++2.8-dev - The GNU stdc++ library (development files)
Changes: 
 egcs (1.0.3a-0.1) frozen unstable; urgency=low
 .
   * New upstream release egcs-2.90.29 980515 (egcs-1.0.3 release)
     (we were using 1.0.3-prerelease).  This includes the Haifa patches
     we had since 1.0.3-0.2 and the gcc/objc/thr-posix.c patch we had
     since 1.0.3-0.1; the differences with 1.0.3-prerelease + patches
     we had is negligable.
   * iostream info documentation was in the wrong package (libg++2.8-dev).
     Now it's in libstdc++2.8-dev. (Thanks to Jens Rosenboom for bringing
     this to my attention). As 1.0.3-0.3 didn't make it out of Incoming,
     I'm not adding "Replaces:" for this; folks who had 1.0.3-0.3 installed
     already know enough to use --force-overwrite.
   * [gcc/objc/objc-act.c] Applied patch Matthias Klose supplied me with that
     demangles Objective C method names in gcc error messages.
   * Explicitly disable Haifa scheduling on Alpha, to make it easier to use
     this package's diff with egcs snapshots, which may turn on Haifa
     scheduling even though it is still unstable. (Requested by Chris Chimelis)
   * Don't run "configure" again if builddir already exists (makes it faster
     to restart builds in case one is hacking internals). Requested by
     Johnnie Ingram.
   * [gcc/gbl-ctors.h] Don't use extern declaration for atexit on glibc 2.1
     and higher (the prototype has probably changed; having the declaration
     broke Sparc compiles).
   * [debian/rules] Determine all version number automatically (from the
     version string in gcc/version.c).
   * [debian/copyright] Updated FTP locations; added text about libg++ (fixes
     #22465).
Files: 
 e1712849d044b8530b0f9b7716b3ec85 707 devel standard egcs_1.0.3a-0.1.dsc
 44ea51fdb369a96cb1c926b82b414567 9996934 devel standard egcs_1.0.3a.orig.tar.gz
 e299fb0f3ed21c400e3ce6870696a06b 696430 devel standard egcs_1.0.3a-0.1.diff.gz
 dfbc1797ce81cab685a60c5e4ce1419a 750254 devel extra egcc_2.90.29-0.1_i386.deb
 4598871ab59e4a7e8c0c6c25c2aa22b8 720100 devel optional gobjc_2.90.29-0.1_i386.deb
 c948ff8169fb608e8940ee2e64b62e7f 1242262 devel optional g77_2.90.29-0.1_i386.deb
 de83e4bb2175c4baf06e481835c6987f 1058972 devel optional g++_2.90.29-0.1_i386.deb
 69c0035b36180817b1b469f7efbe6339 89258 base required libstdc++2.8_2.90.29-0.1_i386.deb
 d003824baa2eb2bf5b6debe5b603a01c 540074 devel optional libstdc++2.8-dev_2.90.29-0.1_i386.deb
 ca93c1e9ed09a070d1b362841504574d 113814 libs optional libg++2.8_2.90.29-0.1_i386.deb
 588fcbafe07f7c2beebf4af91a819d79 569626 devel optional libg++2.8-dev_2.90.29-0.1_i386.deb
 9cf74c6e96838fe37c8676f75068c821 418246 devel optional egcs-docs_2.90.29-0.1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBNV3OlIcCuHlnLQXBAQGcqgP/e/IpsFcBzBN4oVlt7TBso32ohXKelfzb
fXioohxpGudi2dzeEEv4f0VnaK8PA0puzl21pqxUHx5ezFxK6zAo7MFQaLjO/bI4
Bto5gZVr71fnLIkDTNTZ6CpqUxZIGNsYQvDLID45uEAQmeVOcQ1O5Y8FW/9GT2pl
OCPNVjnU12k=
=Hh7+
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-devel-changes-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: