unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 47928@debbugs.gnu.org
Subject: bug#47928: go-gopkg-in-yaml-v2-2.2.2 build fails
Date: Fri, 30 Apr 2021 18:21:25 -0400	[thread overview]
Message-ID: <87bl9vl8gq.fsf@disroot.org> (raw)
In-Reply-To: <20210428024559.1b9293f3@riseup.net>

raingloom writes:

> On Mon, 26 Apr 2021 17:39:58 -0400
> Bone Baboon <bone.baboon@disroot.org> wrote:
>
>> raingloom writes:
>> > My guess is that int is 32 bits on i686.  
>> 
>> The computer's CPU is 32 bit.
>> 
>> How would I check if "int is 32 bits on i686"?
>
> Looking up an authoritative source (ie.: "the docs") is one way. Here
> is what I found:
>
> https://tour.golang.org/basics/11
>  The int, uint, and uintptr types are usually 32 bits wide on 32-bit
>  systems and 64 bits wide on 64-bit systems. When you need an integer
>  value you should use int unless you have a specific reason to use a
>  sized or unsigned integer type. 
>
>
> Another would be to try to do an operation that would wrap around, but
> if you aren't familiar with binary arithmetic in the language in
> question, just looking it up is probably easier.

Thank you for sharing this.




  reply	other threads:[~2021-04-30 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  1:46 bug#47928: go-gopkg-in-yaml-v2-2.2.2 build fails Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:17 ` raingloom
2021-04-26 21:39   ` Bone Baboon via Bug reports for GNU Guix
2021-04-28  0:45     ` raingloom
2021-04-30 22:21       ` Bone Baboon via Bug reports for GNU Guix [this message]
2021-04-30 22:28 ` Bone Baboon via Bug reports for GNU Guix
2021-05-03  3:28 ` Bone Baboon via Bug reports for GNU Guix

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=87bl9vl8gq.fsf@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=47928@debbugs.gnu.org \
    --cc=bone.baboon@disroot.org \
    --cc=raingloom@riseup.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).