Bug 493146

Summary:	cross-armv6j-hardfloat-linux-gnueabi/binutils-2.23.2 - Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: .../work/patch
Product:	Gentoo Linux	Reporter:	Reuben Martin <reuben.m>
Component:	[OLD] Core system	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED NEEDINFO
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Build log emerge info environment Build log - glibc environ environment - glibc patch-output - glibc emerge debug log

Description Reuben Martin 2013-12-02 18:15:41 UTC

I'm trying to setup distcc for a raspberry pi, and I'm having a hell of a time getting crossdev to work.

Each package seems to fail in the unpacking phase, not being able to find a file or directory of some sort. I can kind of fix it by hand, but then the next package fails in the same manner.

Also, not sure if it has anything to do with it, but the failure is always preceded by a "vecho command not found" error. (I was under the impression vecho had been stripped out of ebuilds quite some time ago)



Reproducible: Always

Comment 1 Reuben Martin 2013-12-02 18:16:21 UTC

Created attachment 364462 [details]
Build log

Comment 2 Reuben Martin 2013-12-02 18:16:36 UTC

Created attachment 364464 [details]
emerge info

Comment 3 Reuben Martin 2013-12-02 18:16:56 UTC

Created attachment 364466 [details]
environment

Comment 4 Reuben Martin 2013-12-03 15:29:56 UTC

After manually unpacking the patches for binutils manually, the package builds. However the next package (glibc) also fails in the unpacking phase. I'm attaching it's build log as well.

Comment 5 Reuben Martin 2013-12-03 15:30:38 UTC

Created attachment 364532 [details]
Build log - glibc

Comment 6 Reuben Martin 2013-12-03 15:30:56 UTC

Created attachment 364534 [details]
environ

Comment 7 Reuben Martin 2013-12-03 15:31:30 UTC

Created attachment 364536 [details]
environment - glibc

Comment 8 Reuben Martin 2013-12-03 15:37:31 UTC

Created attachment 364538 [details]
patch-output - glibc

Comment 9 SpanKY gentoo-dev

2013-12-03 16:14:06 UTC

sounds like something is fundamentally broken in your system.  does it only happen with cross packages, or does it happen with other ones ?

is your portage install broken ?  try `qcheck portage`.

do you have weird bashrc hooks ?  or portage env settings ?

you can run `emerge --debug pkg >& log` and post that output as an attachment

Comment 10 Reuben Martin 2013-12-03 17:03:48 UTC

I'm thinking that is probably the case as well, because I was able to get it to build on a separate system. However, I can't seem to figure out what it is. Normal portage stuff outside of cross packages works fine.

'qcheck portage' checks out ok

The only thing I've added to bashrc is "source /etc/profile"

No custom portage env settings (that I'm aware of)

I'll add the debug log from 'emerge --oneshot --nodeps --debug cross-armv6j-hardfloat-linux-gnueabi/glibc >& debug.log'

Comment 11 Reuben Martin 2013-12-03 17:04:10 UTC

Created attachment 364542 [details]
emerge debug log

Comment 12 SpanKY gentoo-dev

2013-12-07 07:58:18 UTC

you have ridiculous CFLAGS.  use something sane like:
  CFLAGS="-O2 -march=native -pipe"
same goes for CXXFLAGS.

then rebuild your glibc/gcc/binutils/patch/portage/python/bash programs and see if the problem fixes itself.