2011/5/3 Ozkan Sezer <[email protected]>
> On Tue, May 3, 2011 at 8:14 PM, Ruben Van Boxem
> <[email protected]> wrote:
> > Using mingw-w32-1.0-bin_i686-linux_20110502.tar.bz2, and this configure
> to
> > libiconv:
> >
> >> configure --host=i686-w64-mingw32 --build=x86_64-gnu-linux
> >> --prefix=/home/ruben/Development/x86/libs --enable-shared
> >> CFLAGS='-mtune=core2 -fomit-frame-pointer -momit-leaf-frame-pointer'
> >
> > I get this in the "make" stage:
> >
> >> /bin/bash ../libtool --mode=link i686-w64-mingw32-gcc
> >>
> -L"/home/ruben/Development/cross64/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.1/"
> >> -Wl,--export-all-symbols -O2 -mtune=core2 -fomit-frame-pointer
> >> -momit-leaf-frame-pointer -fvisibility=hidden -o libiconv.la -rpath
> >> /home/ruben/Development/x86/libs/lib -version-info 7:0:5 -no-undefined
> >> iconv.lo localcharset.lo relocatable.lo iconv-exports.lo libiconv.res.lo
> >> libtool: link: i686-w64-mingw32-gcc -shared .libs/iconv.o
> >> .libs/localcharset.o .libs/relocatable.o .libs/iconv-exports.o
> >> .libs/libiconv.res.o
> >>
> -L/home/ruben/Development/cross64/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.1/
> >> -Wl,--export-all-symbols -mtune=core2 -momit-leaf-frame-pointer -o
> >> .libs/libiconv-2.dll -Wl,--enable-auto-image-base -Xlinker --out-implib
> >> -Xlinker .libs/libiconv.dll.a
> >> Creating library file:
> >> .libs/libiconv.dll.a.libs/iconv.o:iconv.c:(.text+0x1274a): undefined
> >> reference to `___chkstk'
> >> collect2: ld returned 1 exit status
> >
> > I have double-checked the used executables using "which", and they are
> the
> > ones from the autobuild. I am building under Ubuntu 11.04 x86_64. Is it
> me
> > or is it the autobuild?
> >
> > Thanks,
> >
> > Ruben
>
> This:
>
> -L"/home/ruben/Development/cross64/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.1/"
> ... looks suspicious, to say the least, because you are compiling for
> x86-windows _and_
> using i686-w64-mingw32-gcc. How did it make into the command line??
> Is your toolchain a multilib one? (even if it is, linkage against x64
> libraries must not
> go into that command line...)
>
<Slaps himself on the forehead>
OK, I fixed it in my mingw64 script, but forgot it in the 32-bit one.
Must.... centralize.... scripts....more....
I'm almost there... Multilib builds coming along slowly but surely.
>
> --
> Ozkan
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
