After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749461 - faad2 plugin can't recognize faad2 version due to GCC-5.0 preprocessor changes
faad2 plugin can't recognize faad2 version due to GCC-5.0 preprocessor changes
Status: RESOLVED DUPLICATE of bug 748571
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.4.5
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-16 06:11 UTC by Gabriel Marcano
Modified: 2015-05-16 06:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gst-plugins-faad-1.4.5-configure-ac-gcc-5-fix.patch (682 bytes, patch)
2015-05-16 06:11 UTC, Gabriel Marcano
none Details | Review

Description Gabriel Marcano 2015-05-16 06:11:37 UTC
Created attachment 303457 [details] [review]
gst-plugins-faad-1.4.5-configure-ac-gcc-5-fix.patch

When building the faac plugin for gst-plugins-bad, GCC-5.0 changed the behavior of the -E preprocessor flag. This breaks autoconf's AC_EGREP_CPP behavior used to extract the version number of the faac2 library. I was able to patch the configure script for version 1.4.5 of gst-plugins-bad (see https://bugs.gentoo.org/show_bug.cgi?id=549612 for details on that). configure.ac still needs to be fixed.

In theory, according to the GCC porting docs, the only new flag that needs to be added to CPPFLAGS somehow is "-P." I am attaching a patch that does just that, which saves the CPPFLAGS, appends "-P", lets AC_EGREP_CPP do its job, and then restores the original CPPFLAGS. I've tested it on my system (Gentoo Linux, unstable, GCC 5.1) and it works, although I don't really like having to mess with CPPFLAGS directly. Thought?
Comment 1 Sebastian Dröge (slomo) 2015-05-16 06:36:27 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 748571 ***