Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 212584 - media-sound/moc-2.5.0_alpha3-r1 configure fails
Summary: media-sound/moc-2.5.0_alpha3-r1 configure fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Sound Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-07 13:37 UTC by Czeryna Karol
Modified: 2008-03-10 08:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Czeryna Karol 2008-03-07 13:37:44 UTC 
Hi! i cant compile media-sound/moc-2.5.0_alpha3-r1 i have this error:
***** autoconf *****

configure.in:20: error: possibly undefined macro: AC_SUBST
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:375: error: possibly undefined macro: AM_PATH_LIBFLAC

on gcc42 and gcc43

Reproducible: Always
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2008-03-08 12:24:42 UTC 
It's the patch and eautoreconf in -r1 that breaks it for you since there is no m4 file macro from libFLAC available.

Hendrik, can you provide us a patch that patches configure directly, so we can avoid running eauto(re)conf here?
Comment 2 Alexis Ballier gentoo-dev 2008-03-08 12:28:43 UTC 
(In reply to comment #1)
> It's the patch and eautoreconf in -r1 that breaks it for you since there is no
> m4 file macro from libFLAC available.
> 
> Hendrik, can you provide us a patch that patches configure directly, so we can
> avoid running eauto(re)conf here?

I'd prefer going the way of shipping libFLAC.m4 in a separate tarball :)
(and poke upstream about it missing)
Comment 3 Alexis Ballier gentoo-dev 2008-03-09 14:36:36 UTC 
fixed
Comment 4 Hendrik Iben 2008-03-10 08:41:17 UTC 
It is nice to see that it has been fixed. I never had any problems with autoreconfed moc builds. What exactly caused the problem ? I would like to report this upstream.