Inkscape failed to buil on FreeBSD - BSD

This is a discussion on Inkscape failed to buil on FreeBSD - BSD ; I tried to build inkscape from the port but it failded. Below is what I got: I tried the suggestion of the error message but it doesn't work. How to work around this problem? ===> Vulnerability check disabled, database not ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Inkscape failed to buil on FreeBSD

  1. Inkscape failed to buil on FreeBSD

    I tried to build inkscape from the port but it failded.
    Below is what I got:
    I tried the suggestion of the error message but it doesn't work. How
    to work around this problem?

    ===> Vulnerability check disabled, database not found
    ===> Extracting for inkscape-0.45_3
    => MD5 Checksum OK for inkscape-0.45.tar.gz.
    => SHA256 Checksum OK for inkscape-0.45.tar.gz.
    ===> Patching for inkscape-0.45_3
    ===> Applying FreeBSD patches for inkscape-0.45_3
    ===> inkscape-0.45_3 depends on executable in : gmake - found
    ===> inkscape-0.45_3 depends on file: /usr/local/bin/intltool-extract - found
    ===> inkscape-0.45_3 depends on file: /usr/local/libdata/pkgconfig/gnome-mime-data-2.0.pc - found
    ===> inkscape-0.45_3 depends on executable in : pkg-config - found
    ===> inkscape-0.45_3 depends on executable in : update-desktop-database - found
    ===> inkscape-0.45_3 depends on shared library: popt.0 - found
    ===> inkscape-0.45_3 depends on shared library: gtkmm-2.4.1 - found
    ===> inkscape-0.45_3 depends on shared library: gc.1 - found
    ===> inkscape-0.45_3 depends on shared library: gtkspell.0 - found
    ===> inkscape-0.45_3 depends on shared library: lcms.1 - found
    ===> inkscape-0.45_3 depends on shared library: intl - found
    ===> inkscape-0.45_3 depends on shared library: atk-1.0.0 - found
    ===> inkscape-0.45_3 depends on shared library: gconf-2.4 - found
    ===> inkscape-0.45_3 depends on shared library: glib-2.0.0 - found
    ===> inkscape-0.45_3 depends on shared library: gnomevfs-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: gtk-x11-2.0.0 - found
    ===> inkscape-0.45_3 depends on shared library: art_lgpl_2.5 - found
    ===> inkscape-0.45_3 depends on shared library: bonobo-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: glade-2.0.0 - found
    ===> inkscape-0.45_3 depends on shared library: gnomecanvas-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: gnomeprint-2-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: gnomeprintui-2-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: IDL-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: xml2.5 - found
    ===> inkscape-0.45_3 depends on shared library: xslt.2 - found
    ===> inkscape-0.45_3 depends on shared library: linc.1 - found
    ===> inkscape-0.45_3 depends on shared library: ORBit-2.0 - found
    ===> inkscape-0.45_3 depends on shared library: pango-1.0.0 - found
    ===> Configuring for inkscape-0.45_3
    checking build system type... i386-portbld-freebsd6.2
    checking host system type... i386-portbld-freebsd6.2
    checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether gmake sets $(MAKE)... yes
    checking for intltool >= 0.22... 0.35.0 found
    checking for perl... /usr/bin/perl
    checking for XML::Parser... ok
    checking for iconv... /usr/local/bin/iconv
    checking for msgfmt... /usr/local/bin/msgfmt
    checking for msgmerge... /usr/local/bin/msgmerge
    checking for xgettext... /usr/local/bin/xgettext
    checking for gcc... cc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether cc accepts -g... yes
    checking for cc option to accept ISO C89... none needed
    checking for style of include used by gmake... GNU
    checking dependency style of cc... gcc3
    checking whether cc understands -c and -o together... yes
    checking whether we are using the GNU C++ compiler... yes
    checking whether c++ accepts -g... yes
    checking dependency style of c++... gcc3
    checking for strerror in -lcposix... no
    checking whether we are using the GNU C++ compiler... (cached) yes
    checking whether c++ accepts -g... (cached) yes
    checking dependency style of c++... (cached) gcc3
    checking for cc option to accept ANSI C... no
    checking how to run the C++ preprocessor... c++ -E
    checking for grep that handles long lines and -e... /usr/bin/grep
    checking for egrep... /usr/bin/grep -E
    checking for ANSI C header files... yes
    checking for ranlib... ranlib
    checking GNU compiler version... 3.4.6
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking locale.h usability... yes
    checking locale.h presence... yes
    checking for locale.h... yes
    checking for LC_MESSAGES... yes
    checking libintl.h usability... yes
    checking libintl.h presence... yes
    checking for libintl.h... yes
    checking for ngettext in libc... no
    checking for bindtextdomain in -lintl... yes
    checking for ngettext in -lintl... yes
    checking for dgettext in -lintl... yes
    checking for bind_textdomain_codeset... yes
    checking for msgfmt... /usr/local/bin/msgfmt
    checking for dcgettext... yes
    checking for gmsgfmt... /usr/local/bin/msgfmt
    checking for xgettext... /usr/local/bin/xgettext
    checking for catalogs to be installed... am az be bg ca cs da de dz el en_GB en_CA en_US@piglatin eo es es_MX et fi fr ga gl hr hu it ja ko lt mk mn nb ne nl nn pa pl pt pt_BR ru rw sk sl sq sr sr@Latn sv th tr uk vi zh_CN zh_TW
    checking for pkg-config... /usr/local/bin/pkg-config
    checking for png_read_info in -lpng... yes
    checking png.h usability... yes
    checking png.h presence... yes
    checking for png.h... yes
    checking for shl_load in -ldld... no
    checking for dlopen... yes
    checking gc.h usability... yes
    checking gc.h presence... yes
    checking for gc.h... yes
    checking for GC_init in -lgc... yes
    checking libgc version 6.4+... Segmentation fault (core dumped)
    no
    configure: error: libgc (the Boehm Conservative Collector) 6.4+, is needed to compile inkscape -- http://www.hpl.hp.com/personal/Hans_Boehm/gc
    ===> Script "configure" failed unexpectedly.
    Please run the gnomelogalyzer, available from
    "http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
    problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
    solve the problem, report the build failure to the FreeBSD GNOME team at
    gnome@FreeBSD.org, and attach (a)
    "/usr/ports/graphics/inkscape/work/inkscape-0.45/config.log", (b) the output
    of the failed make command, and (c) the gnomelogalyzer output. Also, it might
    be a good idea to provide an overview of all packages installed on your system
    (i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
    copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with
    the attachment. Try to avoid sending any attachments to the mailing list
    (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are
    usually discarded by the mailing list software.
    *** Error code 1

    Stop in /usr/ports/graphics/inkscape.

  2. Re: Inkscape failed to buil on FreeBSD

    Begin <867isw875e.fsf@zhouyan.local.domain>
    On 2007-04-01, Matthew Zhou wrote:
    > I tried to build inkscape from the port but it failded.
    > Below is what I got:
    > I tried the suggestion of the error message but it doesn't work. How
    > to work around this problem?

    [massive snip]

    From what you posted, I learned that the maintainers have provided
    a tool to diagnose and perhaps help you solve the problem. All you
    can say is ``it doesn't work''. Nobody can help you if that really is
    all information you can provide. Further, there are several fallbacks
    provided, and you apparently couldn't followup with those either.

    What is it, exactly, that you expect random strangers who have no access
    to your computer to divine and tell you, if you cannot deal with the
    instructions given already, and you cannot explain just what the trouble
    was that you ran into?


    --
    j p d (at) d s b (dot) t u d e l f t (dot) n l .
    This message was originally posted on Usenet in plain text.
    Any other representation, additions, or changes do not have my
    consent and may be a violation of international copyright law.

+ Reply to Thread