I'm just tesitng fb/agg build again, so I can also really confirm
that the segfault is gone, and I confirm that the compatibility
layer need detection is working here:
AGG flags are: -I/extra/agg-2.4/include/agg2
AGG libs are: -L/extra/agg-2.4/lib -lagg
needs compatibility layer: no
--strk;
On Wed, Oct 18, 2006 at 05:25:20PM +0200, strk wrote:
> On Wed, Oct 18, 2006 at 05:21:53PM +0200, Udo Giacomozzi wrote:
> > configure still activates the AGG compatibility layer, even if I use
> > the source version of AGG 2.4 which does not need it.
> >
> > AGG flags are: -I/home/udo/agg-2.4/include
> > AGG libs are: -L/home/udo/agg-2.4/src -lagg
> > needs compatibility layer: yes
> >
> > How can this be avoided?
>
> The compatibility layer is activated by this rule:
>
> AC_EGREP_HEADER(render_scanlines_compound_layered,
> ${agg_include_dir}/agg_renderer_scanline.h,
> ...
>
> So, what's the value of ${agg_include_dir} for you ?
> Does agg_renderer_scanline.h really contains the
> 'render_scanlines_compound_layered' string ?
> Look in macros/agg.m4 to add some debugging output
> (echo ${agg_include_dir})
>
> --strk;
>
>
> _______________________________________________
> Gnash-dev mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/gnash-dev
--
/"\ ASCII Ribbon Campaign
\ / Respect for low technology.
X Keep e-mail messages readable by any computer system.
/ \ Keep it ASCII.
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
