Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 576596

Summary: sys-devel/binutils-2.26 version bump
Product: Gentoo Linux Reporter: Petros <petros_20>
Component: [OLD] Core systemAssignee: Gentoo Toolchain Maintainers <toolchain>
Status: RESOLVED NEEDINFO    
Severity: enhancement    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build.log

Description Petros 2016-03-06 13:58:04 UTC
Created attachment 427576 [details]
build.log

media-plugins/gst-plugins-dv-1.6.3 fails to build because /usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/../../../../x86_64-pc-linux-gnu/bin/as tries to use libopcodes-2.26.51.20160306.so

libopcodes-2.26.51.20160306.so is part of binutils-2.26 and not of the current binutils-2.25
Comment 1 Alex Xu (Hello71) 2016-03-06 17:41:17 UTC
please paste output of "binutils-config -l".
Comment 2 Petros 2016-03-06 17:48:27 UTC
[1] x86_64-pc-linux-gnu-2.24.51.0.2
[2] x86_64-pc-linux-gnu-2.24.90
[3] x86_64-pc-linux-gnu-2.25.1
[4] x86_64-pc-linux-gnu-git *

Git version -> 
ld -v
GNU gold (Gentoo git 2.26.51.20160306) 1.11

Maybe last time I ran smart-live-rebuild binutils:git moved to 2.26. Either way sys-devel/binutils-2.26 should exist for those who don't want live packages.
Comment 3 SpanKY gentoo-dev 2016-03-08 16:59:00 UTC
while version 2.26 is pending (i'm not adding it because there's a bunch of regressions), that isn't relevant to this bug.  you're using a live git version, not the 2.26 release.

as itself should be linked using rpath's to its internal libs.  usually this error comes up because the build system is polluting LD_LIBRARY_PATH.

if you go into the build dir and run `make`, does it still fail ?
Comment 4 Petros 2016-03-09 14:28:16 UTC
(In reply to SpanKY from comment #3)
> if you go into the build dir and run `make`, does it still fail ?

After rebuilding binutils (smart-live-rebuild), gst-plugins-dv is installed without a problem.

So...I suppose the build process found the libopcodes it was searching for.