I don't believe slackware has a build-everything-static mode. Every package (if correctly built) includes a script responsible for building said package (it compiles and packages all files that result from compilation). This script is called a "SlackBuild".
The point is: we actually have to modify some SlackBuild scripts (like the vlc.SlackBuild) to force a static-build when that is desirable. Anyway, although ocfs2-tools now compiles with no errors (thanks to the precious help from Sunil Mushran) but only after manually editing o2image's Makefile to accept the -lpthread flag (as per Sunil's suggestion) I do appreciate that you took the time to explain what was probably wrong to begin with. I'm sure that with your help we'll be able to come up with a working ocfs2 setup on slackware :) One other thing: the --libdir flag was not respected and some python files ended up in the wrong directory, making the console fail. I fixed that by manually copying the files to their proper place, but console still does not work :( I have not tried a "command line only" setup because I really want the to fix the issue with the console first. ----- Mensagem Original ----- De: Joel Becker <joel.bec...@oracle.com> Para: pica pica <pica6...@aeiou.pt> Cc: Sunil Mushran <sunil.mush...@oracle.com>, ocfs2-users@oss.oracle.com Enviado: Thu, 2 Dec 2010 05:18:31 +0000 (WET) Assunto: Re: [Ocfs2-users] Compiling ocfs2-tools-1.6.3 on slackware64-13.1 >Does Slackware have a build-everything-static mode? The compile >line does not have -static, so I'm guessing it is in your toolchain. --------------------------------------------------- Venha conhecer o novo AEIOU: http://www.aeiou.pt _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
