Best Way to Fix a links Browser Compilation Problem

From: Martin McCormick (martin_at_dc.cis.okstate.edu)
Date: 11/05/03

  • Next message: Chris Pressey: "Re: Best Way to Fix a links Browser Compilation Problem" 
    To: freebsd-questions@freebsd.org
Date: Wed, 05 Nov 2003 13:48:31 -0600

            I am attempting to install a newer version of the "links" text
    browser. The Makefile tells you to
    define WITHOUT_X11 if you are not using X so I modified the Makefile
    to define that parameter as follows:
    CONFIGURE_ARGS+= --enable-javascript --with-ssl --without-svgalib --WITHOUT_X11

            Actually, that line may wrap when you read this message, but
    all those defines are on one line and the WITHOUT_X11 is simply tacked
    on to the end.

            Anyway, if I do a make build, the make abends with:

    mv -f .libs/fcdir.lo fcdir.lo
    /bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/c
    rm -f .libs/fcfreetype.lo
    cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/freetype2 -I/usr/local/inco
    fcfreetype.c: In function `FcFreeTypeQuery':
    fcfreetype.c:279: syntax error before `psfontinfo'
    fcfreetype.c:738: `psfontinfo' undeclared (first use in this function)
    fcfreetype.c:738: (Each undeclared identifier is reported only once
    fcfreetype.c:738: for each function it appears in.)
    gmake[2]: *** [fcfreetype.lo] Error 1
    gmake[2]: Leaving directory `/usr/ports/x11-fonts/fontconfig/work/fontconfig-2.'
    gmake[1]: *** [all-recursive] Error 1
    gmake[1]: Leaving directory `/usr/ports/x11-fonts/fontconfig/work/fontconfig-2.'
    gmake: *** [all-recursive-am] Error 2
    *** Error code 2

    Stop in /usr/ports/x11-fonts/fontconfig.
    *** Error code 1

    Stop in /usr/ports/x11/XFree86-4-libraries.
    *** Error code 1

    Stop in /usr/ports/www/links.

            The problem seems to be buried in all those X libraries links
    uses. Either that or I defined that WITHOUT_X11 variable in the wrong
    way.

            What is the safest way to correct a problem like this?

            In my experience, the port installation process is very good
    at figuring out what it needs to do to get a package to build but
    obviously, I have the wrong version of something or there is something
    wrong with the WITHOUT_X11 directive.

            This system does not have X windows on it, but it has several
    XFree86 libraries due to software such as expect that needs several X
    libraries.

            Many thanks for any help.

    Martin McCormick WB5AGZ Stillwater, OK
    OSU Information Technology Division Network Operations Group
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

  • Next message: Chris Pressey: "Re: Best Way to Fix a links Browser Compilation Problem"

    Relevant Pages

    • Re: 6.1_RELEASE Install Problem
      ... let's assume for now that something was wrong with the makefile or there was a glitch in the make/install process. ... *** Error code 64 ... It does not look like a directory problem or a permissions problem. ...
      (freebsd-questions)
    • Re: p5-libapreq2 port fails to build
      ... Writing Makefile for libapreq2 ... *** Error code 2 ... skv@ doesn't really like perl too much so he split this out so just the ...
      (freebsd-questions)
    • Re: problems building fusefs-kmod
      ... objcopy --strip-debug fuse.ko ... I wonder why SRC_BASE is set in port's Makefile and not used at all. ... incomplete type mount_fusefs.c: In function 'usage': ... type *** Error code 1 ...
      (freebsd-questions)
    • Re: how to solve the problem to install R?
      ... *** Error code 1 ... examined the port's Makefile for the BROKEN variable ... again remove the configuration and re-enter ... related to some info, texinfo, teTex or other dependency for the ...
      (freebsd-questions)
    • Buildworld breaks at libpcap
      ... buildworld breaks very eloquently at libpcap. ... Error message looks like: ... (Each undeclared identifier is reported only once ... *** Error code 1 ...
      (freebsd-current)