//go.dev/issue/54197
>
>
> - sean
>
> On Wed, Aug 31, 2022, 21:35 Shane wrote:
>
>> I was finally able to compile the bootstrap on Linux (I had to install
>> the missing libc).
>>
>> However, after copying the .tbz file onto my Solaris 11u4 AMD64
, Aug 27, 2022 at 12:15 PM Shane wrote:
> >
> > My understanding then is that cmd/dist first builds for the host here
> (in my case, for Linux) and then builds for the target starting here. Since
> there is always a build for the host first, then since my host OS is Linux,
>
2 at 2:59:31 PM UTC-4 se...@liao.dev wrote:
> make.bash calls cmd/dist which does the build chaining, calling it
> directly doesn't skip the process.
>
> - sean
>
> On Sat, Aug 27, 2022, 19:54 Shane wrote:
>
>> > Is there some way I can skip straight to building
led, and then I would not get the compiler error I am seeing.
On Saturday, August 27, 2022 at 2:40:52 PM UTC-4 Shane wrote:
> I already have a working Go 1.19 for Linux with cgo support on my build
> machine that I downloaded and installed from https://go.dev. Given this,
> is it still
I already have a working Go 1.19 for Linux with cgo support on my build
machine that I downloaded and installed from https://go.dev. Given this, is
it still necessary to build for the host? Is there some way I can skip
straight to building Go for my Solaris target using my existing Linux Go
too
es this mean that whatever I set for GOOS when I run either boostrap.bash
or make.bash is always ignored?
On Saturday, August 27, 2022 at 12:53:48 PM UTC-4 Brian Candler wrote:
> On Saturday, 27 August 2022 at 17:10:21 UTC+1 Shane wrote:
>
>> Is it expected that linux_syscall.c would b
10:52:47 PM UTC-4 Ian Lance Taylor wrote:
> On Thu, Aug 18, 2022 at 5:05 PM Shane wrote:
> >
> > I'm not sure what you mean when you ask which C library version I am
> using. Are you asking the version of my libc?
> >
> > I am cross-compiling on Debian 10 using
f the Go source tree is compiled by Go). My
target is Solaris 11.
On Wednesday, August 17, 2022 at 10:16:10 PM UTC-4 Ian Lance Taylor wrote:
> On Wed, Aug 17, 2022 at 4:28 PM Shane wrote:
> >
> > I am trying to follow what I believe to be the official instructions for
> buildin
s being treated as errors
go tool dist: FAILED:
/some/redacted/parent/dirs/go/goroot/pkg/tool/linux_amd64/go_bootstrap
install std cmd: exit status 2
I am building on Linux. I have gcc and Go 1.19 installed on my Linux
system, and both tools are on my PATH.
I am looking for help fixing the
On Wednesday, July 29, 2020 at 7:23:22 PM UTC+10, mb0 wrote:
>
> This is a special kind of switch called a type switch. You can read more
> about it in the language specification where its part of the intrinsic
> go syntax. https://golang.org/ref/spec#Switch_statements
>
> Because it is a spec
Hrm, that bpaste site will only last a week, so, for posterity, I'll paste
the script here
#!/bin/bash if [[ "$#" -ne 1 ]]; then echo "No filename supplied, nothing
to do" exit 0 fi INFILE="$1" echo "=== In file
===" cat $INFILE echo
"===
Thanks, I have a bash script that I use to examine the assembly code that
is generated by a given go file
https://bpa.st/MRJ4IWJFJ5YNHXFLCMMYGGSI3A
But that takes me past the code that was used to generate that assembly
I'm wanting the midpoint here, the code that the compiler sees, in order to
Hi all, I'm trying to understand what *exactly* the .(type) is doing in the
following statement
switch foo := bar.(type)
I mean, I get that foo is being assigned a type converted version of the
bar interface, but, I want to see what exactly they .(type) call does.
I have
found https://github.
OMG, it was my *test* that was modifying the value... Thanks so much for
your time
On Monday, April 6, 2020 at 4:24:10 PM UTC+10, Jakob Borg wrote:
>
> Hi Shane,
>
> This doesn't happen with your example:
> https://play.golang.org/p/C3zb6Qyx-2f
>
> Can you provide
I know that it's documented that the json encoder will produce base64 "Array
and slice values encode as JSON arrays, except that []byte encodes as a
base64-encoded string", but I am getting a base64 response when I pass in a
string
response := []string
response = append(response,
"http://local
On Monday, March 23, 2020 at 2:49:46 PM UTC+11, Ian Lance Taylor wrote:
>
> On Sun, Mar 22, 2020 at 7:10 PM Shane H >
> wrote:
> >
> > I'm a lot confused by the behaviour of some tests I have at the moment,
> they're skipping.. when there's no skip o
I'm a lot confused by the behaviour of some tests I have at the moment,
they're skipping.. when there's no skip or timeout or... anything that I
can see
I know this is going to be difficult because I don't have code I can paste
to show what's happening
I'm using go1.13.9, but this behaviour wa
On Sunday, January 26, 2020 at 1:49:15 PM UTC+11, Shane H wrote:
>
> Hi all, I'm trying to learn how to write a linter (because long weekend,
> etc)
>
> I looked at Fatih's very fine blog post (
> https://arslan.io/2019/06/13/using-go-analysis-to-write-a-custom-li
Hi all, I'm trying to learn how to write a linter (because long weekend,
etc)
I looked at Fatih's very fine blog post (
https://arslan.io/2019/06/13/using-go-analysis-to-write-a-custom-linter/)
as well as the one that precedes it, although I was a LOT lost reading that
one.
Copying and pasting
On Saturday, December 28, 2019 at 5:23:27 AM UTC+11, Ignacio Grande wrote:
>
> Hi!
>
> I have an application I made a few years ago for a friend which sends
> emails using a Gmail account with STMP, using the library
> gopkg.in/gomail.v1. Since then I moved on and I'm not familiar with
> lates
On Tuesday, November 19, 2019 at 4:11:52 PM UTC+11, burak serdar wrote:
>
>
>
> This is what I usually do in these situations:
>
> var amqpDial=amqp.Dial
> func (mq *MQ) Connect() (err error) {
> ...
>mq.conn, err = amqpDial(mq.URI)
> ...
> }
>
> func TestConnect(t *testing.T) {
I'm trying to unit test some code (pasted below). I've struggled to find a
way to mock the amqp.Connection, so have decided to go the monkey patching
route.
The test 'works' but only if I use the following incantation
go test -gcflags=-l
So, my next step is to ensure that -gcflags is set to pr
xit status 1: go build go/src/runtime/cgo: package using cgo
has Go assembly file asm_amd64.s"
Any help on either or both issues appreciated (even if it's just a link to
"This is how you do what you're trying to do")
$ golangci-lint run -v ./...
INFO [config_reader] C
>
>
> This looks like you unpacked a Go distribution into a directory that
> already held another Go distribution. Always unpack a Go distribution
> into an empty directory.
>
> Ian
>
You could well be right, I think (from my perspective) the bigger issue is
managing a Go installation on Ub
On Tuesday, August 6, 2019 at 11:31:40 AM UTC+10, Shane H wrote:
>
>
>
> On Tuesday, August 6, 2019 at 10:56:42 AM UTC+10, Shane H wrote:
>>
>> Hi all,
>>
>> I've done a bit of searching, and asked around, but not found an answer
>> to my (most li
On Tuesday, August 6, 2019 at 10:56:42 AM UTC+10, Shane H wrote:
>
> Hi all,
>
> I've done a bit of searching, and asked around, but not found an answer to
> my (most likely self-inflicted) problem.
>
> I have been coding with Go 1.10 and 1.11 for a whiles, but I deci
lling
the OS
This is probably best demonstrated as:
shane@desktop ~/GoLang/src/github.com/ipfs/go-ipfs (master) $ make build
go version go1.12.7 linux/amd64
bin/check_go_version 1.12
go build "-asmflags=all='-trimpath=/home/shane/GoLang'"
"-gcflags=all='-tr
On Sat, Aug 18, 2018 at 2:56 PM John wrote:
>
> Hi I am trying to make an game of Connect Five using Golang, I have
> already made an player versus player mode so I am making the player versus
> computer mode.
I think what you are looking for is adversarial graph search, min/max
with al
Hmm I meant to reply to the group but I think I inadvertantly replied
directly (my apologies).
I'll repost my answer because I think that it may help others with the same
issue (the multi line examples!)
Hi
There are two ways to use examples with multi line outputs
1) Multi line comments (Be aw
29 matches
Mail list logo
