From: Matthew Jordan <matthewjordandevops@yandex.com>
To: Alex Vong <alexvong1995@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: gccgo package does not include gccgo binary
Date: Tue, 12 Jul 2016 05:38:10 -0400 [thread overview]
Message-ID: <87h9bvyz5p.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87shvfmz38.fsf@gmail.com>
> Actually, I am trying to link object file compile with gcc with go
> object file. I was thinking using gccgo would make things simplier since
> the backend is the same. Anyway, I follows your suggestion to use 'go'
> command instead and find this guide
> <https://stackoverflow.com/questions/16747021/how-do-you-statically-link-a-c-library-in-go-using-cgo>
> on SO. The answer written by Didier basically works for me, except that
> '//#include <toto.h>' has to be replaced by '//#include <toto.h>' to get
> the code compiled. Have a good day :)
No problem, and you are welcome.
> Btw, does anyone have problem cloning github repo? I get the SSL
> verfication problem mentioned earlier. However, I have already installed
> nss-certs and include the following line in .bashrc:
> GIT_SSL_CAINFO="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt"
> export GIT_SSL_CAINFO
>
> Any ideas?
Add nss-certs to your system config.
$ $EDITOR /etc/config.scm
$ guix system reconfigure /etc/config.scm
That solved my SSL issues.
Cheers,
---
Matthew Jordan
next prev parent reply other threads:[~2016-07-12 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 14:55 gccgo package does not include gccgo binary Alex Vong
2016-07-09 18:23 ` Leo Famulari
2016-07-09 22:09 ` Matthew Jordan
2016-07-10 15:29 ` Alex Vong
2016-07-10 17:16 ` Matthew Jordan
2016-07-12 1:20 ` Alex Vong
2016-07-12 9:38 ` Matthew Jordan [this message]
2016-07-12 11:05 ` Alex Vong
2016-07-12 12:35 ` Leo Famulari
2016-07-12 14:13 ` Alex Vong
2016-07-12 13:23 ` Ludovic Courtès
2016-07-13 14:41 ` git ca cert problems Alex Vong
2016-07-13 21:11 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9bvyz5p.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me \
--to=matthewjordandevops@yandex.com \
--cc=alexvong1995@gmail.com \
--cc=help-guix@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: link
Be 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).