public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin dot jansa at mk dot cvut dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/30915] [4.3 regression] bootstrap fails while building libstdc++-v3 on x86_64-pc-linux-gnu
Date: Sun, 11 Mar 2007 20:36:00 -0000	[thread overview]
Message-ID: <20070311203559.27334.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30915-7220@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from martin dot jansa at mk dot cvut dot cz  2007-03-11 20:35 -------
(In reply to comment #14)
downgrading glibc didn't that trick but now() I have successfully builded
latest snapshot with this "patch":

--- ./gcc-4.3-20070309/libstdc++-v3/include/c_global/cstdio.orig       
2007-03-11 20:12:59.000000000 +0100
+++ ./gcc-4.3-20070309/libstdc++-v3/include/c_global/cstdio     2007-03-11
20:14:00.000000000 +0100
@@ -46,7 +46,7 @@

 #include <bits/c++config.h>
 #include <cstddef>
-#include_next <stdio.h>
+#include "/usr/include/gentoo-multilib/amd64/stdio.h"

 #ifndef _GLIBCXX_CSTDIO
 #define _GLIBCXX_CSTDIO 1

There is list of \*stdio\* in build directory:
./build/gcc/include-fixed/stdio.h
./build/x86_64-pc-linux-gnu/libstdc++-v3/include/tr1/stdio.h
./build/x86_64-pc-linux-gnu/libstdc++-v3/include/tr1/cstdio
./build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/stdio_sync_filebuf.h
./build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/stdio_filebuf.h
./build/x86_64-pc-linux-gnu/libstdc++-v3/include/cstdio
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/man/man3/__gnu_cxx::stdio_sync_filebuf.3
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/man/man3/__gnu_cxx::stdio_filebuf.3
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/cstdio.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/class____gnu__cxx_1_1stdio__filebuf.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/stdio__filebuf_8h.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/stdio_8h.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/class____gnu__cxx_1_1stdio__sync__filebuf.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/tr1_2cstdio.xml
./build/x86_64-pc-linux-gnu/libstdc++-v3/docs/doxygen/xml/stdio__sync__filebuf_8h.xml
./build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/tr1/stdio.h
./build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/tr1/cstdio
./build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/ext/stdio_sync_filebuf.h
./build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/ext/stdio_filebuf.h
./build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/cstdio
./build/stage1-gcc/include-fixed/stdio.h
./build/prev-gcc/include-fixed/stdio.h
./gcc-4.3-20070309/gcc/testsuite/gcc.dg/cpp/usr/include/stdio.h
./gcc-4.3-20070309/libstdc++-v3/config/io/basic_file_stdio.cc
./gcc-4.3-20070309/libstdc++-v3/config/io/c_io_stdio.h
./gcc-4.3-20070309/libstdc++-v3/config/io/basic_file_stdio.h
./gcc-4.3-20070309/libstdc++-v3/testsuite/tr1/8_c_compatibility/cstdio
./gcc-4.3-20070309/libstdc++-v3/testsuite/27_io/ios_base/sync_with_stdio
./gcc-4.3-20070309/libstdc++-v3/testsuite/27_io/headers/cstdio
./gcc-4.3-20070309/libstdc++-v3/testsuite/ext/stdio_filebuf
./gcc-4.3-20070309/libstdc++-v3/testsuite/ext/stdio_sync_filebuf
./gcc-4.3-20070309/libstdc++-v3/include/c_std/cstdio
./gcc-4.3-20070309/libstdc++-v3/include/tr1/stdio.h
./gcc-4.3-20070309/libstdc++-v3/include/tr1/cstdio
./gcc-4.3-20070309/libstdc++-v3/include/c_global/cstdio
./gcc-4.3-20070309/libstdc++-v3/include/ext/stdio_sync_filebuf.h
./gcc-4.3-20070309/libstdc++-v3/include/ext/stdio_filebuf.h
./gcc-4.3-20070309/libstdc++-v3/include/c_compatibility/stdio.h
./gcc-4.3-20070309/libstdc++-v3/include/c/cstdio
./gcc-4.3-20070309/fixincludes/tests/base/stdio_tag.h
./gcc-4.3-20070309/fixincludes/tests/base/stdio.h
./gcc-4.3-20070309/libssp/ssp/stdio.h


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30915


  parent reply	other threads:[~2007-03-11 20:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 15:11 [Bug bootstrap/30915] New: " eesrjhc at bath dot ac dot uk
2007-02-22 23:47 ` [Bug libstdc++/30915] " pinskia at gcc dot gnu dot org
2007-02-23  2:00 ` pcarlini at suse dot de
2007-03-07  3:38 ` b33fc0d3 at gmail dot com
2007-03-07 19:06 ` pcarlini at suse dot de
2007-03-11 12:20 ` martin dot jansa at mk dot cvut dot cz
2007-03-11 12:29 ` martin dot jansa at mk dot cvut dot cz
2007-03-11 12:32 ` pcarlini at suse dot de
2007-03-11 12:53 ` pcarlini at suse dot de
2007-03-11 13:03 ` pcarlini at suse dot de
2007-03-11 13:05 ` pcarlini at suse dot de
2007-03-11 13:14 ` pcarlini at suse dot de
2007-03-11 13:26 ` pcarlini at suse dot de
2007-03-11 13:36 ` martin dot jansa at mk dot cvut dot cz
2007-03-11 13:46 ` pcarlini at suse dot de
2007-03-11 13:54 ` martin dot jansa at mk dot cvut dot cz
2007-03-11 20:36 ` martin dot jansa at mk dot cvut dot cz [this message]
2007-03-11 21:20 ` pcarlini at suse dot de
2007-03-12 20:49 ` b33fc0d3 at gmail dot com
2007-03-12 21:08 ` pcarlini at suse dot de
2007-03-12 22:30 ` martin dot jansa at mk dot cvut dot cz
2007-03-12 23:10 ` pcarlini at suse dot de
2007-03-12 23:32 ` pcarlini at suse dot de
2007-03-12 23:34 ` pinskia at gcc dot gnu dot org
2007-03-13 11:45 ` martin dot jansa at mk dot cvut dot cz
2007-03-19  9:30 ` eesrjhc at bath dot ac dot uk
2007-08-08  1:45 ` s_j_newbury at yahoo dot co dot uk
2007-08-08 13:19 ` eesrjhc at bath dot ac dot uk
2007-09-11 18:58 ` aldot at gcc dot gnu dot org
2007-09-11 19:08 ` jakub at gcc dot gnu dot org
2007-11-22 12:58 ` pcarlini at suse dot de
2008-06-07 13:35 ` paolo dot carlini at oracle dot com
2008-09-10 15:18 ` paolo dot carlini at oracle dot com
2008-09-12 10:38 ` lthode at mail dot unomaha dot edu

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=20070311203559.27334.qmail@sourceware.org \
    --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: link
Be 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).