Bug 170494 - missing buildrequirement for javadoc generator
Summary: missing buildrequirement for javadoc generator
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: cairo-java
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-12 12:11 UTC by Karsten Hopp
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-05 20:47:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Karsten Hopp 2005-10-12 12:11:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b3) Gecko/20050827 Fedora/1.1-0.2.8.deerpark.alpha2 Firefox/1.0+

Description of problem:
cairo-java cannot be built if there's no javadoc generator present:
checking for javadoc... no
configure: error: no acceptable javadoc generator found in $PATH
error: Bad exit status from /var/tmp/rpm-tmp.61871 (%build)

Version-Release number of selected component (if applicable):
cairo-java-1.0.0-9

How reproducible:
Always

Steps to Reproduce:
1.try to build without having a javadoc generator
2.
3.
  

Additional info:

Comment 1 Igor Foox 2005-10-12 13:12:55 UTC
Thanks for reporting this. Did you manage to build any of the other java-gnome
packages with a javadoc generator? Specifically cairo-java requires glib-java,
were you able to build that? (I'm assuming no, since it seems that all the
java-gnome packages are missing this build requirement a.t.m.).

Comment 2 Karsten Hopp 2006-05-02 13:12:32 UTC
Well, it looks like all those java-gnome packages need proper build requirements.
Did you actually remove the javadoc generator from your system and have you tried
to build the cairo-java without it ?
That bug still exists in the current -development tree and will need to be fixed
when we switch to the new brew buildsystem in June/July as that one is supposed
to fail the build when the buildrequirements are incomplete.

Comment 3 Stepan Kasal 2007-11-05 20:47:59 UTC
I believe the build requires are correct in the current version.


Note You need to log in before you can comment on or make changes to this bug.