Re: Webalizer compiles and installs fine in 6.1, goes splat in 6.2.
On Thursday 03 April 2008 01:21:38 Lou Katz wrote: In /usr/ports/webalizer (6.2) # make === Vulnerability check disabled, database not found === Extracting for webalizer-2.1.10_13 = MD5 Checksum OK for webalizer-2.01-10-src.tar.bz2. = SHA256 Checksum OK for webalizer-2.01-10-src.tar.bz2. === Patching for webalizer-2.1.10_13 === Applying extra patch /usr/ports/www/webalizer.save/files/output.patch === Applying extra patch /usr/ports/www/webalizer.save/files/linklist.patch === Applying extra patch /usr/ports/www/webalizer.save/files/webalizer-fullrefs.patch === Applying FreeBSD patches for webalizer-2.1.10_13 === webalizer-2.1.10_13 depends on shared library: gd.4 - not found ===Verifying install for gd.4 in /usr/ports/graphics/gd === Building for gd-2.0.35,1 make LIB=gd SRCS=gd.c gd_gd.c gd_gd2.c gd_io.c gd_io_dp.c gd_io_file.c gd_io_ss.c gd_jpeg.c gd_png.c gd_ss.c gd_topal.c gd_wbmp.c gdcache.c gdfontg.c gdfontl.c gdfontmb.c gdfonts.c gdfontt.c gdft.c gdfx.c gdhelpers.c gdhelpers.h gdkanji.c gdtables.c gdxpm.c gd_security.c wbmp.c gd_gif_in.c gd_gif_out.c SHLIB_MAJOR=4 SHLIB_MINOR=0 CFLAGS=-O2 -fno-strict-aliasing -pipe -I/usr/ports/graphics/gd/work/gd-2.0.35 -I/usr/local/include/freetype2/freetype -I/usr/local/include/freetype2 -I/usr/local/include -DHAVE_LIBPNG -DHAVE_LIBJPEG -DHAVE_LIBFREETYPE -DHAVE_LIBZ -DHAVE_ERRNO_H -DHAVE_FT2BUILD_H -DHAVE_LIBFREETYPE -DHAVE_LIBJPEG -DHAVE_LIBPNG -DHAVE_LIBZ -DHAVE_STDDEF_H -DHAVE_STDINT_H -DHAVE_STDLIB_H -I/usr/local/include/X11 -I/usr/local/include -DHAVE_LIBXPM -I/usr/local/include -DHAVE_LIBFONTCONFIG -DHAVE_PTHREAD -DHAVE_ICONV -DHAVE_ICONV_H -DHAVE_ICONV_T_DEF -ECFLAGS LDADD=-L/usr/local/lib -lpng -lz -ljpeg -lfreetype -lm -L/usr/local/lib -lXpm -lX11 -pthread -L/usr/local/lib -lfontconfig -L/usr/local/lib -liconv -f /usr/share/mk/bsd.lib.mk libgd.a cc -O2 -fno-strict-aliasing -pipe -I/usr/ports/graphics/gd/work/gd-2.0.35 -I/usr/local/include/freetype2/freetype -I/usr/local/include/freetype2 -I/usr/local/include -DHAVE_LIBPNG -DHAVE_LIBJPEG -DHAVE_LIBFREETYPE -DHAVE_LIBZ -DHAVE_ERRNO_H -DHAVE_FT2BUILD_H -DHAVE_LIBFREETYPE -DHAVE_LIBJPEG -DHAVE_LIBPNG -DHAVE_LIBZ -DHAVE_STDDEF_H -DHAVE_STDINT_H -DHAVE_STDLIB_H -I/usr/local/include/X11 -I/usr/local/include -DHAVE_LIBXPM -I/usr/local/include -DHAVE_LIBFONTCONFIG -DHAVE_PTHREAD -DHAVE_ICONV -DHAVE_ICONV_H -DHAVE_ICONV_T_DEF -c gdft.c gdft.c:1403:35: fontconfig/fontconfig.h: No such file or directory gdft.c:1466: error: Install x11-fonts/fontconfig or set WITHOUT_X11 cause you don't need XPM support in GD anyway. And be sure to read: less -p20070519 /usr/ports/UPDATING -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Webalizer compiles and installs fine in 6.1, goes splat in 6.2.
On Thu, Apr 03, 2008 at 12:11:52PM +0200, Mel wrote: On Thursday 03 April 2008 01:21:38 Lou Katz wrote: In /usr/ports/webalizer (6.2) # make snip -DHAVE_ICONV_H -DHAVE_ICONV_T_DEF -c gdft.c gdft.c:1403:35: fontconfig/fontconfig.h: No such file or directory gdft.c:1466: error: Install x11-fonts/fontconfig or set WITHOUT_X11 cause you don't need XPM support in GD anyway. And be sure to read: less -p20070519 /usr/ports/UPDATING -- Mel Thank you! Problem solved. The 'funny thing' was: a. This system is not an upgrade. It was a fresh install of 6.2. b. When I did the initial make on webalizer, I foolishly checked the X11 boxes in the config screen. c. However, the make mechanism apparently didn't properly pick up the dependency like it usually does. d. When I got the errors, I tried to re-do the config, and just could not find any way at all to unring that bell. Make config did not work, as config was not a target. I even make a clean, empty ports tree and tried to make webalizer there hoping for another shot at the config screen, but it never appeared, and I got the same error. This leads to the question of where in the maze of twisty little passageways, all the same, did the make mechanism hide the X11 requirement -- -=[L]=- Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
