Bugzilla Bug 224237

Performing an emerge for dbus-1.2.1 fails with an emake failed. This is on a
Fulong based mips workstation, Loongson CPU.

I have tried different methods to get this to work, and each time the build
fails at exactly the same point. It is so close to getting actually finished...
it looks like a post step in the ebuild process is broken somewhere.

Reproducible: Always

Steps to Reproduce:
1. emerge dbus

Actual Results:  
The first error is thus:

*** glibc detected ***
/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/../../../../mipsel-unknown-linux-gnu/bin/ld:
double free or corruption (out): 0x009848f0 ***
collect2: ld terminated with signal 6 [Aborted]
/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/../../../../mipsel-unknown-linux-gnu/bin/ld:
BFD 2.17 assertion fail
/var/tmp/portage/sys-devel/binutils-2.17-r1/work/binutils-2.17/bfd/elfxx-mips.c:10114
/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/../../../../mipsel-unknown-linux-gnu/bin/ld:
BFD 2.17 assertion fail
/var/tmp/portage/sys-devel/binutils-2.17-r1/work/binutils-2.17/bfd/elfxx-mips.c:2508
/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/../../../../mipsel-unknown-linux-gnu/bin/ld:
BFD 2.17 assertion fail
/var/tmp/portage/sys-devel/binutils-2.17-r1/work/binutils-2.17/bfd/elfxx-mips.c:2508

The assertion fail then occurs about 1000 times on the same line (2508) until
we get to the following:

/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/../../../../mipsel-unknown-linux-gnu/bin/ld:
BFD 2.17 assertion fail
/var/tmp/portage/sys-devel/binutils-2.17-r1/work/binutils-2.17/bfd/elfxx-mips.c:2508
make[2]: *** [dbus-daemon-launch-helper-test] Error 1
make[2]: Leaving directory
`/tmp/portage/sys-apps/dbus-1.2.1/work/dbus-1.2.1/bus'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/portage/sys-apps/dbus-1.2.1/work/dbus-1.2.1'
make: *** [all] Error 2
 * 
 * ERROR: sys-apps/dbus-1.2.1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2803:  Called die
 * The specific snippet of code:
 *       emake || die "make failed"
 *  The die message:
 *   make failed
 * 
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/tmp/portage/sys-apps/dbus-1.2.1/temp/build.log'.
 * The ebuild environment file is located at
'/tmp/portage/sys-apps/dbus-1.2.1/temp/environment'.
 * 

 * Messages for package sys-apps/dbus-1.2.1:

 * 
 * ERROR: sys-apps/dbus-1.2.1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2803:  Called die
 * The specific snippet of code:
 *       emake || die "make failed"
 *  The die message:
 *   make failed
 * 
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/tmp/portage/sys-apps/dbus-1.2.1/temp/build.log'.
 * The ebuild environment file is located at
'/tmp/portage/sys-apps/dbus-1.2.1/temp/environment'.
 * 


Expected Results:  
dbus should have built fine.

I will also attach the output of "emerge --debug dbus" to this report.

Created an attachment (id=154841) [details]
Output of "emerge --debug dbus"

this fails on the O2-5K with binutils-2.18 as well.  it works with
binutils-2.18.50.0.7 but that version has a different showstopper issue on
mips.  i was looking into this when my O2's power supply died a couple weeks
ago.

(In reply to comment #2)
> this fails on the O2-5K with binutils-2.18 as well.  it works with
> binutils-2.18.50.0.7 but that version has a different showstopper issue on
> mips.  i was looking into this when my O2's power supply died a couple weeks
> ago.
> 

Currently the version of binutils I have installed is binutils-2.18-r1. Not
sure if this is going to help at all. 

I have an odd listing of binutils:

kiona binutils # binutils-config -l
 [1] mips64-unknown-linux-gnu-2.18 *

 [2] mipsel-unknown-linux-gnu-2.17 *
 [3] mipsel-unknown-linux-gnu-2.18

If I switch to mipsel-unknown-linux-gnu-2.18, it makes things even worse. I
have not tried installing binutils-2.18.50.0.7 on this machine, and at the
moment I think I may want to avoid doing that in the first place.

This may just have to be a wait and see thing to see if a new version of either
binutils or dbus fixes the issue.

Just tested against  sys-apps/dbus-1.2.3 and it is still failing with the exact
same problem.