Bug 532704

Summary:	dev-lang/yasm-1.2.0-r1 - ?
Product:	Gentoo Linux	Reporter:	aabarkley3
Component:	[OLD] Development	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	aabarkley3
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description aabarkley3 2014-12-16 14:08:13 UTC

Reproducible: Always

Steps to Reproduce:
1. # emerge -1 yasm

Comment 1 Andrew Miller 2014-12-17 01:25:17 UTC

Please give some more information so I can look into this bug.

1. Click "Add an attachment" and attach the full build log.
2. Put the output of "emerge --info" as a comment.
3. Tell us about the host. Which version of Ubuntu is it running and which architecture, 32-bit or 64-bit?

Comment 2 aabarkley3 2014-12-17 02:44:55 UTC

I think you meant Gentoo, not Ubuntu. For now, see http://forums.gentoo.org/viewtopic-p-7650490.html. I'm away from that system right now. My situation seems similar to the one in that forum post, if not identical. When I am at that system again I will post my build log and info.

Comment 3 Andrew Miller 2014-12-17 05:31:08 UTC

>I'm attempting to build a gentoo chroot inside of an ubuntu install

You need to supply some basic information (version and architecture) about the Ubuntu host. This could be a distro-specific bug caused by the Ubuntu kernel.

Comment 4 Jeroen Roovers (RETIRED) gentoo-dev

2014-12-17 06:09:22 UTC

1) Please post your `emerge --info' output in a comment.
2) Please attach the entire build log to this bug report.

Comment 5 aabarkley3 2014-12-18 22:08:16 UTC

This was in a VirtualBox virtual machine on Windows 8.1.

Comment 6 Jeroen Roovers (RETIRED) gentoo-dev

2014-12-19 07:22:29 UTC

(In reply to Jeroen Roovers from comment #4)
> 1) Please post your `emerge --info' output in a comment.
> 2) Please attach the entire build log to this bug report.