liquidzoo Posted December 29, 2003 Report Share Posted December 29, 2003 I just bought a Rio s30s. It's a pretty good little mp3 player. 64 MB built in memory, expandible to 576 with SD cards. Trouble is, I can't get it to work. It has a USB connection. I tried to modprobe both usb-storage and rio500, both succeeded with no errors, but neither is letting me access the rio. Next I tried rio500_tui, but that had some errors that I couldn't work out. Next I tried rioutil because it's homepage says it works with the S-series of Rio players. now I am getting a compile error that I can't work out and maybe someone here has had a similar experience and can lend a hand. Here's the full make output: [ rioutil-1.4.2b ]$ make Making all in librioutil make[1]: Entering directory `/home/liquidzoo/Downloads/rioutil-1.4.2b/librioutil' source='rio.c' object='rio.lo' libtool=yes \ depfile='.deps/rio.Plo' tmpdepfile='.deps/rio.TPlo' \ depmode=gcc3 /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g3 -c -o rio.lo `test -f 'rio.c' || echo './'`rio.c rm -f .libs/rio.lo gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g3 -c rio.c -MT rio.lo -MD -MP -MF .deps/rio.TPlo -fPIC -DPIC -o .libs/rio.lo In file included from rio.c:45: ../include/driver.h:113:17: usb.h: No such file or directory make[1]: *** [rio.lo] Error 1 make[1]: Leaving directory `/home/liquidzoo/Downloads/rioutil-1.4.2b/librioutil' make: *** [all-recursive] Error 1 [ rioutil-1.4.2b ]$ Anyone have a clue? libusb is installed, the README file does say that is needed, but aside from that, I have no clue. Quote Link to comment Share on other sites More sharing options...
iphitus Posted December 30, 2003 Report Share Posted December 30, 2003 I realise you probably do, but to be sure, You might have libusb, but do you have libusb-devel? Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted December 30, 2003 Author Report Share Posted December 30, 2003 That I am not sure of. I assume so, but I will double check again when I get home, just to make sure. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted December 30, 2003 Report Share Posted December 30, 2003 [root@localhost patrick]# rpm -qa | grep libusb libusb0.1_4-devel-0.1.7-1mdk libusb0.1_4-0.1.7-1mdk libusb0.1_4-static-devel-0.1.7-1mdk I've got two libusb-devel libraries installed; you might want to check for both. It can't find the usb headers either because they're not installed(no devel libs) or it's not searching the directory where they are installed. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted December 30, 2003 Author Report Share Posted December 30, 2003 ok, installed libusb-devel and libusb-stativ-devel Now it gets a bit farther along in the make process, but still errors out. I can't figure out what it's looking for here. make[1]: Entering directory `/home/liquidzoo/Downloads/rioutil-1.4.2b/src' /bin/sh ../libtool --mode=link gcc -g -O3 -o rioutil main.o getopt.o getopt1.o -L/usr/local/lib ../librioutil/librioutil.la -lz -lz gcc -g -O3 -o .libs/rioutil main.o getopt.o getopt1.o -L/usr/local/lib ../librioutil/.libs/librioutil.so -lz -lz -lz -lz -Wl,--rpath -Wl,/usr/local/lib ../librioutil/.libs/librioutil.so: undefined reference to `usb_open_rio' ../librioutil/.libs/librioutil.so: undefined reference to `write_bulk' ../librioutil/.libs/librioutil.so: undefined reference to `read_bulk' ../librioutil/.libs/librioutil.so: undefined reference to `usb_close_rio' ../librioutil/.libs/librioutil.so: undefined reference to `control_msg' ../librioutil/.libs/librioutil.so: undefined reference to `usb_setdebug' collect2: ld returned 1 exit status make[1]: *** [rioutil] Error 1 make[1]: Leaving directory `/home/liquidzoo/Downloads/rioutil-1.4.2b/src' make: *** [all-recursive] Error 1 [ rioutil-1.4.2b ]$ Quote Link to comment Share on other sites More sharing options...
iphitus Posted December 31, 2003 Report Share Posted December 31, 2003 I am not sure, but a shot in the dark: if you are compiling with GCC 3.2/3.2, try compiling with 2.95 instead. This worked with a game for me. although a driver is far from a game....... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.