Note: I don't see this on go1.9

I checked out https://bitbucket.org/ausocean/av, and ran git checkout librtmpPorting, but there is no src directory there. Can you give precise directions for reproducing the problem starting from scratch? Thanks.

/cc @randall77 @josharian

@gopherbot please open a backport issue as this might be a 1.10 regression.

Backport issue(s) opened: #26402 (for 1.10).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.

@FiloSottile in the future, can we wait on backport setup until we can reproduce?

I looked into this.

It seems like you hardcoded in a few places that the librtmp you are using with cgo can be found in /usr/local/lib. In fact, when I try to build the c dependencies of your project using make, it instructs me to run sudo make install-deps, which I have no intention to do.

Please provide a reproducer that can be compiled without the requirement of running a make command from root, if possible.

I'll amend the comment I wrote above since it sounds unnecessarily harsh.

What I wanted to say is that, in general, Go contributors and the Go Devs will be able to help much quicker if the reproducer attached to a bug is easy to build. In this case I downloaded your repository, looked into it, and I found out that building it -apparently- requires to run a make command from root, to move headers you depend on into a specific system folder. Since running arbitrary commands from root is something that may have harmful consequences, anyone investigating your report may be unwilling to do that, and this will slow down the investigation. For this reason, we usually ask the reporter to try to make the reproducer as small, simple, and easy to build as possible.

I ended up committing past the problem. I'm going to rebase and create a new branch. I'll also provide instructions for building the C stuff in the program dir rather than in /usr/local. And apologies for making it more difficult to investigate. I'm quite a busy boy currently - once I went back to go1.9 and got it working, I nearly forgot about the issue.

@Saxon1 is this still an issue? W/o a way to reproduce we cannot act on this. Please let us know if you can provide more detailed information, or close the issue.

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

I've closed the backport bug as well.

@josharian thanks!