public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stgraber at stgraber dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/65404] cgo tool on powerpc-linux-gnu maybe incomplete Date: Fri, 13 Mar 2015 16:53:00 -0000 [thread overview] Message-ID: <bug-65404-4-aCIdmdtnLE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65404-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65404 --- Comment #7 from Stéphane Graber <stgraber at stgraber dot org> --- So with the cherry-picked fix, I get: (vivid-powerpc-sbuild)root@winton-06:~# cat test.go package main /* #include <stdio.h> now void hello() { printf("Hello world!\n"); } */ import "C" func main() { C.hello() } (vivid-powerpc-sbuild)root@winton-06:~# go build -v -x test.go WORK=/tmp/go-build320378268 command-line-arguments mkdir -p $WORK/command-line-arguments/_obj/ cd /root CGO_LDFLAGS="-g" "-O2" /usr/lib/gcc/powerpc-linux-gnu/5/cgo -objdir $WORK/command-line-arguments/_obj/ -gccgo -- -I $WORK/command-line-arguments/_obj/ test.go # command-line-arguments ./test.go:13:5: call of non-function C.hello So cgo is now supported and I don't have to force it with CGO_ENABLED=1 but I still can't use my cgo function. >From gcc-bugs-return-480307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 13 16:58:25 2015 Return-Path: <gcc-bugs-return-480307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 44972 invoked by alias); 13 Mar 2015 16:58:25 -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 44902 invoked by uid 48); 13 Mar 2015 16:58:16 -0000 From: "stgraber at stgraber dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/65404] cgo tool on powerpc-linux-gnu maybe incomplete Date: Fri, 13 Mar 2015 16:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stgraber at stgraber dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65404-4-0YPHXBOlae@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65404-4@http.gcc.gnu.org/bugzilla/> References: <bug-65404-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-03/txt/msg01451.txt.bz2 Content-length: 256 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65404 --- Comment #8 from Stéphane Graber <stgraber at stgraber dot org> --- Mathias suggested this may be #65417 but I'm not familiar enough with gccgo and cgo to know whether that's the case or not. >From gcc-bugs-return-480308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 13 17:02:31 2015 Return-Path: <gcc-bugs-return-480308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 71213 invoked by alias); 13 Mar 2015 17:02:31 -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 71170 invoked by uid 48); 13 Mar 2015 17:02:28 -0000 From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/65404] cgo tool on powerpc-linux-gnu maybe incomplete Date: Fri, 13 Mar 2015 17:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ian at airs dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65404-4-irXYyEHtl8@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65404-4@http.gcc.gnu.org/bugzilla/> References: <bug-65404-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: 2015-03/txt/msg01452.txt.bz2 Content-length: 150 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide404 --- Comment #9 from Ian Lance Taylor <ian at airs dot com> --- It could be due to PR 65417, yes.
prev parent reply other threads:[~2015-03-13 16:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-12 14:49 [Bug go/65404] New: " doko at gcc dot gnu.org 2015-03-12 16:02 ` [Bug go/65404] " ian at airs dot com 2015-03-12 16:04 ` doko at gcc dot gnu.org 2015-03-12 16:27 ` stgraber at stgraber dot org 2015-03-12 16:42 ` ian at gcc dot gnu.org 2015-03-12 16:46 ` ian at airs dot com 2015-03-13 16:53 ` stgraber at stgraber dot org [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-65404-4-aCIdmdtnLE@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).