Login  •  Register


The time is now: Wed May 22, 2013 10:59 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 2 of 2 [ 32 posts ]    Go to page Previous  1, 2
Print view Previous topic  |  Next topic
Author Message
 Post subject: Compilation problems
PostPosted: Tue May 18, 2010 8:21 am 
Offline
Student Driver

Joined: Thu May 27, 2004 9:21 am
Posts: 18
Cat_7 wrote:


Cat_7, I've managed to get further with your tar-ball than with any other SheepShaver source but it still won't compile - I'm getting the following error:

ether_unix.cpp:68:22: error: libslirp.h: No such file or directory

Any ideas?

(I'm running Ubuntu 9.04 Jaunty Jackalope on an x86_64 box)


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue May 18, 2010 11:29 am 
Offline
Expert User
User avatar

Joined: Fri Feb 13, 2004 8:59 am
Posts: 3126
Location: Sittard, The Netherlands
Is the file libslirp.h on your system? If so, try to edit the ether_unix.sys so it points to that file.
Otherwise, find a libslirp.h file and place it with the source. I don't know exactly where it should go.
This might work, but I'm not sure....
https://projects.honeynet.org/sebek/bro ... libslirp.h

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject: Re: Compilation problems
PostPosted: Tue May 18, 2010 11:37 am 
Offline
Student Driver

Joined: Wed Nov 19, 2008 4:58 pm
Posts: 24
domiel wrote:
ether_unix.cpp:68:22: error: libslirp.h: No such file or directory

Copy the contents of the BasiliskII/src/slirp/ into SheepShaver/src/slirp/


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue May 18, 2010 2:00 pm 
Offline
Expert User
User avatar

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

Did you download both Basilisk and Sheepshaver source? You need to have both folders extracted in one folder.
The first step in the compilation process is to make links to the Basilisk source (much of which is shared with sheepshaver)

So, if you have a folder "source", you place both unpacked folders BasiliskII and SheepShaver in that folder.
Next, you cd into the SheepShaver folder and issue the command "make links"
then cd into src/Unix and compile the SheepShaver soruce.

Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue May 18, 2010 4:28 pm 
Offline
Student Driver

Joined: Thu May 27, 2004 9:21 am
Posts: 18
Cat_7 wrote:
Hi,

Did you download both Basilisk and Sheepshaver source? You need to have both folders extracted in one folder.
The first step in the compilation process is to make links to the Basilisk source (much of which is shared with sheepshaver)

So, if you have a folder "source", you place both unpacked folders BasiliskII and SheepShaver in that folder.
Next, you cd into the SheepShaver folder and issue the command "make links"
then cd into src/Unix and compile the SheepShaver soruce.

Best,
Cat_7


Cat_7, uhhu,

Thankyou both that has gotten me a bit further but I'm getting another error:

make: *** No rule to make target `obj/video_sdl.o', needed by `SheepShaver'. Stop.

Any thoughts on this one?

Thanks again!


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue May 18, 2010 5:20 pm 
Offline
Expert User
User avatar

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

You need to install SDL libraries as well.
Instructions on compiling are here on the forum somewhere. I'll dig them up once I get home.

Make a folder for SDL as well in your Basilisk and SheepShaver source folder.
These are the commands to install SDL into it's own folder:
(Make sure svn is installed in your linux distro)

mkdir SDL
cd SDL
svn checkout http://svn.libsdl.org/tags/SDL/release-1.2.10
cd release-1.2.10
./autogen.sh
./configure --disable-shared --prefix=`pwd`
make
make install
PATH=`pwd`/bin:$PATH
export PATH

Then, in the same terminal window, execute the earlier commands:
cd SheepShaver
make links
cd src/Unix
./autogen.sh



Best,
Cat_7


Top
 Profile  
Post a reply  
 Post subject:
PostPosted: Tue May 18, 2010 5:34 pm 
Offline
Student Driver

Joined: Thu May 27, 2004 9:21 am
Posts: 18
Cat_7 wrote:
Hi,

You need to install SDL libraries as well.
Instructions on compiling are here on the forum somewhere. I'll dig them up once I get home.

Best,
Cat_7


AFAIK I have installed SDL - according to apt:

Code:
# aptitude search sdl|grep ^i
i A libsdl-console                  - console that can be added to any SDL appli
i   libsdl-console-dev              - development files for libsdl-console     
i A libsdl-gfx1.2-4                 - drawing and graphical effects extension fo
i   libsdl-gfx1.2-dev               - development files for SDL_gfx             
i A libsdl-image1.2                 - image loading library for Simple DirectMed
i   libsdl-image1.2-dev             - development files for SDL 1.2 image loadin
i A libsdl-mixer1.2                 - mixer library for Simple DirectMedia Layer
i   libsdl-mixer1.2-dev             - development files for SDL1.2 mixer library
i A libsdl-net1.2                   - network library for Simple DirectMedia Lay
i   libsdl-net1.2-dev               - Development files for SDL network library
i   libsdl-pango-dev                - text rendering with Pango in SDL applicati
i A libsdl-pango1                   - text rendering with Pango in SDL applicati
i A libsdl-sge                      - extension of graphic functions for the SDL
i   libsdl-sge-dev                  - development files for libsdl-sge         
i A libsdl-sound1.2                 - Decoder of several sound file formats for
i   libsdl-sound1.2-dev             - Development files for SDL_sound           
i A libsdl-ttf2.0-0                 - ttf library for Simple DirectMedia Layer w
i   libsdl-ttf2.0-dev               - development files for SDL ttf library (ver
i   libsdl1.2-dev                   - Simple DirectMedia Layer development files
i   libsdl1.2debian                 - Simple DirectMedia Layer                 
i   libsdl1.2debian-alsa            - Simple DirectMedia Layer (with X11 and ALS

btw. There's a small but subtle error with your SheepShaver_src_2504102010.tar.gz tarball:
when you do a "make links" you end up with
SheepShaver/src/slirp/slirp -> ../../BasiliskII/src/slirp
rather than
SheepShaver/src/slirp -> ../../BasiliskII/src/slirp
I believe this is because Sheepshaver/src already contains an empty directory called slirp

Thanks again!


Top
 Profile  
Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 2 of 2 [ 32 posts ]    Go to page Previous  1, 2


Who is online

Users browsing this forum: Google [Bot] and 1 guest


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