Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Thx Christian, that's what gdb reports when I try to start gnubg: "Starting program: /usr/local/bin/gnubg [Thread debugging using libthread_db enabled] GNU Backgammon 0.90.0 Copyright (C) 2008 by the AUTHORS; for details type `show version'. This program comes with ABSOLUTELY NO WARRANTY; for details type `show warranty'. This is free software, and you are welcome to redistribute it under certain conditions; type `show copying' for details. [New Thread 0x7fffe9fa5950 (LWP 17936)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe9fa5950 (LWP 17936)] 0x004915f9 in MT_WorkerThreadFunction (id=0x4ba87b0) at multithread.c:336 336 multithread.c: No such file or directory. in multithread.c (gdb) bt #0 0x004915f9 in MT_WorkerThreadFunction (id=0x4ba87b0) at multithread.c:336 Cannot access memory at address 0xe9fa5018" What does this tell me (or you)? Regards, Hardy Christian Anthon schrieb: Seems you are hitting all the hard rocks. Please do the following install "gdb" through yast, if it isn't installed on your system already. Then in a terminal type gdb gnubg and in the gdb prompt run and after the crash in the gdb prompt bt We may need to install some debug libraries and compile with debug symbols in gnubg, but let's try without it. Christian. -- Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Seems you are hitting all the hard rocks. Please do the following install "gdb" through yast, if it isn't installed on your system already. Then in a terminal type gdb gnubg and in the gdb prompt run and after the crash in the gdb prompt bt We may need to install some debug libraries and compile with debug symbols in gnubg, but let's try without it. Christian. On Sat, Feb 21, 2009 at 12:18 PM, Hardy Hübener wrote: > Hi Michael, Christian and all, > > > thx for your outstanding support!!! I finally managed to make it through the > make and make install, as far as I could see, without errors. > > When I start gnubg by typing "gnubg" in the terminal, I get the following > message: > > > "GNU Backgammon 0.90.0 > Copyright (C) 2008 by the AUTHORS; for details type `show version'. > This program comes with ABSOLUTELY NO WARRANTY; for details type > `show warranty'. > This is free software, and you are welcome to redistribute it > under certain conditions; type `show copying' for details. > Segmentation fault" > > > So there is a "segmentation fault" and gnubg is not running. Any idea? I use > the SNAPSHOT-20090220. > > > Cheers, > > Hardy > > > > -- > Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com > > > ___ > Bug-gnubg mailing list > Bug-gnubg@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-gnubg > ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Hi Michael, Christian and all, thx for your outstanding support!!! I finally managed to make it through the make and make install, as far as I could see, without errors. When I start gnubg by typing "gnubg" in the terminal, I get the following message: "GNU Backgammon 0.90.0 Copyright (C) 2008 by the AUTHORS; for details type `show version'. This program comes with ABSOLUTELY NO WARRANTY; for details type `show warranty'. This is free software, and you are welcome to redistribute it under certain conditions; type `show copying' for details. Segmentation fault" So there is a "segmentation fault" and gnubg is not running. Any idea? I use the SNAPSHOT-20090220. Cheers, Hardy -- Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
We all have to learn Linux somehow. We were all Linux dummies at one time :) The last set of errors you sent is because of libxml missing: You will need: http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/libxml-1.8.17-480.51.x86_ 64.html Looking at config.log you likely need: http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/freetype2-2.3.7-23.15.x86 _64.html http://rpmfind.net//linux/RPM/opensuse/updates/11.1/x86_64/libpng12-0-32bit- 1.2.31-4.35.1.x86_64.html http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/cairo-1.8.0-5.1.x86_64.ht ml http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/pango-1.22.1-2.11.x86_64. html http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/sqlite3-3.6.4-1.13.x86_64 .html http://rpmfind.net//linux/RPM/opensuse/updates/11.1/x86_64/gtk2-devel-2.14.4 -8.5.2.x86_64.html http://rpmfind.net//linux/RPM/opensuse/11.1/x86_64/gtkglext-1.2.0-139.67.x86 _64.html I couldn't find packages for gstreamer for suse. So this may be a problem still. If you can find them great. I may have missed some, but this should help for the moment. Michael ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
I guess SUSE is still RPM based. After looking at rpmfind, if you are using x86_64 (Your first email indicated it) you will want to install this: http://rpmfind.net//linux/RPM/opensuse/updates/11.1/x86_64/python-devel-2.6. 0-2.22.1.x86_64.html This should at least get you passed the first set of errors. On 20/02/09 5:02 PM, "Michael Petch" wrote: > Unfortunately I'm not a SUSE person so I'm not sure where the repository for > the development files (For things like python, cairo, etc reside). > > Michael ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
On 20/02/09 4:54 PM, "Hardy Hübener" wrote: > Hi Christian, > > > disregard my last mail ... I was in the wrong folder. > Running from wrong directory will do it ;-) [snip] > In file included from dbprovider.c:28: > gnubgmodule.h:32:20: error: Python.h: No such file or directory > dbprovider.c:43: error: expected =¹, ,¹, ;¹, asm¹ or __attribute__¹ > before *¹ token > dbprovider.c:44: error: expected )¹ before *¹ token > dbprovider.c: In function GetDBProvider¹: > [snip] What this says is that your system is missing dependencies required to build GnuBG. In this case python.h (Header file) is missing. This would imply you either don't have python installed, or you don't have the python development files installed. What might help Christian and I more is if you can email us directly (Don't use the mailing list since the attachments could be large) a copy of these 2 files: config.h config.log These two files contain information about what the build process sees on your system, and what other things may be missing. Unfortunately I'm not a SUSE person so I'm not sure where the repository for the development files (For things like python, cairo, etc reside). Michael ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
> > To add back the executable flag to autogen.sh one can issue a command like: > > chmod 755 autogen.sh > I just realized something. Usually if the executable flag is nlot set you would get soemthing like: -bash: ./autogen.sh: Permission denied Rather than file not found. When you issue: ./autogen.sh You are adding the period at the front right? The PERIOD is important as well as the / (Slash) . If you leave off the period then you are trying to run a program called autogen.sh in the root directory (Sort of like C:\ in windows). ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Hi Christian, disregard my last mail ... I was in the wrong folder. ./autogen.sh and ./configure --enable-threads worked. But with the command "make" I get the following report: make all-recursive make[1]: Entering directory `/root/gnubg-source/gnubg' Making all in lib make[2]: Entering directory `/root/gnubg-source/gnubg/lib' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/lib' Making all in doc make[2]: Entering directory `/root/gnubg-source/gnubg/doc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/doc' Making all in met make[2]: Entering directory `/root/gnubg-source/gnubg/met' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/met' Making all in po make[2]: Entering directory `/root/gnubg-source/gnubg/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/po' Making all in m4 make[2]: Entering directory `/root/gnubg-source/gnubg/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/m4' Making all in xpm make[2]: Entering directory `/root/gnubg-source/gnubg/xpm' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/xpm' Making all in sounds make[2]: Entering directory `/root/gnubg-source/gnubg/sounds' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/sounds' Making all in board3d make[2]: Entering directory `/root/gnubg-source/gnubg/board3d' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/board3d' Making all in textures make[2]: Entering directory `/root/gnubg-source/gnubg/textures' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/textures' Making all in scripts make[2]: Entering directory `/root/gnubg-source/gnubg/scripts' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/scripts' Making all in flags make[2]: Entering directory `/root/gnubg-source/gnubg/flags' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/flags' Making all in fonts make[2]: Entering directory `/root/gnubg-source/gnubg/fonts' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/fonts' Making all in non-src make[2]: Entering directory `/root/gnubg-source/gnubg/non-src' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/non-src' Making all in pixmaps make[2]: Entering directory `/root/gnubg-source/gnubg/pixmaps' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/gnubg-source/gnubg/pixmaps' Making all in . make[2]: Entering directory `/root/gnubg-source/gnubg' gcc -DHAVE_CONFIG_H -I. -I./lib -I./board3d - DLOCALEDIR=\"/usr/local/share/locale\" -fPIC -I/usr/include/python2.6 - I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread - I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include - DDOCDIR='"/usr/local/share/doc/gnubg"' -DDATADIR='"/usr/local/share"' - DPKGDATADIR='"/usr/local/share/gnubg"' -g -O2 -MT dbprovider.o -MD -MP -MF .deps/dbprovider.Tpo -c -o dbprovider.o dbprovider.c In file included from dbprovider.c:28: gnubgmodule.h:32:20: error: Python.h: No such file or directory dbprovider.c:43: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token dbprovider.c:44: error: expected ‘)’ before ‘*’ token
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
On 20/02/09 4:34 PM, "Hardy Hübener" wrote: > > I fear this is a "I don't understand Linux problem" :-( > > I have downloaded the current soure and unzipped it into the directory > /root/gnubg-source/ > > Then I started a Terminal, changed into that directory and typed > "./autogen.sh". > > The directory does contain a file called autogen.sh. Nevertheless I get > the error "No such file or directory". I am confused. > > > Hardy :-? > Hi Hardy, Christian is asking all the same things I would. The big one is, what was the name of the file you downloaded (and from where) that contained the source? And how did you extract/unzip it? If autogen.sh is in the directory but you can't run it, it means the flag that says "This file is an executable" is no longer set for that file. The question is, how did it get removed. In the windows world a program is generally only executable if it was built as an executable, and has .EXE on the end (This is a generality). In the Linux world, text files can be executable as well as binary programs made with a C compiler. A text file has to be structured a certain way (The first line says what program should interpret the text - like perl, bash, php etc). The caveat is that text files that are expected to be executed must also be flagged in the file system appropriately. There are attributes for each file (Including permissions, whether they are executable or not etc). To add back the executable flag to autogen.sh one can issue a command like: chmod 755 autogen.sh Its beyond the scope of this message, but for your purposes this will set the "executable bit" on the file. More information about chmod can be found with the manpages. To get the manpages for chmod issue: man chmod Once the executable bit is set you should be able to run it again with: ./autogen.sh I should point out, that resolving why the exectuable flag on this file should probably be investigated - since your source files seem to be in an unusual state. If you can answer the 2 questions in my first paragraph, it will likely help Christian and I. Michael ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Hi Christian, I fear this is a "I don't understand Linux problem" :-( I have downloaded the current soure and unzipped it into the directory /root/gnubg-source/ Then I started a Terminal, changed into that directory and typed "./autogen.sh". The directory does contain a file called autogen.sh. Nevertheless I get the error "No such file or directory". I am confused. Hardy :-? Christian Anthon schrieb: On Fri, Feb 20, 2009 at 11:39 PM, Hardy Hübener wrote: Thx Christian for your help! When trying to install the required development libraries I can't find cairo2 and gmp3. I think that Cairo will be installed already because of gtk. gmp doesn't matter. When typing "./autogen.sh" (being at the top level of the unzipped gnubg install files) I get the error "No such file or directory". That is a bit weird. Is there a file named autogen.sh in the directory? Where did you get the source.? Does bash autogen.sh work? Christian. -- Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
On Fri, Feb 20, 2009 at 11:39 PM, Hardy Hübener wrote: > Thx Christian for your help! > > > When trying to install the required development libraries I can't find > cairo2 and gmp3. I think that Cairo will be installed already because of gtk. gmp doesn't matter. > > When typing "./autogen.sh" (being at the top level of the unzipped gnubg > install files) I get the error "No such file or directory". > That is a bit weird. Is there a file named autogen.sh in the directory? Where did you get the source.? Does bash autogen.sh work? Christian. ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Thx Christian for your help! When trying to install the required development libraries I can't find cairo2 and gmp3. When typing "./autogen.sh" (being at the top level of the unzipped gnubg install files) I get the error "No such file or directory". Hardy Christian Anthon schrieb: I'm not too familiar with suse, but it shouldn't be too difficult. I assume that you have the source already. In the top level directory is a file called INSTALL. Here the tools that you need are listed. Install them using the normal yast installation tool. Then you need the development libraries listed in the file. On suse I believe they are called something like gtk2-devel, glib2-devel, libpng-devel Install all those as well. Now the top level directory you type ./autogen.sh ./configure --enable-threads make and as root make install That should be it. Otherwise report back with more exact problems. Christian. -- Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com ___ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
Re: [Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
I'm not too familiar with suse, but it shouldn't be too difficult.
I assume that you have the source already. In the top level directory
is a file called INSTALL. Here the tools that you need are listed.
Install them using the normal yast installation tool. Then you need
the development libraries listed in the file. On suse I believe they
are called something like
gtk2-devel, glib2-devel, libpng-devel
Install all those as well.
Now the top level directory you type
./autogen.sh
./configure --enable-threads
make
and as root
make install
That should be it. Otherwise report back with more exact problems.
Christian.
On Fri, Feb 20, 2009 at 9:22 PM, Hardy Hübener
wrote:
> Hi everyone,
>
>
> I know this is not a helpdesk for GNUBG or Linux, but perhaps someone can
> help me getting GNUBG run on my Open Suse 11.1 (x86_64) computer ("standard
> installation"). I am not that familiar with Linux, but wanna give it a try.
> But what's the use of having a computer if GNUBG is not running on it?!?!
>
> The steps for building GBUBG from source on UBUNTU don't work for Open Suse
> Linux. Can anyone please give me advice, which steps to take to convert the
> source into a runable GNUBG version on my computer?
>
>
> Many thanks in advance!
>
>
> Cheers,
>
> Hardy ;-)
>
> --
> Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com
>
>
>
> ___
> Bug-gnubg mailing list
> Bug-gnubg@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>
___
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnubg
[Bug-gnubg] Building gnubg from source on a Open Suse 11.1 computer
Hi everyone,
I know this is not a helpdesk for GNUBG or Linux, but perhaps someone
can help me getting GNUBG run on my Open Suse 11.1 (x86_64) computer
("standard installation"). I am not that familiar with Linux, but wanna
give it a try. But what's the use of having a computer if GNUBG is not
running on it?!?!
The steps for building GBUBG from source on UBUNTU don't work for Open
Suse Linux. Can anyone please give me advice, which steps to take to
convert the source into a runable GNUBG version on my computer?
Many thanks in advance!
Cheers,
Hardy ;-)
--
Hardy's Backgammon Pages --> www.hardys-backgammon-pages.com
___
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnubg
