On Fri, 28 Jan 2011, William Bulley wrote:
So something is clearly wrong here. The /var/db/ports/poppler/OPTIONS
file had:
WITHOUT_CAIRO=yes
inside, so I changed that to WITH_CAIRO=yes and repeated the above steps.
The file /usr/local/libdata/pkgconfig/poppler-cairo.pc is now there!
The
According to Warren Block on Thu, 01/27/11 at 16:41:
> >
> >Which is the correct port to install this "poppler-cairo" file?
>
> poppler-0.14.5
>
> Be sure to clean it before rebuilding and installing.
Thanks for the reply.
I did a "make deinstall" in /usr/ports/graphics/poppler and it claimed
On Thu, 27 Jan 2011, William Bulley wrote:
According to David Demelier on Thu, 01/27/11 at
11:39:
It seems that gmake does not call `pkg-config --libs --cflags poppler`.
do you have pkg-config and poppler installed correctly?
/usr/local/libdata/pkgconfig/poppler-cairo.pc
/usr/local/libdata/
According to Chris Brennan on Thu, 01/27/11 at 12:03:
>
> gmake is GNU Make, some applications don't talk nice w/ bsdmake ('make' on
> your bsd system). If your installing GIMP from ports then you should be
> correctly using something like 'make install clean'. The only time I've
> invoked gmake w
On Thu, Jan 27, 2011 at 11:55 AM, William Bulley wrote:
> You mention gmake, yet I use "# make install" all the time. Is this
> really gmake under the covers? I see both executables and they differ:
>
>
gmake is GNU Make, some applications don't talk nice w/ bsdmake ('make' on
your bsd system).
According to David Demelier on Thu, 01/27/11 at
11:39:
>
> It seems that gmake does not call `pkg-config --libs --cflags poppler`.
> do you have pkg-config and poppler installed correctly?
>
> /usr/local/libdata/pkgconfig/poppler-cairo.pc
> /usr/local/libdata/pkgconfig/poppler-cpp.pc
> /usr/lo
On 27/01/2011 17:22, William Bulley wrote:
According to Lowell Gilbert on Thu,
01/27/11 at 11:04:
William Bulley writes:
Everything up to this point builds okay. Then this happens:
Making all in common
gmake[3]: Entering directory
`/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/c
According to Lowell Gilbert on Thu,
01/27/11 at 11:04:
> William Bulley writes:
>
> > Everything up to this point builds okay. Then this happens:
> >
> > Making all in common
> > gmake[3]: Entering directory
> > `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common'
> > cc -DHAVE_CON
William Bulley writes:
> Everything up to this point builds okay. Then this happens:
>
> Making all in common
> gmake[3]: Entering directory
> `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common'
> cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT
> -I/usr/local/inc
Everything up to this point builds okay. Then this happens:
Making all in common
gmake[3]: Entering directory
`/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common'
cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT
-I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/
10 matches
Mail list logo