public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/52266] New: [4.7 Regression] syntax error in libgo/configure Date: Wed, 15 Feb 2012 22:20:00 -0000 [thread overview] Message-ID: <bug-52266-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52266 Bug #: 52266 Summary: [4.7 Regression] syntax error in libgo/configure Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go AssignedTo: ian@airs.com ReportedBy: doko@gcc.gnu.org seen in 4.7.0, not 4.6.2: checking for stdint.h... yes checking for unistd.h... yes /scratch/packages/gcc/4.7/gcc-4.7-4.7-20120210/src/libgo/configure: line 4750: #include: command not found checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking how to print strings... printf configure: [...] eval as_val=\$$as_ac_Header if test "x$as_val" = x""yes; then : cat >>confdefs.h <<_ACEOF #define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi done $ac_includes_default { $as_echo "$as_me:${as_lineno-$LINENO}: checking for a sed that does not truncate output" > &5 $as_echo_n "checking for a sed that does not truncate output... " >&6; } if test "${ac_cv_path_SED+set}" = set; then : $as_echo_n "(cached) " >&6 else [...]
next reply other threads:[~2012-02-15 21:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-15 22:20 doko at gcc dot gnu.org [this message] 2012-02-16 10:44 ` [Bug go/52266] " rguenth at gcc dot gnu.org 2012-02-17 15:45 ` ian at gcc dot gnu.org 2012-02-17 15:46 ` 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=bug-52266-4@http.gcc.gnu.org/bugzilla/ \ --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).