On Mar 14 10:13, Corinna Vinschen wrote:
> Sorry, but I'm really confused about the unnecessary complexity. I don't
> want to "stage" anything. I would like to be able call
>
> configure --prefix=...
> make
> make install
>
> That's a pretty standard scenario. But here's what happens: Try to
> build a full set of headers and libs for a Cygwin target:
>
> ${srcdir}/configure \
> --host=x86_64-w64-mingw32 \
> --prefix=/home/corinna/mingw \
That should have been --prefix=/home/corinna/mingw64 to match the below
error message. Sorry.
> --enable-w32api
>
> As common as it looks, the build will fail:
>
> x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H \
> -I. \
> -I${srcdir}/mingw-w64-crt \
> -m32 \
> -I/home/corinna/mingw64/include \
> [...] -g -O2 [...] \
> -c -o libsrc/lib32_libwmcodecdspuuid_a-wmcodecdspuuid.o \
> [...]/wmcodecdspuuid.c
> ${srcdir}/mingw-w64-crt/libsrc/wmcodecdspuuid.c:8:24: fatal error:
> wmcodecdsp.h: No such file or directory
> compilation terminated.
>
> The reason is obvious. The -I don't include the headers within the
> same src tree, and they don't contain the generated headers within
> the same build tree *even though thay are available*.
>
> It simply doesn't make sense to require having a copy of these headers
> installed to some arbitrary sysroot dir, just to be able to build crt.
Corinna
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
