On 13.02.2010, at 11:28, Makis Tsimaras wrote: > Hello. > > I tried a few times to fix broken packages by following the documentation. > > I did the "cd src.packagename.uniqu-id --> ./debug.sh --> cd > some_pkg_$ver --> eval $MAKE --> $makeopt" as the documentation says,.. > and the result is the output of the build process of the package until it > reaches the error and stops. > > What can i do after that? > What is the next step? > > I don't really understand the fixfile and fixfilediff also, how can i use > them? > > > Any help is welcome and it will help others too.
fixfile is only a wrapper to make a backup of the file to edit, and fixfilediff is a wrapper to diff all such editied files. How to "fix" a package depends on the actual issue, bug, new compiler warnings or errors as usually in the upstream package source. Common, easy examples are: adding a missing #include <> directive, adding some cast for new GCC C++ nitpicking, or changing some API calls to match new X.org, Gtk+, etc. issues. But this really is usually regular C programming topic. René -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin http://exactcode.com | http://t2-project.org | http://rene.rebe.name
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
