[uae] Re: CAPS plugin (was 'Compile problems with UAE 0.8.25')



Giulio Canevari wrote:
Derek Piper wrote:


Hi,

I have been trying to compile UAE 0.8.25 from source on Debian Woody and have not been having an easy time of it.

I am using these configure options:

--prefix=/usr/local/uae/ --with-x --with-sdl --with-sdl-sound --with-sdl-gfx --with-zlib --enable-sound --enable-x86assembly --enable-ui --enable-bsdsock --enable-aga --enable-cycle-exact-cpu --enable-compatible-cpu --enable-jit --enable-natmem --with-caps --with-caps-prefix=/usr/local/uae/support/ipfdevlib_linux/


How many options! ( most of them are not useful too ).

Heh.. yea, there are a lot. I saw 'auto' on the configure help and wanted to be sure it was the same as letting it 'decide' for you.


Take a look at http://giuliogiuseppecarlo.interfree.it/uae/index.html , maybe you'll find the solution ( when i first wrote it i was using debian woody too ).

Anyway you should drop, since it's enabled by default, a lot of options, such as: --with-x ( if you use sdl ), --with-zlib ( default ), --enable-x86assembly, --enable-ui , --enable-bsdsock, --enable-cycle-exact-cpu, --enable-compatible-cpu

Okay, now I'm using these options:

--prefix=/usr/local/uae/
--enable-aga
--enable-cycle-exact-cpu
--enable-compatible-cpu
--with-sdl-gfx
--with-caps
--with-caps-prefix=/usr/local/uae/support/ipfdevlib_linux/



when I do 'make', it runs briefly and this error is seen amongst the output:


make -C tools build68kc
make[2]: Entering directory `/usr/src/uae-0.8.25-20040302/src/tools'
make[2]: *** No rule to make target `build68kc'.  Stop.
make[2]: Leaving directory `/usr/src/uae-0.8.25-20040302/src/tools'
make[1]: *** [tools/build68k] Error 2
make[1]: *** Waiting for unfinished jobs....

Every time I run make it gets a little bit closer to finishing. Is the order of the targets incorrect? Why does it need to have to be 'prodded' along like that? 'make' needs to be run 3 times in order for the build to complete. Is that normal?


Of course no.

With the revised configure options, it still exhibits that behaviour. I have to type 'make' a few times to get it to compile fully. Anyone know why it does that?



Upon running, that build opens the UI but when running a standard A500 KS1.3 config it locks up before the Kickstart has fully initialized - a dark grey 'screen', which as far as I can remember on a real Amiga was after the 'hardware' was initialized but before the software was. This config has worked fine on the UAE 0.8.22 that is in Debian woody by the way.


Without the SDL options above I get a build that at least loads the kickstart.

I have the following SDL debian packages installed:

libsdl1.2debian
libsdl1.2debian-oss
libsdl1.2-dev


Should be enougth.

Okay. I did find that my problems only came when I had '--with-sdl-sound' in my options, so I guess I'll leave that out. I still get sound.




However, when I try and run a CAPS image I get the message 'Failed to load CAPS plug-in' even though the shared library is in the location above. How can I check what location UAE is needing the library in? Should the directory be included in /etc/ld.so.conf ? I tried that and it didn't make any difference. The contents of my /usr/local/uae/support/ipfdevlib_linux/ directory is that of the CAPS
ipfdevlib_linux.tgz file from caps-project.org.


I don't remember exactly but there are instructions in the ipf package, and they are clear afair.

Well, like I said I already tried adding the exact directory to ld.so.conf. I had added the symlink in /usr/lib/ and it had made no difference. Unless there are some other 'instructions' I'm unaware of, shouldn't that be it? Where is uae trying to load the CAPS plug-in from? I have the library itself copied to /usr/lib/ now, and it still comes up with 'Failed to load CAPS plug-in.' and dies (yes, the file and path are world readable). Is anyone else trying to run UAE+CAPS on Debian Woody?


I've even tried it in the same directory as the UAE executable like WinUAE requires, but nothing helps.

I'd like to know where UAE is looking for the shared library.

There seems to be little information on it. I have the ipfdevlib tar.gz and all it has in it is this:

drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/examples/
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/examples/i686/
-rw-r--r-- KieronW/mkgroup_l_d 4212 2004-08-11 19:19:50 ipfdevlib_linux/examples/i686/ipfinfo
-rw-r--r-- KieronW/mkgroup_l_d 1778 2004-08-11 19:19:50 ipfdevlib_linux/examples/ipfinfo.c
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/examples/ppc/
-rw-r--r-- KieronW/mkgroup_l_d 3912 2004-08-11 19:21:18 ipfdevlib_linux/examples/ppc/ipfinfo
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/include/
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/include/caps/
-rw-r--r-- KieronW/mkgroup_l_d 5265 2004-08-11 19:19:50 ipfdevlib_linux/include/caps/capsimage.h
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/lib/
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/lib/i686/
-rw-r--r-- KieronW/mkgroup_l_d 53456 2004-08-11 19:19:50 ipfdevlib_linux/lib/i686/libcapsimage.so.2.0
drwxr-xr-x KieronW/mkgroup_l_d 0 2004-08-13 07:49:42 ipfdevlib_linux/lib/ppc/
-rw-r--r-- KieronW/mkgroup_l_d 63140 2004-08-11 19:21:18 ipfdevlib_linux/lib/ppc/libcapsimage.so.2.0
-rw-r--r-- KieronW/mkgroup_l_d 15416 2004-08-13 08:02:48 ipfdevlib_linux/LICENSE
-rw-r--r-- KieronW/mkgroup_l_d 698 2004-08-13 08:52:08 ipfdevlib_linux/HISTORY
-rw-r--r-- KieronW/mkgroup_l_d 403 2004-08-13 09:01:34 ipfdevlib_linux/README


Other related posts: