Login  •  Register


The time is now: Wed Apr 24, 2019 6:37 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 12 posts ]
Print view Previous topic  |  Next topic
Author Message
 Post subject: Basilisk for Linux
PostPosted: Tue Jun 01, 2010 10:10 am 
Offline
Space Cadet

Joined: Tue Jun 01, 2010 10:08 am
Posts: 3
Hello I do not have Windows or OSX, just Fedora 12 linux. How do I get the latest Basilisk running? Thanks.


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Tue Jun 01, 2010 10:52 am 
Offline
Tinkerer

Joined: Thu Feb 18, 2010 10:09 pm
Posts: 63
Code:
$ cvs -d :pserver:anoncvs@cvs.cebix.net:/home/cvs/cebix login
(password is "anoncvs")
$ cvs -d :pserver:anoncvs@cvs.cebix.net:/home/cvs/cebix checkout BasiliskII
$ cd BasiliskII/src/Unix
$ ./autogen.sh
check output if config is correct if no do ./configure with needed options
$ make
$ ./BasiliskII


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Tue Jun 01, 2010 6:58 pm 
Offline
Space Cadet

Joined: Tue Jun 01, 2010 10:08 am
Posts: 3
There is a lot of output after running the ./autogen.sh command. I notice at the end there is a summary. Does this look correct or am I missing something?

Code:
Basilisk II configuration summary:

SDL support ............................ : none
XFree86 DGA support .................... : yes
XFree86 VidMode support ................ : yes
fbdev DGA support ...................... : no
Enable video on SEGV signals ........... : yes
ESD sound support ...................... : yes
GTK user interface ..................... : gtk
mon debugger support ................... : no
Running m68k code natively ............. : no
Use JIT compiler ....................... : no
JIT debug mode ......................... : no
Floating-Point emulation core .......... : IEEE fpu core
Assembly optimizations ................. : i386
Addressing mode ........................ : direct
Bad memory access recovery type ........ : siginfo


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Tue Jun 01, 2010 8:11 pm 
Offline
Tinkerer

Joined: Thu Feb 18, 2010 10:09 pm
Posts: 63
yes it looks good


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Wed Jun 02, 2010 12:19 am 
Offline
Space Cadet

Joined: Tue Jun 01, 2010 10:08 am
Posts: 3
Alright, thanks, it seems to work well. I notice that many games do not run...I guess they are older and have to be run from minivmac?


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Wed Jun 02, 2010 6:01 am 
Offline
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 4539
Location: Sittard, The Netherlands
Hi,

Not all games work in Basilisk. Of course, checking their system requirements might provide insight into why.
I noticed you're not running with the JIT compiler enabled.

If you use
"NO_CONFIGURE=1 ./Autogen.sh" and wait for it to finish, you can then run ./configure with parameters. They are listed below. Your summary shows some of the results already in their default settings, but you can use e.g. --enable-jit-compiler to get the JIT compiler running.

--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-standalone-gui enable a standalone GUI prefs editor default=no
--enable-xf86-dga use the XFree86 DGA extension default=yes
--enable-xf86-vidmode use the XFree86 VidMode extension default=yes
--enable-fbdev-dga use direct frame buffer access via /dev/fb default=yes
--enable-vosf enable video on SEGV signals default=yes
--enable-sdl-static use SDL static libraries for linking default=no
--enable-sdl-video use SDL for video graphics default=no
--enable-sdl-audio use SDL for audio default=no
--enable-sdl-framework use SDL framework default=no
--enable-sdl-framework-prefix=PFX default=/Library/Frameworks
--enable-jit-compiler enable JIT compiler default=no
--enable-jit-debug activate native code disassemblers default=no
--enable-fpe=FPE specify which fpu emulator to use default=auto
--enable-addressing=AM specify the addressing mode to use default=fastest
--disable-gtktest do not try to compile and run a test GTK+ program
--disable-gtktest Do not try to compile and run a test GTK program
--disable-nls do not use Native Language Support
--disable-rpath do not hardcode runtime library paths
--disable-esdtest Do not try to compile and run a test ESD program
--disable-largefile omit support for large files

Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-esd support ESD for sound under Linux/FreeBSD default=yes
--with-gtk use GTK user interface default=yes
--with-mon use mon as debugger default=yes
--with-x use the X Window System
--with-gtk-prefix=PFX Prefix where GTK is installed (optional)
--with-gtk-exec-prefix=PFX Exec prefix where GTK is installed (optional)
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in includedir and libdir
--with-included-gettext use the GNU gettext library included here
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--with-gnome-config=GNOME_CONFIG Location of gnome-config
--with-esd-prefix=PFX Prefix where ESD is installed (optional)
--with-esd-exec-prefix=PFX Exec prefix where ESD is installed (optional)


Top
 Profile  
Reply with quote Post a reply  
 Post subject: checking for X... no
PostPosted: Sun Jul 04, 2010 11:24 pm 
Offline
Space Cadet

Joined: Sun Jul 04, 2010 11:10 pm
Posts: 9
Location: Nashua, NH
Hi,

Trying to follow your instructions, and all goes well until the ./autogen.sh gets to the configure section. I'm seeing:

checking for X... no
configure: error: You need X11 to run Basilisk II.

I'm running Ubuntu 9.10 Karmic Koala using Gnome window manager. However, if I run xterm or xclock or any of the basic X "checks" they work fine. I even tried running autogen.sh in an Xterm window. It gives me the same error.

How do I get past this?

BTW, I've been a BasiliskII user on Windows for several years. I'm trying to move to Ubuntu and was happy to see BasiliskII works with Linux. Thank you very much for your assistance.

Earl


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Mon Jul 05, 2010 6:44 am 
Offline
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 4539
Location: Sittard, The Netherlands
Hi Earl,

Basilisk need the X development header files etc. Please check your repository for those and install them.


Best,
Cat_7


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jul 05, 2010 7:01 pm 
Offline
Space Cadet

Joined: Sun Jul 04, 2010 11:10 pm
Posts: 9
Location: Nashua, NH
Hi again,

Well, I did find and install several X11 libraries. That did seem to work. I now have an executable BasiliskII file.

However, when I run the file I get a number of errors:


earl@Austin:~/BasiliskII/src/Unix$ ./BasiliskII
Basilisk II V1.0 by Christian Bauer et al.

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function

(process:31013): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:31013): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(process:31013): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
Segmentation fault
earl@Austin:~/BasiliskII/src/Unix$


These look like build errors to me, but I suppose they could be configuration errors.

I've been looking for BasiliskII build/installation documentation for Linux but so far haven't found anything of substance other than this forum. I'm not even sure I have all the libraries required to build a good binary, although my configuration summary closely matched land's second post:

Basilisk II configuration summary:

SDL support ............................ : none
XFree86 DGA support .................... : no
XFree86 VidMode support ................ : no
fbdev DGA support ...................... : yes
Enable video on SEGV signals ........... : yes
ESD sound support ...................... : yes
GTK user interface ..................... : gtk2
mon debugger support ................... : no
Running m68k code natively ............. : no
Use JIT compiler ....................... : no
JIT debug mode ......................... : no
Floating-Point emulation core .......... : IEEE fpu core
Assembly optimizations ................. : i386
Addressing mode ........................ : direct
Bad memory access recovery type ........ : siginfo

Configuration done. Now type "make" (or "gmake").


Do I have build errors or configuration errors? If configuration errors, can someone please provide examples of a working pref's file? Since I don't see a configuration GUI I suppose I'm going to have to edit the pref's file manually. Any help or pointers provided is greatly appreciated.


Earl


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Mon Jul 05, 2010 7:42 pm 
Offline
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 4539
Location: Sittard, The Netherlands
Hi,

I don't know what to do about those errors. They might be related to your GLibc version, but I don't know. I hope someone else with better linux/compiling knowledge comes along and answers your question.

When you start Basilisk in Linux, the GUI should automatically appear. You get only the errors? If so, you might try to compile the source code I provided elsewhere in the forum.

Best,
Cat_7


Top
 Profile  
Reply with quote Post a reply  
 Post subject: Weird, but good!
PostPosted: Thu Jul 08, 2010 1:46 am 
Offline
Space Cadet

Joined: Sun Jul 04, 2010 11:10 pm
Posts: 9
Location: Nashua, NH
Hi,

I set aside the original cvs source I has used and checked it out again (same commands as was given by Amade in post 2; same as I did the first time). Recompiled and everything works. The only thing I can think of is that some of the modules compiled before I updated the libraries were used on the final build, which caused my errors.

Anyway, I get the setting configuration settings window now, and am very pleased.

Thank you so much for your help.


Earl


Top
 Profile  
Reply with quote Post a reply  
 Post subject:
PostPosted: Sat Jul 10, 2010 6:30 pm 
Offline
Inquisitive Elf

Joined: Mon Feb 16, 2009 1:06 am
Posts: 39
Just one more hint for anyone who's interested: the Linux package "hfsutils" contains some useful command line tools for moving files to and from Mac-format disks (and disk images) and there's also a Tk-based GUI that uses "hfsutils" called "xhfs", if you want to move stuff graphically. Before I discovered this, I would just use HFVExplorer in Wine, but the native solution is a bit more stable.


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 1 of 1 [ 12 posts ]


Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group