[geos-devel] MinGW build of Geos on Win7

[Theuns Heydenrych]

It looks like the input is coming from libtool.m4, but i have no idea how
to debug this.
I might stare at the problem and not even know it.

Is there a way of listing the internal library paths of the compiler or the
linker?
Because it looks like if during configuration it asks somehow for the
internal paths and test that.

On Tue, Nov 4, 2014 at 12:18 PM, Sandro Santilli <strk at keybit.net> wrote:

> On Tue, Nov 04, 2014 at 12:10:32PM +0200, Theuns Heydenrych wrote:
> > Thanks Sandro
> > I did run the commands you suggested and yes,
> > "prerequisites/i686-w64-mingw32-static"
> > appear in the output.
> > It also appear with the extra ' in the output, like
> prerequisites/i686-w64-
> > mingw32-static/lib'
> >
> > How do i fix this?
> >
> > Here is the grep result.
> > $ grep prerequisites/i686-w64-mingw32-static debug.log
> > + test '-L/c/mingw491/prerequisites/i686-w64-mingw32-static/lib'\''' = -L
>
> Check higher in the output, where did this value come from ?
>
>  '-L/c/mingw491/prerequisites/i686-w64-mingw32-static/lib'\'''
>
> You might need to reference the output to some .m4 input which could
> be on your system (somewhere in autoconf install dir) and would sound
> broken.
>
> --strk;
>
>   ()   Free GIS & Flash consultant/developer
>   /\   http://strk.keybit.net/services.html
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20141104/b444aa20/attachment.html>