[gstreamer-bugs] [Bug 572532] New: OpenEmbedded crosscompiling failes due to selection of wrong staging libdir in latest releases of -base, -good, -bad, -ugly

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=572532

  GStreamer | gst-plugins | Ver: 0.10.x
           Summary: OpenEmbedded crosscompiling failes due to selection of
                    wrong staging libdir in latest releases of -base, -good,
                    -bad, -ugly
           Product: GStreamer
           Version: 0.10.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: andreas.frisch at multimedia-labs.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
I used to be able to crosscompile the gstreamer plugin packages using
OpenEmbedded and Bitbake for mips32 architecture just like that. Releases 
gst-plugins-good_0.10.13.bb and gst-plugins-base_0.10.22.bb now require a
modification of all the libdir variables in all the
.../build/tmp/staging/mipsel-linux/lib/libgst*-0.10.la files to 
libdir='.../build/tmp/staging/mipsel-linux/lib/' where #libdir='/usr/lib' used
to work fine and still select the target-architecture symbols correctly. 

i haven't tested with bad and ugly 0.10.10 since they are depended on base but
i assume the same problem there.


Steps to reproduce:
in openembedded, create packages for gst-plugins-*, based upon copies of the
previous revisions and bitbake ...

Actual results:
except from openembedded compile log:

libtool: link:  ccache mipsel-linux-gcc -shared 
.libs/libgsttag_0.10_la-gstvorbistag.o .libs/libgsttag_0.10_la-gstid3tag.o
.libs/libgsttag_0.10_la-tags.o .libs/libgsttag_0.10_la-gsttagdemux.o  
-Wl,-rpath
-Wl,/dream/dm8000/build/tmp/work/gstreamer-0.10.22-r0/gstreamer-0.10.22/gst/.libs
-Wl,-rpath -Wl,/dream/dm8000/build/tmp/staging/mipsel-linux/lib/ -Wl,-rpath
-Wl,/dream/dm8000/build/tmp/staging/mipsel-linux/lib -Wl,-rpath
-Wl,/dream/dm8000/build/tmp/staging/mipsel-linux/lib/
-L/dream/dm8000/build/tmp/work/gstreamer-0.10.22-r0/gstreamer-0.10.22/gst/.libs
-L/dream/dm8000/build/tmp/staging/mipsel-linux/lib/.libs
-L/dream/dm8000/build/tmp/staging/mipsel-linux/lib /usr/lib/libgstbase-0.10.so
/dream/dm8000/build/tmp/work/gstreamer-0.10.22-r0/gstreamer-0.10.22/gst/.libs/libgstreamer-0.10.so
/dream/dm8000/build/tmp/staging/mipsel-linux/lib//libgstreamer-0.10.so -lrt
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libgobject-2.0.so
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libgmodule-2.0.so
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libgthread-2.0.so -lpthread
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libxml2.so -ldl
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libz.so -lm
/dream/dm8000/build/tmp/staging/mipsel-linux/lib/libglib-2.0.so 
-Wl,-rpath-link -Wl,/dream/dm8000/build/tmp/staging/mipsel-linux/lib -Wl,-O1
-pthread -pthread   -pthread -Wl,-soname -Wl,libgsttag-0.10.so.0
-Wl,-version-script -Wl,.libs/libgsttag-0.10.ver -o
.libs/libgsttag-0.10.so.0.16.0
/usr/lib/libgstbase-0.10.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status

it uses my amd64 host machine's libs instead of the staging target architecture
one's

Expected results:
make should succeed, like in the previous releases

Does this happen every time?
yes

Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=572532.