[Bug 187923] [patch] graphics/zbar fails with V4L enabled

bz-noreply at freebsd.org bz-noreply at freebsd.org
Tue Jun 10 14:49:11 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187923

Josh C <josh.cepek at usa.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |josh.cepek at usa.net

--- Comment #5 from Josh C <josh.cepek at usa.net> ---
Created attachment 143624
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143624&action=edit
Fix CPP include path

This issue impacts more than just V4L for zbar; under FreeBSD 10.0, the port
fails to build since libjpeg cannot be found as the local include dir (normally
/usr/local/include) is not passed to CPPFLAGS.

This results in the following build failure when the libjpeg.h header can't be
found:

/bin/sh ./libtool --tag=CC   --mode=compile cc -DHAVE_CONFIG_H -I. -I./include 
-I./zbar -I./include   -DLIBICONV_PLUG -Wall -Wno-parentheses -O2 -pipe
-DLIBICONV_PLUG -fno-strict-aliasing -MT zbar/zbar_libzbar_la-jpeg.lo -MD -MP
-MF zbar/.deps/zbar_libzbar_la-jpeg.Tpo -c -o zbar/zbar_libzbar_la-jpeg.lo
`test -f 'zbar/jpeg.c' || echo './'`zbar/jpeg.c
libtool: compile:  cc -DHAVE_CONFIG_H -I. -I./include -I./zbar -I./include
-DLIBICONV_PLUG -Wall -Wno-parentheses -O2 -pipe -DLIBICONV_PLUG
-fno-strict-aliasing -MT zbar/zbar_libzbar_la-jpeg.lo -MD -MP -MF
zbar/.deps/zbar_libzbar_la-jpeg.Tpo -c zbar/jpeg.c  -fPIC -DPIC -o
zbar/.libs/zbar_libzbar_la-jpeg.o
zbar/jpeg.c:25:10: fatal error: 'jpeglib.h' file not found
#include <jpeglib.h>
         ^
1 error generated.

The new zbar-cpp-includes.patch alters the logic of the earlier patch by moving
the CPPFLAGS definition to the body of the Makefile. There's no reason to
conditionally add this as the configure arg --with-jpeg=yes is always set.

With this patch applied, the build completes normally for me, and should also
resolve the V4L build issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list