Bug 99531 – libgnome-2.10.1-r1 will not compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Darren Dale 2005-07-19 07:47:08 UTC]

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.

[Comment 1 Leonardo Boshell (RETIRED) 2005-07-19 08:12:34 UTC]

*** Bug 99536 has been marked as a duplicate of this bug. ***

[Comment 2 Serkan Hosca 2005-07-19 08:46:13 UTC]

(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.

[Comment 3 ummajumma 2005-07-19 08:56:27 UTC]

(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.

[Comment 4 Leonardo Boshell (RETIRED) 2005-07-19 09:16:10 UTC]

Created attachment 63791 [details, diff]
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

[Comment 5 Leonardo Boshell (RETIRED) 2005-07-19 09:21:51 UTC]

*** Bug 99543 has been marked as a duplicate of this bug. ***

[Comment 6 Fabio Catarinella 2005-07-19 09:57:19 UTC]

Patch works for me.

[Comment 7 Leonardo Boshell (RETIRED) 2005-07-19 10:07:39 UTC]

Thanks for the feedback. The fix has been committed in CVS.

[Comment 8 Leonardo Boshell (RETIRED) 2005-07-20 00:49:35 UTC]

*** Bug 99580 has been marked as a duplicate of this bug. ***