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

Bug#512817: marked as done (Unexplainable -include flag for compilation when using PCH)

Your message dated Mon, 09 May 2011 11:34:13 +0200
with message-id <4DC7B515.6050000@debian.org>
and subject line Compilation problems solved
has caused the Debian Bug report #512817,
regarding Unexplainable -include flag for compilation when using PCH
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
512817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512817
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qt4-qmake
Version: 4.4.3-2
Severity: normal

  Hello,

  I'm using qmake-qt4 to build a project named QCam, with the use of
precompiled headers (the project file is attached, in case there is
anything thing relevant in that). Every once in a while, when I
haven't compiled the project for a long time, it seems, I get very
weird errors:

~ make
g++ -c -include QCam -pipe -g -Wall -W -D_REENTRANT -DQT_PHONON_LIB -DQT_SQL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtSql -I/usr/include/phonon -I/usr/include/phonon -I/usr/include/qt4 -I. -Isrc -I. -I. -o database.o src/database.cc
[...]
./QCam:128: error: stray '\201' in program
./QCam:128: error: stray '\377' in program
./QCam:128: error: stray '\211' in program
./QCam:128: error: stray '\235' in program

  It seems that the effect of the -include QCam flag here is to actually include
the target binary as part of the source C++ files (here src/database.cc). 

  make clean is enough to work around the problem, but I still can't understand
the use of this -include flag, and I even can't understand why it works most
of the time.

  Why is that so ? Isn't it a bug of some kind ?

  Regards,

	Vincent

PS: I don't expect a fix any time soon anyway, but I'd be very greatful to
have an explanation, as I really don't understand the rationale behind this
-include stuff.


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages qt4-qmake depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  libgcc1                       1:4.3.2-4  GCC support library
ii  libstdc++6                    4.3.2-4    The GNU Standard C++ Library v3

qt4-qmake recommends no packages.

qt4-qmake suggests no packages.

-- no debconf information

# -*- mode: conf; -*-
# QMake configuration file for QCam

TEMPLATE = app
CONFIG += precompile_header debug
INCLUDEPATH += . src

VERSION = 0.1

QT += sql
QT += phonon

PRECOMPILED_HEADER = src/headers.hh

# Following lines for profiling
# QMAKE_CXXFLAGS += -pg
# QMAKE_LFLAGS += -pg

# We need libjpeg for file identification
LIBS += -ljpeg

# Input
SOURCES += src/qmain.cc src/mainwin.cc src/actions.cc \
	src/thumbnails.cc src/exif.cc src/thumblist.cc \
	src/database.cc src/viewer.cc \
	src/mixeddirmodel.cc 
HEADERS += src/mainwin.hh src/actions.hh \
	src/thumbnails.hh src/exif.hh src/thumblist.hh \
	src/database.hh src/viewer.hh \
	src/mixeddirmodel.hh

RESOURCES += data/resources.qrc

--- End Message ---
--- Begin Message --- 
  Hello,

  Long ago, I reported a puzzling problem with compilation failures
using PCH. Much later I found at that it was triggering only on g++
updates. The error still triggers on g++ updates, but now g++ also
complains about old and incompatible PCH, which makes it much easier to
understand what the problem is. I therefore consider that this bug has
been dealt with.

  Cheers,

      Vincent

-- 
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

Comme dit mon tonton: plus on est de cons, plus ça se voit !
 -- La Tordue, Où va-t-on

Vincent, listening to Siren Song (Bat for Lashes)

--- End Message ---
Reply to: