Results for 3.3.2 20030908 (Debian prerelease) testsuite on m68k-unknown-linux-gnu

2003-09-12 Thread Matthias Klose
LAST_UPDATED: Mon Sep 8 19:46:09 UTC 2003 Native configuration is m68k-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/abi/bitfield4.C execution test FAIL: g++.dg/abi/empty6.C (test for warnings, line 6) FAIL: g++.eh/spec3.C Execution test FAIL: g++.eh/sp

Processed: Merge cpp bugs

2003-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > merge 210478 210482 Bug#210478: cpp-3.3: cpp generates files with weird characters Bug#210482: cpp: cpp generates files with weird characters Merged 210478 210482. > thanks Stopping processing here. Please contact me if you need assistance. Debian bu

Bug#210482: first.S attached.

2003-09-12 Thread Falk Hueffner
This is caused by cpp inserting a spurious newline after occurrance of a macro with arguments withourt parentheses (which it is supposed to leave alone): [EMAIL PROTECTED]:/tmp% cat first.S #define S(x) foobar foo ! S bar [EMAIL PROTECTED]:/tmp% cpp-3.2 < first.S # 1 "" # 1 "" # 1 "" # 1 "" foo !

Bug#210482: first.S attached.

2003-09-12 Thread Andrés Roldán
#if 0 ; first.S - LILO first stage boot loader with LBA32 support */ Copyright 1992-1998 Werner Almesberger. Copyright 1999-2003 John Coffman. All rights reserved. Licensed under the terms contained in the file 'COPYING' in the source directory. #endif #define LILO_ASM #include "lilo.h" get c

Bug#210482: cpp: cpp generates files with weird characters

2003-09-12 Thread Falk Hueffner
[EMAIL PROTECTED] (Andrés Roldán) writes: > I was trying to compile a program with the latest cpp version and I > got the following error (I'm sorry for the verbosity): > > cpp-3.3 -DLILO=0x489b `( if [ -r $ROOT/etc/lilo.defines ]; then cat > $ROOT/etc/lilo.defines; else echo -DBDATA -DDSECS

Bug#210565: Recent regression: x is an inaccessible base of y (within gtkmm2)

2003-09-12 Thread Christof Petig
Package: g++-3.3 Version: 1:3.3.2-0pre3 Very recently (3.3.2ds1-0pre2 was ok AFAIK) the name lookup mechanisms changed in g++. This exposes problems with libgtkmm2.0-dev Version 2.2.7-1. Since g++-3.2 does not complain this looks like a compiler issue (and not gtkmm's fault) - but I can't tell f