Package: gcc-3.3
Version: 1:3.3.1-0pre0
Severity: normal
File: /usr/bin/gcc-3.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
cc -ansi -std=c99 -pedantic -Wall -Werror -I'/usr/include/mysql' -c -o
AniMatrixMaker.o AniMatrixMaker.c
In file included from AniMatrixMaker.c:1:
/usr/include/mysql/my
On Mon, 2003-05-19 at 01:39, Martin v. Löwis wrote:
> cpp.texi:This manual contains no Invariant Sections. The Front-Cover Texts
> are
[...]
> So cpp.texi is free documentation; the others contain invariant sections.
-legal isn't too happy with front or back cover texts, either.
severity 175353 important
thanks
On Wednesday, May 14, 2003, at 08:20 PM, Colin Watson wrote:
Why is this filed as a serious bug? It causes harm (at least in theory,
if there are people who really share /usr/share with Debian) to have a
file incorrectly in /usr/share; it causes no harm to have a fi
reopen 175353
thanks
Many (if not most) libraries have the same ABI on every architecture.
Examples:
>From gcc-3.2-3.2.3ds9:
cp -p $(srcdir)/libstdc++-v3/config/linker-map.gnu \
$(d_pic)/$(gcc_lib_dir)/libstdc++_pic.map
(file is created during debian/rules unpack)
On Sun, 2003-03-16 at 16:24, Daniel Jacobowitz wrote:
> If it weren't for the disk/archivespace/maintenance/PITA cost I'd
> suggest binary-i686. Things being what they are, maybe we should poll
> for people interested in new versions of Debian on i386; I doubt we can
> drop 586, since I've seen u
On Thu, 2003-02-06 at 12:51, Es Que wrote:
> When I use apt to install gcc2.95, it automatically installs 3.2.2. In fact,
> I think I'm running both versions. I need to compile a the 2.4.19 kernel
> using gcc 2.95.
doesn't using "gcc-2.95" as the compiler instead of "gcc" work?
signature.asc
D
salt-generator-pp.c.bz2
Description: Binary data
Package: gcc-3.2
Version: 1:3.2.1-0pre3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
gcc-3.2 -Wall -pedantic -ansi -Werror -march=i486 -mcpu=i486 -Os\
-Wunreachable-code -g -o salt-generator salt-generator.c
cc1: warnings being treated as errors
salt-generator.c:
On Saturday, January 18, 2003, at 11:44 AM, Falk Hueffner wrote:
The declaration
int x[2, 3];
is not legal in C99, since "2, 3" is not an assignment-expression.
I'm not a C99 language lawyer, but are you sure? Is the comma operator
allowed there, or would one have to write "int x[(2,3)]" to get th
On Fri, 2003-01-03 at 19:30, Phil Edwards wrote:
> If it would help, libstdc++ also has such a file in its sources.
cp linker-map.gnu /usr/lib/gcc-lib/i386-linux/3.2.1/libstdc++_pic.map
fixed the warnings. Thank you!
Please add it to the libstdc++5-pic deb!
signature.asc
Description: This is
On Fri, 2003-01-03 at 05:13, Matthias Klose wrote:
> How to avoid this?
Not sure. The libc6-pic package doesn't suffer from this warning. The
major difference I see quickly is some "libc_pic.map" file which lists
symbols by version (apparently).
Having that map file appears to make mklibs call t
Package: libstdc++5-pic
Version: 1:3.2.1-0pre3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When using mklibs w/ libstdc++5-pic to build minimal shared libs for an
embedded system, I get warnings like this:
specialmap-reader: /lib/libstdc++.so.5: no version information availabl
reopen 174626
severity 174626 important
reassign 174626 apt
thanks
On Sun, 2002-12-29 at 11:05, Matthias Klose wrote:
> this is not a bug. leave the unstable sources only and get gcc-3.2
> from unstable.
Errm, 3.2.1-0pre3 is still in the archive[0]. Thus, per the GPL, the
source must be as well.
Package: libstdc++5
Version: 1:3.2.1-0pre3
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bohr:/home/anthony# apt-get build-dep libstdc++5=1:3.2.1-0pre3
Reading Package Lists... Done
Building Dependency Tree... Done
E: Unable to find a source package for libstdc++5
bohr:/home/ant
On Tuesday, December 3, 2002, at 05:16 AM, Francesco Potorti` wrote:
Sorry if this is not a bug, but I cannot find any way why it isn't.
This is due to a rather old change in the C++ standard. I think it was
between the second and third edition of the Stroustrup book, but I
could be mistaken.
Th
Package: libstdc++3
Version: 1:3.0.3-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It'd be nice to have __STL_ASSERTIONS or equivelant come back to do
things like bounds-check vector accesses (yes, I know about at()) for
debugging purposes.
- -- System Information
Debian Rel
On Friday, January 4, 2002, at 08:17 , Morten Brix Pedersen wrote:
mbp:~$ g++ benchmark.cpp ; ls -l a.out ; time a.out ; g++-3.0
benchmark.cpp
; ls -l a.out ; time a.out
Well, first, take . out of your path! I get:
-rwxr-xr-x1 anthony anthony 42840 Jan 5 23:46 a.out
real0m7.870s
use
Package: gcc
Version: 2:2.95.4-8
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I realize this is probably implemented easily, but a warning about
asserts with obvious side effects would be nice. For example:
assert(ptr = malloc(...)) /* programmer didn't understa
Package: g++-3.0
Version: 1:3.0.2-3
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Accidentally leaving the close brace off of a block in e.g., a header
file will often result in errors in files that include it, without any
indication of what is wrong. For example, leaving a nam
19 matches
Mail list logo
