public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "typesylph at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/51844] configuring with --with-gxx-include-dir=<absolute path> adds a relative (non-existing) C++ include dir Date: Thu, 18 Jul 2013 15:34:00 -0000 [thread overview] Message-ID: <bug-51844-4-btb2aBg8za@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51844-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51844 Sylpheed <typesylph at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |typesylph at gmail dot com --- Comment #5 from Sylpheed <typesylph at gmail dot com> --- Please try these patches for trunk(4.9.0). 1. gcc/gcc.c line 2548 < if (sysroot_len > 0 --- > if (sysroot_len > 1 2. gcc/incpath.c line 182 < if (sysroot_len > 0 && sysroot[sysroot_len - 1] == DIR_SEPARATOR) --- > if (sysroot_len > 1 && sysroot[sysroot_len - 1] == DIR_SEPARATOR) There patch is for 'host-compiling' with '--withsysroot=/'. Anyother promrems defferent env('cross-compiling') the other problem may be. >From gcc-bugs-return-426356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jul 18 15:49:56 2013 Return-Path: <gcc-bugs-return-426356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 20715 invoked by alias); 18 Jul 2013 15:49:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 17907 invoked by uid 48); 18 Jul 2013 15:47:53 -0000 From: "lailavrazda1979 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57926] New: Atomic functions broken with C++ but not C? Date: Thu, 18 Jul 2013 15:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: lailavrazda1979 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-57926-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-07/txt/msg00863.txt.bz2 Content-length: 653 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW926 Bug ID: 57926 Summary: Atomic functions broken with C++ but not C? Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com Note that this possible bug does not trigger with GCC, only G++. Try compiling the code in the attachment with g++. It'll give strange errors, including complaining that an argument must be a non-void pointer when it IS in fact, a non-void pointer.
prev parent reply other threads:[~2013-07-18 15:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-13 8:59 [Bug driver/51844] New: [4.7 regression] " doko at gcc dot gnu.org 2012-01-13 10:12 ` [Bug driver/51844] " rguenth at gcc dot gnu.org 2012-01-13 20:23 ` jakub at gcc dot gnu.org 2012-01-17 11:41 ` rguenth at gcc dot gnu.org 2012-01-25 14:34 ` jakub at gcc dot gnu.org 2012-01-25 16:33 ` doko at gcc dot gnu.org 2013-07-18 15:34 ` typesylph at gmail 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=bug-51844-4-btb2aBg8za@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).