>One other thing I have tried using the commands found in the online handbook
>for building a single package and when I issue the command I >get
Please try following command to compile a single package and starting from
stage 5 (assumed that xorg-server went through previous stages while T2 was
preparing the chrooted toolchain environment. Usuallly compilation fails at
stage 5):
./scripts/Build-Target -cfg myConfigName -job-5-xorg-server
Various other commands I often find useful
Download all required packages for the specified configuration:
./scripts/Download -cfg myConfigName -required
Cleanup failed src.xxxx folders from the T2 source tree:
./scripts/Cleanup
Cleanup obsolete downloaded packages to save disk space (ie. older tar.bz2
versions not used by T2 package definitions anymore):
./script/Cleanup -download
Try to build manually failed package (after trying some patch fix or manual
source code fix):
cd src.mypackagename-targetname-xxxxxxx (ie. the folder T2 created on the
T2 root dir)
./debug.sh
eval $MAKE $makeopt
Temporarly override the default T2 package definition file to try to compile
different version of pkg source codes (ie. newer version from the original home
website not used by T2, yet):
- Create a new "t2/targets/mytargetName/packages/" folder
- Create fex "xterm" folder below the new packages folder (ie. to override
xterm default package definitions)
- Copy the original "t2/packages/*/xterm/xterm.desc" file to
"t2/targets/mytargetname/packages/xterm" folder
- Modify the copied "xterm.desc" file and remove everything else but lines
starting with [V] and [D] tags
- Modify [V] line and enter a new version tag. For example "[V] 300"
- Modify [D] line as follows to instruct T2 to download different source
tarball than the default desc file (X tag skips package check-sum checking
because the new tarball naturally has different checksum. There handy T2
commands to update these checksums if you use different tarballs but it is not
necessary while testing new packages)
[D] X xterm-300.tgz ftp://invisible-island.net/xterm/
- Run configurator just in case (not sure if this is required):
./scripts/Configure -cfg myconfigname
- Force T2 to download the new source tarball: ./scripts/Download -cfg
myconfigname -required
- Re-compile the overriden package: ./scripts/Build-Target -cfg myconfigname
-job-5-xterm
The idea behind removing everything else but V and D lines is to re-use
everything else from the original desc file and just to override V and D lines.
Of course you can override other lines too if necessary.
-Mika
>From: Robert Holmes <grumpywolfe <at> gmail.com>
>Subject: Xorg
>One other thing I have tried using the commands found in the online handbook
>for building a single package and when I issue the command I get
># ./scripts/Emerge-Pkg xorg-server-1.9.4.tar.bz2
> xorg-server-1.9.4.tar.bz2 checking ... Error: No such package.
>0 packages scheduled to build.
>I do know that the package is downloaded and the build-target finds it just
>fine but cant build any file by its self.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
