Uploaded gcc 2.95.2-0pre2 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Sun, 19 Sep 1999 17:44:50 +0200
Source: gcc
Binary: g++ cpp gobjc libg++2.8.1.3-dbg cpp-doc libstdc++2.10-dev libg++2.8.1.3 chill gcc gcc-doc gcj g77 libstdc++2.10-dbg g77-doc libg++2.8.1.3-dev libstdc++2.10
Architecture: m68k
Version: 2.95.2-0pre2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@m68k.debian.org>
Description:
chill - The GNU Chill compiler.
cpp - The GNU C preprocessor.
g++ - The GNU C++ compiler.
g77 - The GNU Fortran 77 compiler.
gcc - The GNU C compiler.
gcj - The GNU compiler for Java(TM).
gobjc - The GNU Objective-C compiler.
libg++2.8.1.3 - The GNU C++ extension library - runtime version.
libg++2.8.1.3-dbg - The GNU C++ extension library - debugging files.
libg++2.8.1.3-dev - The GNU C++ extension library - development files.
libstdc++2.10 - The GNU stdc++ library
libstdc++2.10-dbg - The GNU stdc++ library (debugging files)
libstdc++2.10-dev - The GNU stdc++ library (development files)
Closes: 43478 45067 45293
Changes:
gcc (2.95.2-0pre2) unstable; urgency=low
.
* Updated to cvs updates of the gcc-2_95-branch until 19990919.
* Close bug already fixed in 2.95.2-0pre1 (closes: #43478).
* Tighten debhelper dependency to 2.0.50 (2.0.49 has a bug triggered by
the gcc package).
* Previous version had Pascal examples missing in doc directory.
* gobjc depends on libgc5-dev, reenabled ObjC-GC for alpha architecture
(tested by Christopher C Chimelis).
* debian/control.in: Increase priority of libstdc++-dev to Standard
(closes: #45293).
* debian/README: Fix typo (fixes #45253).
* Patch from Ben Collins <bcollins@debian.org>:
- Corrections in various debian/rules* files.
- What I have done in rules2 is to add two new vars, MULTILIBS and
MULTIDIRS. The first lists what libs get packages when there are
generated multilibs (stdc++, g++, gcc, objc...), and the second is a
globable representation of the dirs for multilibs (like "64" or
"{32,64}"). These are used later down when setting up which files go
into each package. I have this setup for sparc and sparc64 right now.
- I also have a sparc64-linux-gcc-wrapper.c file included in the patch
that is compiled and installed for sparc-linux. This is used for the
sparc64-linux-gcc alternative. It does two things, 1) adds -m64 to the
command line to get 64bit objects, 2) if -mmedlow is passed, it
converts it to -mcmodel=medlow (kernel compiles use the old -mmedlow,
while new gcc's look for -mcmodel=medlow) for compatibility.
* Make doc -> share/doc links in scripts for packages, where dh_installdocs
is not called (closes: #45067).
Files:
871cb8c098b077a83ecfcaa438ce0018 824226 devel standard gcc_2.95.2-0pre2_m68k.deb
20989fa499242d6d9dd4a2add56d736b 83804 interpreters standard cpp_2.95.2-0pre2_m68k.deb
6aa8b6127328e17cdf1ce926addcbfaf 876498 devel optional g++_2.95.2-0pre2_m68k.deb
c441b37ae7496f3caf729a72de289187 687138 devel optional gobjc_2.95.2-0pre2_m68k.deb
d479de0cbf8ab4a7c247c7bf6bac2003 880496 devel optional g77_2.95.2-0pre2_m68k.deb
f013018f36824b0df6bf2c8871af447f 705852 devel optional chill_2.95.2-0pre2_m68k.deb
59405ad2df2600edf19db2120573e51f 738646 devel optional gcj_2.95.2-0pre2_m68k.deb
37e7349e4c728843005d862193630141 105888 base required libstdc++2.10_2.95.2-0pre2_m68k.deb
4c42597f1944393dbb65ff25b8a786be 281452 devel standard libstdc++2.10-dev_2.95.2-0pre2_m68k.deb
f85682e90fe0fb8d19300e3ddea48361 296598 devel extra libstdc++2.10-dbg_2.95.2-0pre2_m68k.deb
b4d0149f338bb2710254a7074ebbdcc1 108554 libs optional libg++2.8.1.3_2.95.2-0pre2_m68k.deb
7c1499021945165f4eb7707b714fab7f 299428 devel optional libg++2.8.1.3-dev_2.95.2-0pre2_m68k.deb
e99e0f1f60146b46913960343ea6fce7 290608 devel extra libg++2.8.1.3-dbg_2.95.2-0pre2_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAwUBN+neq3VhJ0HiWnvJAQEScAQAy0qqRqlGsw42f1uUYziqGZnA0LzOgiCd
j16iYxiKCQ8AbAC5EfSuodRLgJz0GtQ+ozBShzWg0fn84cdZ23sp0yaBJXIVMpFF
AeIHt/dIviz6s3IXx/Q+66dsyFE/I5RbgXMFQ1H8PSoGh0agyodqrrbmntPaZcjR
1Pizs9RUbhY=
=T2U3
-----END PGP SIGNATURE-----
Reply to: