I seem unable to compile k9copy from SlackBuilds.org.

I have all the libdvd* packages installed as well as MPlayer and dvdauthor.

When I run the script I get to the point of:

Good - your configure finished. Start make now

The compiling starts and within seconds the script stops. Here is the end of the script output:

In file included from ../libk9copy/k9common.h:34,
from cpu_state.cpp:25:
/usr/include/dvdread/ifo_print.h:27:58: error: dvdnav/ifo_types.h: No such file or directory
In file included from ../libk9copy/k9common.h:34,
from cpu_accel.cpp:26:
/usr/include/dvdread/ifo_print.h:27:58: error: dvdnav/ifo_types.h: No such file or directory
if /bin/sh ../libtool --silent --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../k9vamps -I../libdvdnav -I../libk9copy -I. -I/usr/lib/qt/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -O2 -march=i486 -mtune=i686 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -fpermissive -MT header.lo -MD -MP -MF ".deps/header.Tpo" -c -o header.lo header.cpp; \
then mv -f ".deps/header.Tpo" ".deps/header.Plo"; else rm -f ".deps/header.Tpo"; exit 1; fi
In file included from ../libk9copy/k9common.h:34,
from decode.cpp:25:
/usr/include/dvdread/ifo_print.h:27:58: error: dvdnav/ifo_types.h: No such file or directory
cpu_state.cpp:39: warning: unused parameter 'state'
make[2]: *** [cpu_state.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [decode.lo] Error 1
make[2]: *** [cpu_accel.lo] Error 1
In file included from ../libk9copy/k9common.h:34,
from header.cpp:26:
/usr/include/dvdread/ifo_print.h:27:58: error: dvdnav/ifo_types.h: No such file or directory
header.cpp:741: warning: unused parameter 'mpeg2dec'

I am not a compiling expert but the compile seems to have problems with the various libdvd* packages. I installed all of those from SlackBuilds.org. I have no problem reading or playing DVD movies with xine or MPlayer.

Any ideas?

Start with the obvious, do you have this file /usr/include/dvdnav/ifo_types.h installed? Maybe the libdvdnav installation didn't go according to plan and you didn't notice.

Okay, that helped. There were no such files installed with the SlackBuild libdvdnav package. The libdvdread package did install such files, however. I then created three soft links in /usr/include/libdvdnav to those same files located in /usr/include/libdvdread.

Compiling was successful.

Installing and running the package was successful too.

Testing will have to wait until next weekend, however.

Thanks for helping!

Unlucky.Dude.I have had problems with slackbuilds from slackbuilds.org too.I switched to using the builds from Slacky and have encountered no problems since.Glad you got it working tho,K9copy is a great app.

Have you reported your problems to the SlackBuilds.org mailing list?

I have had few issues with build scripts from SlackBuilds.org. I'm unsure how this particular minor bug slipped through testing, but I'm not going to quibble. I've had good success with the scripts I use.

Responding as the original poster, no, I have not yet accomplished that. My computer time is limited to weekends and since discovering and posting the workaround/solution last weekend, this is the first opportunity to again sit at my computer.

On the other hand, I'm not fond of joining mailing lists, which I think is required to report SlackBuild.org bugs. I wish LQ provided a Slackware subforum for the SlackBuild community. That would be more convenient for people like me (centralized location) who are limited in the time they can participate in Slackware activities and the community.

Update: bug reported.

You have lidvdnav and or libdvdread, libdvdnav overwrites libdvdread's headers. k9copy needs libdvdread, uninstall both libdvdnav and libdvdread and reinstall libdvdread. k9copy will then compile ok. Now libdvdnav does have a bug in the headers that needs looking into, but the packages still conflict.

Hi,

Just a quick word in defence of slackbuilds.org:

If there is a problem with any of the scripts a simple email to slackbuilds or the maintainer of the script will almost always result in the script being rapidly pulled into line. Which particular scripts gave you trouble?

Andrew

That's interesting. I just looked at the archives of our mailing list, my own mailbox, and I've talked to most of the other admins. We have ZERO unresolved issues of which we're aware (well, counting this one, we have ONE).

We know full well that mistakes happen and that we're not perfect, but if you don't bother to LET US KNOW when you have problems, the problem won't be fixed.

This is going to come across as a rant, but quite frankly, statments like "I had problems with $something but I switched to $something_else and now everything is wonderful" just piss me off. You're going to have problems with *everything* sooner or later, and guess what? That's OKAY. Users have problems with Slackware every day - there are bugs in it. There will be an update to -current pretty soon with a few more bug fixes. That doesn't mean Slackware is bad.
If you see a *pattern* of problems with $something, THEN you can make statments like the above and not seem like an asshat.

Well, I approved libdvdnav, so for whatever reason, it built fine here. We were aware of the potential conflict of libdvdread|libdvdnav, and it was noted in the README, but as any Debian maintainer will tell you, it's damn near impossible to predict how the interactions will progress among any two given packages.

Subscribing to the list is not required to send mail to it. However, if you are not subscribed, be sure to note that in the mail and request CC on replies; otherwise you might not see the replies.

I won't speak for the entire team, but I don't see it as necessary. We maintain our own support "forum" in the form of a mailing list, and I don't intend to change that. Having to monitor yet another forum (and deal with what would almost certainly be lots of duplicate reports) is not high on my list of things to experience. Just as you (and many other users) are limited in the time you can participate, the same applies for us.

Thanks; we're on it.