Fail to build pidgin with gcc in windows

Daniel Atallah datallah at pidgin.im
Mon Dec 5 10:06:55 EST 2011


2011/12/4 z <zzpidgin at 163.com>:
> Hello:
>
> I fail to build pidgin with gcc in windows.
>
> Environment:
> 1. Windows 7 Home, 64 bit
> 2. The MinGW is 4.4.
>
> Below is the output what I saw in cygwin. Could you please give me any
> suggestion? Thanks in advanced.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> zhuz at zhuz-PC /cygdrive/d/project/pidgin/pidgin-2.10.0
> $ make -f Makefile.mingw
> (cd . && mtn --root=. automate get_base_revision_id) 2>/dev/null
>>package_revisi
> on_raw.txt \
>         || rm -f package_revision_raw.txt
> if [ -f package_revision_raw.txt ]; then \
>                 sed 's/^\(.\{1,\}\)$/#define REVISION "\1"/'
> package_revision_ra
> w.txt & gt; package_revision.h; \
>         fi
> [ -f package_revision.h ] || echo "#define REVISION \"unknown\"" >
> package_revis
> ion.h
> make -C ./libpurple -f Makefile.mingw
> make[1]: Entering directory
> `/cygdrive/d/project/pidgin/pidgin-2.10.0/libpurple'
>
> gcc.exe -O2 -Wall -Waggregate-return -Wcast-align
> -Wdeclaration-after-statement
> -Werror-implicit-function-declaration -Wextra -Wno-sign-compare
> -Wno-unused-para
> meter -Winit-self -Wmissing-declarations -Wmissing-prototypes
> -Wnested-externs -
> Wpointer-arith -Wundef -pipe -mno-cygwin -mms-bitfields -g -DHAVE_CYRUS_SASL
> -DH
> AVE_CONFIG_H -DWIN32_LEAN_AND_MEAN -I../libpurple -I../libpurple/win32 -I..
> -I..
> /../win32-dev/gtk_2_0-2.14/include
> -I../../win32-dev/gtk_2_0-2.14/include/glib-2
> .0 -I../../win32-dev/gtk_2_0-2.14/lib/glib-2.0/include
> -I../../win32-dev/libxml2
> -2.7.4/inclu de/libxml2 -o account.o -c account.c
> gcc: The -mno-cygwin flag has been removed; use a mingw-targeted
> cross-compiler.

You're not using gcc 4.4 - the -mno-cygwin flag was removed in 4.6;
that's why you're seeing this error.

`gcc --version` will confirm this, and `which gcc` will tell you where
it is finding gcc in your Path - it's possible you have several
versions and what is actually being used is different than what you
expect.

There are some issues compiling with gcc 4.6 (not just this flag), so
you really do need to use the version specified in the instructions.

-D



More information about the Support mailing list