Hi jolupa, On Sat, Jul 09, 2005 at 01:46:26 +0200, jolupa wrote:

Hi. Today i was trying to make some pacakges i need, but it was impossible due to the lack of imformation that comes with the program. I thing that all the people that are making packages and installing software from source are sad 'cause a few programmers especify all the dependencies required for this or that program to build I'm not sure if I understand you correctly, but from your e-mail, I believe that you couldn't build the software at all. If you could build it, but don't know what to put into the Pkgfile's dependency header, you can use the "finddeps" script from contrib/prt-utils.

Most packages I've build so far contained this information either in the tarball, or on a webpage. Also, sending a friendly inquiry to the author usually helps to resolve the open questions. Most open source developers are happy to hear from their users, and to resolve issues; also note that they are giving you this for free, so they have no obligation to provide any kind of support; being rude never helps, especially if the other party works for free. Otherwise, the solution I'd suggest is to look at the error message you get. Missing dependencies usually show at three stages: 1) configuration time Those are really easy, since it'll say "Couldn't find libXY". I assume this isn't the case here. 2) Compile time; missing include During compilation, missing dependencies usually cause compilation errors since an include file was missing. The problem here is that compilation will continue a bit, and you may see other error messages after that, much like this: http://mythtv.org/pipermail/mythtv-dev/2002-August/000211.html The final errors here are about undeclared functions all starting with lame_, which suggest that the lame headers are missing (this is not always that obvious). Scrolling up a bit confirms this: "NuppelVideoPlayer.h:11:23: lame/lame.h: No such file or directory" Sometimes, the missing header file is not in the ports tree, in this case you'll have to use google to find the package providing it, and build an additional port for it. 3) Linking errors Linking errors occur after a program's compilation, and can be really tricky to find since they are often caused by the configuration system. Easier error here are if a dependency put its libraries somewhere not in ld.so.conf, in which case ld won't find it. For this case, it's almost impossible to you an easy way how to solve that. Finally, if you don't succeed after that, I'd suggest to search google for similar problem, since understanding the compilation process of packages is a rather important thing to build good packages. If you don't manage to build a package for this particular software package on your own yet, you can always include a complete build log (compilation output) in a file and put it on your web page. Then, someone from the CRUX community might have a look (also note that most crux users don't read clc-contrib, so the crux mailing list is certainly better for general questions related to packaging). So, good luck! :-) Hope this helps, Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net