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 563371 - tags are screwed up
tags are screwed up
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: common
0.10.6
Other Mac OS
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-05 19:50 UTC by Ben Denckla
Modified: 2009-04-10 22:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ben Denckla 2008-12-05 19:50:42 UTC
I am trying to find an official set of sources for gst-ffmpeg that works with the latest stable releases of everything else in gstreamer.  By "official" I mean a tarball or CVS tag.

Because of bug 563305, the 10.6 tarball is no good, so I decided to try to use CVS tag RELEASE-0_10_6.

This gives the following error in configure.ac described at the bottom of this email.

Is this what user 'slomo' was trying to fix with his recent checkin to configure.ac?  Unfortunately he had to revert this checkin.

Error details:

+ running autoconf ...
configure.ac:57: error: possibly undefined macro: AG_GST_ARG_WITH_PACKAGE_NAME
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:58: error: possibly undefined macro: AG_GST_ARG_WITH_PACKAGE_ORIGIN
configure.ac:59: error: possibly undefined macro: AG_GST_ARG_VALGRIND
configure.ac:67: error: possibly undefined macro: AG_GST_ARCH
configure.ac:85: error: possibly undefined macro: AG_GST_DOCBOOK_CHECK
configure.ac:88: error: possibly undefined macro: AG_GST_PLUGIN_DOCS
configure.ac:113: error: possibly undefined macro: AG_GST_CHECK_GST
configure.ac:114: error: possibly undefined macro: AG_GST_CHECK_GST_BASE
configure.ac:115: error: possibly undefined macro: AG_GST_CHECK_GST_PLUGINS_BASE
configure.ac:116: error: possibly undefined macro: AG_GST_CHECK_GST_CHECK
configure.ac:138: error: possibly undefined macro: AG_GST_SET_PLUGINDIR
configure.ac:141: error: possibly undefined macro: AG_GST_SET_ERROR_CFLAGS
configure.ac:144: error: possibly undefined macro: AG_GST_SET_LEVEL_DEFAULT
configure.ac:203: error: possibly undefined macro: AG_GST_CHECK_LIBHEADER

autoconf failed
*** error during stage configure of gst-ffmpeg: ########## Error running ./autogen.sh --prefix /opt/yobuild --libdir '${exec_prefix}/lib' --disable-static --disable-gtk-doc  *** [7/7]
Comment 1 Sebastian Dröge (slomo) 2008-12-06 08:20:17 UTC
You simply can't run autoreconf / autogen.sh from the 0.10.6 tarball unfortunately unless you remove m4 from the acinclude path and add common/m4.

Try changing this in your autogen.sh ( -I common/m4 should be there), also why do you need to run autogen.sh at all? Everything you need for building is inside the tarball ;)
Comment 2 Sebastian Dröge (slomo) 2008-12-06 18:45:42 UTC
Btw, as this is fixed in CVS I'll close this bug as obsolete
Comment 3 Ben Denckla 2008-12-06 21:34:43 UTC
I think we are having some miscommunication.  This bug is not about building from the tarball.  It is about building from CVS tag RELEASE-0_10_6.
Comment 4 Sebastian Dröge (slomo) 2008-12-07 18:55:36 UTC
Ah ok, well the tag seems to be broken as it doesn't include the common directory. Let's reopen the bug :)
Comment 5 Edward Hervey 2008-12-11 14:19:06 UTC
Ben, do you still get this issue with current gst-ffmpeg trunk ? There's nothing we can do about fixing past releases/tags (unless you invent a time machine).
Comment 6 Ben Denckla 2008-12-11 15:56:03 UTC
This issue is not present for me with trunk HEAD. But,  I need to grab something other than HEAD to get reproducible results.  I prefer to grab from a release tag but I imagine CVS has a way to grab from a specific, untagged (or numerically tagged) point in time so I could do that, too.

So, I see that the bug as I stated it, a problem with what is in RELEASE-0_10_6, cannot be fixed without moving the tag (which I understand would be a bad idea).

So maybe the bug is better stated as "no recent release builds successfully," in which case it can only be fixed with a new release (and accompanying tag).

I understand if you're not ready to make a new release, especially not just to fix this bug.

In that case I guess the bug could be resolved as OBSOLETE or left open until verified to be fixed with the next release (RELEASE-0_10_7 probably, unless the next release is a big one (i.e. not just a point release)).
Comment 7 Edward Hervey 2008-12-11 16:49:10 UTC
oh man... I finally realized what your problem is. It's even stupider that you thought.

when you check out gst-ffmpeg with a specific tag, it will also checkout common/ with that same tag ....

The problem is that the tags in common/ are seriously screwed up.

The easiest is to go in common, and checkout the revision from the gst-ffmpeg release date (In this case 27th Nov 2008):
> cd common/
> cvs up -dP -D2008-11-27
> cd ..
> ./autogen.sh .....