Package: gcc-2.95
Version: 1:2.95.3-10
Severity: serious
$ /usr/lib/gcc-lib/i386-linux/2.95.3/cc1 -quiet -dumpbase reg_ld_str.c
-mpreferred-stack-boundary=2 -march=i386 -O2 -Wall -Wstrict-prototypes -version
-fomit-frame-pointer -fno-strict-aliasing -o reg_ld_str.o reg_ld_str.i
GNU C version 2.9
Steve Langasek writes:
> On Fri, 30 Mar 2001, David Schleef wrote:
>
> > On Fri, Mar 30, 2001 at 02:34:48PM -0600, Steve Langasek wrote:
>
> > > > Any comment on the /usr/lib/gcc-lib/*/*/include files? I
> > > > noticed that the gcc build process is supposed to be able to
> > > > create f
Hakan Ardo writes:
> Hi,
> I have now succesfully produced an gcc-avr deb from the
> gcc-3.0_3.0.ds4-0pre010403 sources. To get it working I had to do some minor
> modifications, patches are attached. If you want it done in some other way
> just tell me an I'll fix it (if you don't prefer to d
On Sun, 8 Apr 2001, Matthias Klose wrote:
> > Ah... Yes, I recognize these symptoms now. I had to run strace against the
> > build process to find it myself. You see, gcc doesn't need the include
> > files to be in /usr/lib/gcc-lib, but it does need the *directories* to be
> > there -- not b
Package: gcc-3.0-base
Version: 1:3.0-0pre010403
Severity: wishlist
The section quoting the standard part 4.4/4 uses the soft hyphen at
several places. Why, I don't understand; it seems like a hyphen is
called for, not the ambigiously non-graphic soft hyphen. However,
not all character sets have
5 matches
Mail list logo
