headers
Kunnar Klauks | 15 Apr 2004 22:03
Picon

Unable to create font set.

Hi

I downloaded and compiled current xboard from CVS. When starting xboard,
im getting "Unable to create font set" error. I have in my .Xresources
file:

xboard*font: -microsoft-tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-15

if i remove my .Xresources, then xboard starts ok. I looked into
xboard.c, something is wrong in ENABLE_NLS block but im not sure what
exactly.

--

-- 
Kunnar Klauks <kk001a <at> hot.ee>
Permalink | Reply | 1 comment |
headers
A. Alper Atici | 15 Apr 2004 12:06
Picon

Re: Unable to create font set.


On Thu, Apr 15, 2004 at 11:03:12PM +0300, Kunnar Klauks wrote:
> Hi
> 
> I downloaded and compiled current xboard from CVS. When starting xboard,
> im getting "Unable to create font set" error. I have in my .Xresources
> file:
> 
> xboard*font: -microsoft-tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-15
> 
> if i remove my .Xresources, then xboard starts ok. I looked into
> xboard.c, something is wrong in ENABLE_NLS block but im not sure what
> exactly.
> 

If you don't need NLS support, then configure with --disable-nls

If you want NLS support, then make sure you don't have a broken locale 
implementation, have gettext-runtime functionality, have fonts related to 
your locale settings installed and/or set your locale accordingly.
Permalink | Reply | 0 comments |
headers
Daniel Mehrmann | 20 Apr 2004 05:20
Picon
Picon

Compiling cvs winboard with MSVC

Hello,

i heard from a lot of people they have problems to compile the current 
cvs winboard version with Microsoft Visual Studio. 

They got the follow error message: (sorry german version, but the vars
should be the same)

cl -c -W3 -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -D_WINNT
-D_WIN32_WINNT=0x0400 -D_WIN32_IE=0x0300 -DWINVER=0x0400 -DWIN32
-D_WIN32 -I. -I.. -DWINVER=0x0400 -Z7 -Od ../backend.c
backend.c
../backend.c(9255) : error C2520: Konvertierung von unsigned __int64 in
double nicht implementiert, verwenden Sie signed __int64

The problem is so far that Microsoft goes their own special way for
unsigend/sigend 64bit types. 
Of course we have the problem too, that we haven't yet a ANSI C standard
for 64bit.

So the workaround for that problem is to install the free public
"Processor Pack" AddOn for Visual Studio from Microsoft. 

Here is a download link:
http://msdn.microsoft.com/vstudio/downloads/tools/ppack/download.aspx

--
Daniel Mehrmann
Attachment (smime.p7s): application/x-pkcs7-signature, 3082 bytes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Mehrmann | 25 Apr 2004 06:17
Picon
Picon

Basic fix: FW: Compiling cvs winboard with MSVC

Hello again with the same problem,

i determined that my suggestion don't work with newer microsoft visual
studio's after 6.0 SP5.
The new servicepack 6 for msvc 6.0 disable the processorpack too.

So i wrote a little basic code to fix the problem for ever. 
And now we used this code for all compilers because i think it's a good
idea to have the same basics :)
I don't like to much special compiler code too.

I will checkin in the next hours this:

--- xboard/backend.h	2004-02-15 03:29:36.000000000 +0100
+++ xboard.ready/backend.h	2004-04-25 06:00:03.296875000 +0200
 <at>  <at>  -178,15 +178,17  <at>  <at> 

 /* unsigned int 64 for engine nodes work and display */
 #ifdef WIN32
-	/* I don't know the name for this type of other compilers 
-	 * If it not work just added here 
-	 * Thats for MS Visual Studio 
+	/* I don't know the name for this type of other compilers
+	 * If it not work just added here
+	 * Thats for MS Visual Studio
 	 */
-	#define u64	unsigned __int64
+	#define u64 unsigned __int64
+	#define s64 signed __int64
 	#define u64Display  "%I64u"
(Continue reading)

Permalink | Reply | 0 comments |

Gmane