public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "info at yourkit dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/28097] error: ÂPATH_MAXÂ undeclared (first use in this function) when building cross compiler Date: Tue, 20 Jun 2006 16:59:00 -0000 [thread overview] Message-ID: <20060620163839.10941.qmail@sourceware.org> (raw) In-Reply-To: <bug-28097-9424@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from info at yourkit dot com 2006-06-20 16:38 ------- Actually the problem was solved (in our case) by copying header files from Solaris machine to $PREFIX/sysroot/usr/include dictory and additing "--with-sysroot=$PREFIX/sysroot" to configuration options. Binutils also need to have "--with-sysroot=$PREFIX/sysroot" option. But we are getting stuck with bug #28101 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28097
prev parent reply other threads:[~2006-06-20 16:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-20 15:24 [Bug c++/28097] New: error: PATH_MAX " info at yourkit dot com 2006-06-20 15:26 ` [Bug bootstrap/28097] " pinskia at gcc dot gnu dot org 2006-06-20 15:26 ` [Bug target/28097] " pinskia at gcc dot gnu dot org 2006-06-20 16:59 ` info at yourkit dot com [this message]
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=20060620163839.10941.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).