On 2015-07-23 5:40 AM, Thomas A. Moulton wrote: > Ok, I have done this before and it is usually a piece of cake... > > I am on a new computer, also switched from Debian to Uburuntu > > Installed new SSH keys at savanna, check out source, autogen, configure > (no options) make > and then try to run ./gnubg > > I get no output.. even ./gnubg --tty gives no output > > I checked config.log for WARNINGS and fixed those > > I also noticed the process (gnubg) is running at 100% cpu > > anyone seen this before? >
First off I notice that you didn't do an install. I'd recommend that so all the support files are available. This should do the trick: sudo make install Then use ./gnubg to launch. Same thing happen? Assuming you pulled out the head revision from source control what you are experiencing is something I haven't seen before. The fact you don't get the copyright notice with gnubg --tty is odd in itself. What happens if you redo it doing: make clean ./configure --without-gtk make I'm just curious whether this is a GTK problem. If I get a chance I'll dig up my old Ubuntu 14.04. One other thing I recommend is to make sure all the build dependencies are met. You should be able to do that with: sudo apt-get build-dep gnubg sudo apt-get install libcurl4-openssl-dev The second line makes sure you have the dependency for random.org to function properly as a dice source. Then do: make clean ./autogen.sh ./configure make sudo make install and then run ./gnubg -- Michael Petch GNU Backgammon Maintainer / Developer OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304 _______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
