public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schmid at snake dot iap dot physik dot tu-darmstadt dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/14400] New: Cannot compile qt-x11-free-3.3.0 Date: Wed, 03 Mar 2004 08:35:00 -0000 [thread overview] Message-ID: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de> (raw) I submit this bugreport since the successful build of qt-x11-free is one of the release criteria for gcc 3.4 but I appologize for the low quality of this report since I was not able to get the propressed source output out of gcc which triggers the internal compiler error while compiling the file 3rdparty/ libpng/pngrtran.c of the qt-x11-free-3.3.0 distribution. Everytime I add -save-temps, gcc barfs with a cc1: qt: No such file or directory message. qt.gch is the name of the directory that is included via the -include qt directive while compiling. Appended are the error messages while comping pngrtran.c and the command line used for building the pch. Removing the -include directive allows a successful compilation of the file. Secondly, I do not know how to generate a .i file which contains all the files used for building the precompiled header. gcc -c -include qt -pipe -Wall -W -O2 -fPIC -DQT_SHARED -DQT_NO_DEBUG -DQT_NO_CUPS -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_IMAGEIO_MNG -DQT_NO_IMAGEIO_JPEG -DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE -DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC -I/home/peter/gnu/qt-x11-free-3.3.0/mkspecs/linux-g++ -I. -I/usr/include/freetype2 -I3rdparty/libpng -I3rdparty/zlib -I3rdparty/ opentype -I../include -I/usr/X11R6/include -I.moc/release-shared/ -o .obj/ release-shared/pngrtran.o 3rdparty/libpng/pngrtran.c In file included from 3rdparty/libpng/png.h:329, from 3rdparty/libpng/pngrtran.c:17: 3rdparty/zlib/zlib.h:75: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Command used for generating the precompiled header gcc -x c-header -c -pipe -Wall -W -O2 -fPIC -DQT_SHARED -DQT_NO_DEBUG -DQT_NO_CUPS -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_IMAGEIO_MNG -DQT_NO_IMAGEIO_JPEG -DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE -DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC -I/home/peter/gnu/qt-x11-free-3.3.0/mkspecs/linux-g++ -I. -I/usr/include/freetype2 -I3rdparty/libpng -I3rdparty/zlib -I3rdparty/ opentype -I../include -I/usr/X11R6/include -I.moc/release-shared/ kernel/ qt_pch.h -o qt.gch/c When I add -save-temps to command line given above, the file qt_pch.i contains: # 1 "kernel/qt_pch.h" # 1 "<built-in>" # 1 "<command line>" # 1 "kernel/qt_pch.h" I can submit the pngrtran.i file obtained by adding -save-temps to the command line. I do not know if that is of any use given the problems I mentioned earlier. -- Summary: Cannot compile qt-x11-free-3.3.0 Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: pch AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: schmid at snake dot iap dot physik dot tu-darmstadt dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400
next reply other threads:[~2004-03-03 8:35 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-03 8:35 schmid at snake dot iap dot physik dot tu-darmstadt dot de [this message] 2004-03-03 12:40 ` [Bug pch/14400] " giovannibajo at libero dot it 2004-03-03 16:44 ` pinskia at gcc dot gnu dot org 2004-03-04 6:07 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-04 7:03 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-17 5:50 ` mmitchel at gcc dot gnu dot org 2004-03-17 5:56 ` pinskia at gcc dot gnu dot org 2004-03-25 6:57 ` pinskia at gcc dot gnu dot org 2004-03-26 8:01 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-27 7:03 ` ian at wasabisystems dot com 2004-03-30 1:42 ` geoffk at gcc dot gnu dot org 2004-03-30 7:07 ` ian at wasabisystems dot com 2004-04-01 1:17 ` geoffk at apple dot com 2004-04-02 15:18 ` ian at wasabisystems dot com 2004-04-02 19:16 ` geoffk at apple dot com 2004-04-04 3:39 ` ian at wasabisystems dot com 2004-04-05 20:40 ` [Bug pch/14400] [3.4 regression] " ian at wasabisystems dot com 2004-04-05 20:54 ` mrs at apple dot com 2004-04-05 22:50 ` geoffk at apple dot com 2004-04-06 0:39 ` ian at wasabisystems dot com 2004-04-06 13:34 ` [Bug pch/14400] [3.4/3.5 " ian at wasabisystems dot com 2004-04-07 18:01 ` mmitchel at gcc dot gnu dot org 2004-04-07 18:34 ` mueller at kde dot org 2004-04-07 18:53 ` ian at wasabisystems dot com 2004-04-07 19:21 ` mark at codesourcery dot com 2004-04-07 19:22 ` [Bug pch/14400] " pinskia at gcc dot gnu dot org 2004-04-07 19:35 ` ian at wasabisystems dot com 2004-04-07 20:44 ` ian at wasabisystems dot com 2004-04-12 21:11 ` mmitchel at gcc dot gnu dot org 2004-04-12 22:07 ` geoffk at gcc dot gnu dot org 2004-04-12 22:45 ` ian at wasabisystems dot com 2004-04-12 23:13 ` geoffk at apple dot com 2004-04-13 15:07 ` ian at wasabisystems dot com 2004-04-13 18:38 ` geoffk at gcc dot gnu dot org 2004-04-13 19:48 ` ian at wasabisystems dot com 2004-04-13 19:53 ` geoffk at gcc dot gnu dot org 2004-05-29 22:54 ` [Bug pch/14400] [pch] " mmitchel at gcc dot gnu dot org 2004-06-18 23:57 ` mmitchel at gcc dot gnu dot org 2004-08-23 20:55 ` mmitchel at gcc dot gnu dot org 2004-11-01 0:47 ` mmitchel at gcc dot gnu dot org 2005-04-14 0:28 ` pinskia at gcc dot gnu dot org 2005-05-19 17:50 ` mmitchel at gcc dot gnu dot org 2005-08-02 19:04 ` cvs-commit at gcc dot gnu dot org 2005-08-02 19:05 ` ian at airs dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).