[gstreamer-bugs] [Bug 326683] New: problem building gst-plugins-good

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=326683
 GStreamer | gst-plugins-good | Ver: HEAD CVS

           Summary: problem building gst-plugins-good
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: opensolaris
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: brian.cameron at sun.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I notice a problem when I try to build gst-plugins-good.  Because
AS_LIBTOOL_TAGS has ([CXX]) as an argument, it tries to use the C++ compiler
for doing the 
following "nm" check in configure.

checking command to parse /usr/ccs/bin/nm -p output from $compiler object

But the problem is that if this command ends up compiling a test program and
the compile program it ends up generating uses the C++ compiler but the CFLAGS
I have set up, which isn't valid for the C++ compiler.

This causes configure to think it fails, and the generated libtool doesn't set
global_symbol_pipe right, and the module build breaks when it tries to link.

I'm attaching a simple patch that removes the "([CXX])" from this macro, which
makes things work better.  I notice that this is how the gst-plugins-base
works.  I don't know why we are specifying using the C++ compiler here since
gst-plugins-good doesn't even have any C++ code in it.

Can this patch go into the build?  Otherwise we'll need to patch the code
locally with this change to get gst-plugins-good to build with out build
system.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.