Bug 99531 - libgnome-2.10.1-r1 will not compile
|
Bug#:
99531
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: gnome@gentoo.org
|
Reported By: dsdale24@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: libgnome-2.10.1-r1 will not compile
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-07-19 07:47 0000
|
Here is the relevent error message:
checking for SOUND_TEST... checking for LIBGNOME... ./configure: line 24116:
syntax error near unexpected token `1.0'
./configure: line 24116: `GTK_DOC_CHECK(1.0)'
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
*** Bug 99536 has been marked as a duplicate of this bug. ***
(In reply to comment #0)
> Here is the relevent error message:
>
> checking for SOUND_TEST... checking for LIBGNOME... ./configure: line 24116:
> syntax error near unexpected token `1.0'
> ./configure: line 24116: `GTK_DOC_CHECK(1.0)'
>
> Reproducible: Always
> Steps to Reproduce:
> 1.
> 2.
> 3.
emerge gtk-doc fixes the problem for me.
(In reply to comment #2)
> (In reply to comment #0)
> > Here is the relevent error message:
> >
> > checking for SOUND_TEST... checking for LIBGNOME... ./configure: line 24116:
> > syntax error near unexpected token `1.0'
> > ./configure: line 24116: `GTK_DOC_CHECK(1.0)'
> >
> > Reproducible: Always
> > Steps to Reproduce:
> > 1.
> > 2.
> > 3.
>
> emerge gtk-doc fixes the problem for me.
>
Fixed it here too.
Created an attachment (id=63791) [details]
libgnome_ebuild.patch
Installing gtk-doc can be used as a work-around, but it's not a reasonable
solution for people who want to enforce the USE="-doc" setting.
Please, in order to debug this, uninstall gtk-doc, and apply this small patch
against libgnome-2.10.1-r1.ebuild in your system.
Then try to emerge libgnome again and let us know how it goes. Thanks
*** Bug 99543 has been marked as a duplicate of this bug. ***
Thanks for the feedback. The fix has been committed in CVS.
*** Bug 99580 has been marked as a duplicate of this bug. ***