public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mtrudel at gmx dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30832] [regression] --with-sysroot=foobar wrong handled Date: Sat, 17 Feb 2007 12:24:00 -0000 [thread overview] Message-ID: <20070217122351.1207.qmail@sourceware.org> (raw) In-Reply-To: <bug-30832-13027@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from mtrudel at gmx dot ch 2007-02-17 12:23 ------- Update: It works if I copy the kernel-headers into $SYS_ROOT/usr/include instead of $SYS_ROOT/include. However, I really think this should not be required since it worked with gcc 4.2 and everything else is the same. So either it was a catastrophic build error on 4.2 and miracle that the compiled gcc worked (without linux/limits.h) or it's a regression now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30832
next prev parent reply other threads:[~2007-02-17 12:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-17 10:10 [Bug c/30832] New: " mtrudel at gmx dot ch 2007-02-17 10:16 ` [Bug c/30832] " schwab at suse dot de 2007-02-17 11:31 ` mtrudel at gmx dot ch 2007-02-17 12:12 ` schwab at suse dot de 2007-02-17 12:24 ` mtrudel at gmx dot ch [this message] 2007-02-17 14:31 ` schwab at suse dot de 2007-02-17 21:24 ` [Bug bootstrap/30832] " drow at false dot org 2007-02-19 8:26 ` mtrudel at gmx dot ch 2007-02-20 10:42 ` mtrudel at gmx dot ch
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=20070217122351.1207.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: 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).