bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Mingw32 cross-compilation


From: Christian Anthon
Subject: Re: [Bug-gnubg] Mingw32 cross-compilation
Date: Tue, 12 Jan 2010 10:59:49 +0100

On Tue, Jan 12, 2010 at 9:28 AM, Vyacheslav V. Yurkov
<address@hidden> wrote:
> Christian Anthon wrote:

> external_l.o:external_l.c:(.text+0x258): undefined reference to `_extlval'
> external_l.o:external_l.c:(.text+0x33f): undefined reference to `_extlval'
> external_l.o:external_l.c:(.text+0x368): undefined reference to `_extlval'
> external_l.o:external_l.c:(.text+0x3a9): undefined reference to `_extlval'
> external_l.o:external_l.c:(.text+0x186b): undefined reference to `_extparse'

Don't know why this would happen, but these are defined in
external_y.c. You may try to remove HAVE_SOCKETS config.h and then
remove the references to external_l/external_y in the makefile.am. But
remember that config.h gets clobbered next time you run configure.
Edit configure.in to get rid of HAVE_SOCKETS forever.

> gnubg.o:gnubg.c:(.text+0x7b6d): undefined reference to `_CreateMutex'

You can probably just comment out the line in gnubg.c where it says CreateMutex

> collect2: ld returned 1 exit status
> make[2]: *** [gnubg.exe] Error 1
> make[2]: Leaving directory `/home/uvv/C/GTK+/gnubg'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/uvv/C/GTK+/gnubg'
> make: *** [all] Error 2
>
> I thought it should deal somehow with previous bison/lex errors.
> P.S. You can notice -UDATADIR parameter. It's one more workaround, since
> w32api package already has this macro defined.
>
> --
> Vyacheslav V. Yurkov <address@hidden>       Senior Software Engineer
> Norilsk                                         Tel: +79069001870
>
> Software Development Department
> Joint Stock Company "Channel-7", ISP
>
>
>
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]