SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am running Slackware10.2 with KDE desktop.
I am trying to get "freevo" up & running, but it seem to have a billion
dependencies; for most of which there does not seem to be a slackware pkg.
I use the program "checkinstall" to build slackware pkg.
I am now trying to build a pkg for "mmpython-0.4.9" but it keeps giving
me a lot of error; I am pasting a few lines below
***********************
/usr/local/include/dvdread/ifo_types.h:68: error: syntax error before
"uint8_t"
/usr/local/include/dvdread/ifo_types.h:70: error: syntax error before
"second"
/usr/local/include/dvdread/ifo_types.h:71: error: syntax error before
"frame_u"
/usr/local/include/dvdread/ifo_types.h:78: error: syntax error before
"uint8_t"
/usr/local/include/dvdread/ifo_types.h:143: error: syntax error before
"uint16_t"
/usr/local/include/dvdread/ifo_types.h:145: error: syntax error before
"code_extension"
/usr/local/include/dvdread/ifo_types.h:146: error: syntax error before
"unknown3"
/usr/local/include/dvdread/ifo_types.h:175: error: syntax error before
'}' token
/usr/local/include/dvdread/ifo_types.h:231: error: syntax error before
"uint8_t"
/usr/local/include/dvdread/ifo_types.h:258: error: syntax error before
"uint8_t"
/usr/local/include/dvdread/ifo_types.h:260: error: syntax error before
"lang_extension"
/usr/local/include/dvdread/ifo_types.h:261: error: syntax error before
"code_extension"
/usr/local/include/dvdread/ifo_types.h:270: error: syntax error before
"uint16_t"
/usr/local/include/dvdread/ifo_types.h:272: error: syntax error before
"nr_of_cell"
/usr/local/include/dvdread/ifo_types.h:273: error: syntax error before
"last_byte"
/usr/local/include/dvdread/ifo_types.h:274: error: syntax error before
'*' token
***********************
I have got the "libdvdread-0.9.6" pkg installed, which was also made by
me from source using "checkinstall"
I also tried to make a "lsdvd-0.16" pkg but when I tried to run
"./configure" it kept giving me an error; something like.... "header
files for dvdread could not be found"
but the files were clearly there!!
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
Posts: 1,757
Rep:
I'm running a stock Slackware 10.2 version with all the updates. I downloaded and unpacked mmpython-0.4.9, ran checkinstall, and didn't get any errors. The README didn't say anything about dependecies other than running the 'setup.py' file, so...
# cd mmpython-0.4.9
# checkinstall python setup.py install
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
Posts: 1,757
Rep:
I downloaded and unpacked libdvdread-0.9.6, ran configure, make, and checkinstall, no errors. I'm kind of at a loss as to why your having so much difficulties. Possibly due the packages in question are non-stable 0.x.x versions?
# cd libdvdread-0.9.6
# configure
# make
# checkinstall
--------------------------------------------------------------------
test -z "/usr/local/include/dvdread" || mkdir -p -- "/usr/local/include/dvdread"
/usr/bin/ginstall -c -m 644 'dvd_reader.h' '/usr/local/include/dvdread/dvd_reader.h'
/usr/bin/ginstall -c -m 644 'ifo_types.h' '/usr/local/include/dvdread/ifo_types.h'
/usr/bin/ginstall -c -m 644 'ifo_read.h' '/usr/local/include/dvdread/ifo_read.h'
/usr/bin/ginstall -c -m 644 'ifo_print.h' '/usr/local/include/dvdread/ifo_print.h'
/usr/bin/ginstall -c -m 644 'nav_types.h' '/usr/local/include/dvdread/nav_types.h'
/usr/bin/ginstall -c -m 644 'nav_read.h' '/usr/local/include/dvdread/nav_read.h'
/usr/bin/ginstall -c -m 644 'nav_print.h' '/usr/local/include/dvdread/nav_print.h'
/usr/bin/ginstall -c -m 644 'cmd_print.h' '/usr/local/include/dvdread/cmd_print.h'
make[2]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6/dvdread'
make[1]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6/dvdread'
Making install in src
make[1]: Entering directory `/home/bsdunix/src/libdvdread-0.9.6/src'
make[2]: Entering directory `/home/bsdunix/src/libdvdread-0.9.6/src'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6/src'
make[1]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6/src'
make[1]: Entering directory `/home/bsdunix/src/libdvdread-0.9.6'
make[2]: Entering directory `/home/bsdunix/src/libdvdread-0.9.6'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6'
make[1]: Leaving directory `/home/bsdunix/src/libdvdread-0.9.6'
All I can say is that it has made me more jealous & even mad :-)
Can you please send me a list of all the pkgs installed on your system.... I am asking this cos I made a slim installation, so may be I am missing a certain pkg or somthing...
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
Posts: 1,757
Rep:
I have a tendency to reinstall the OS for testing purposes. I normally accept all the packages selected at the "Package Series Selection" screen prompt, remove anything related to RAID, and install all Python packages. I upgrade all installed packages with the latest security updates. I then installed checkinstall from the /extra package directory from a local mirror. This isn't exactly what your looking for, but it should give you an idea what packages I have installed. If you need a more detailed list I can send a list to you via this forum's email app.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.