#9738: vala-0.38.0 will not build without graphviz
--------------------+-----------------------
 Reporter:  renodr  |       Owner:  bdubbs@…
     Type:  defect  |      Status:  assigned
 Priority:  normal  |   Milestone:  8.2
Component:  BOOK    |     Version:  SVN
 Severity:  normal  |  Resolution:
 Keywords:          |
--------------------+-----------------------

Comment (by pierre.labastie):

 Replying to [comment:6 bdubbs@…]:
 > Replying to [comment:5 pierre.labastie]:
 > > Well, there is a circular dependency at the recommended level: graphiz
 recommends librsvg which recommends vala. But graphviz can be built
 without any of its recommended deps, and vala then builds OK. Maybe this
 information could be added to the vala page.
 >
 > As an experiment, I was able to build graphviz on a pristine LFS
 (chrrot) build.  I had to add --enable-swig=no but it did build.

 I'm curious why this should be required: we do not have this in the
 instructions, and swig is said to be optional...

 >
 > The problem is, why should a user have to do that if the only thing that
 is needed is vala and if valadoc, Vala Documentation Tool, is not needed
 or wanted by the user?
 >
 > Depending on the build order and user needs, it may require the user to
 build graphviz twice.  I think this is something we need to avoid if
 possible.

 Building graphviz without any dependency takes about 2 minutes on a modern
 computer... Maintaining a patch to remove valadoc will add editing work
 for each release of vala (which is often!). Upstream has made a bad move,
 I agree, but if we were to fix all upstream bad decisions, we would have
 thousands of patches... In this case, we can live with it, and we just
 need to explain how to proceed, as we do for the freetype<->harfbuzz
 circular dep.

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/9738#comment:9>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to