Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 566836 - =dev-go/sanitized-anchor-name-0_pre20150822: In golang-build_src_compile at line 1459 (no message provided)
Summary: =dev-go/sanitized-anchor-name-0_pre20150822: In golang-build_src_compile at l...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: William Hubbs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-25 16:48 UTC by Alex Brandt (RETIRED)
Modified: 2015-11-29 21:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
build output (1448469827-install-dev-go_sanitized-anchor-name-0_pre20150822:0::gentoo.out,3.35 KB, application/octet-stream)
2015-11-25 16:48 UTC, Alex Brandt (RETIRED) 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Brandt (RETIRED) gentoo-dev 2015-11-25 16:48:21 UTC 
When attempting to build app-emulation/docker-1.9.1 after removing the entire go stack, go-1.5 is pulled in (successfully) but this package errors for literally no reason.

Reproducible: Always
Comment 1 Alex Brandt (RETIRED) gentoo-dev 2015-11-25 16:48:45 UTC 
Created attachment 417852 [details]
build output
Comment 2 Alex Brandt (RETIRED) gentoo-dev 2015-11-25 16:49:18 UTC 
I'm sure I'm missing some information on this bug, just let me know what would be useful.  I use paludis instead of portage so some information may be slightly different.
Comment 3 Brian Evans (RETIRED) gentoo-dev 2015-11-25 18:34:04 UTC 
Please don't forget to assign your own bugs since you can.
Comment 4 Alex Brandt (RETIRED) gentoo-dev 2015-11-25 19:45:21 UTC 
Hey Brian,

I thought that was automated since it's just a lookup on an ebuild anyway.  My apologies.
Comment 5 Alex Brandt (RETIRED) gentoo-dev 2015-11-29 21:00:44 UTC 
I'm not sure if this is still a valid bug.  I found that go had injected spurious source files in my /usr/lib/go directory that were causing a mess of problems. 

I'll close this for now but feel free to re-open if it crops up elsewhere.