I've managed to compile TinyX on my Gentoo system. I would like to make an ebuild, but I am quite inexperienced at this. I tried copying the XFree86 ebuild and modify as much as I understood. If you are interested in trying this, then here are the simplest instructions that I can think of to get it compiled: 1.) uncompress X420src-1.tgz and other sources 2.) cat this into .../xc/config/cf/host.def #define KDriveXServer YES #define TinyXServer YES #define XvesaServer YES #define ProjectRoot /usr/X11R6 #define BuildLBX YES #define BuildDBE YES #define KdriveServerExtraDefines -DPIXPRIV #define BuildRandR YES #define BuildXInputLib YES #define Freetype2Dir $(TOP)/extras/freetype2 #define Freetype2LibDir $(TOP)/exports/lib #define BuildXTrueType YES #define BuildScreenSaverExt YES #define BuildScreenSaverLibrary YES #define SharedLibXss YES #define ServerXdmcpDefines #define XfbdevServer YES 3.) cd .../xc 4.) make World I don't know about the rest, but it should be similar to a regular XFree86 install. There are probably other better tweaks too. Sincerely, & with thanks, Eugene T.S. Wong
Hi. All of the following might be obvious to you guys, but just in case I might be able to save you a few moments, I'd like to share with you what I've found. I tried again without much success, but I may have stumbled on to something. I tried manually uncompressing X420src-1.tgz in /var/tmp/portage/tinyx-4.2.1-r2/work, then going into /usr/portage/x11-base/tinyx-4.2.1-r2 then executing, "ebuild tinyx-4.2.1-r2.ebuild compile". The idea was to test whether or not there was anything wrong with the unpacking process. Not surprisingly, I still ran into problems. So, since there are the same errors, I suspect that all problems are in the compile stage. I looked through /usr/lib/portage/bin/emake and I noticed that the script adds parameters. Would anybody know how to figure out whether or not certain parameters are causing the problem?
Okay, I think that I did it. The problem seemed to be the fact that the unpacking done by ebuild would take a .../site.def & use that as the base for host.def. That doesn't work well for TinyX. I discovered this when I tried manually uncompressing X420src-1.tgz in the working portage directory. I then manually constructed the appropriate host.def file using the site.def file as a base. Of course I found the same errors. So, I then tried recreating the host.def file without the site.def file, and this time the only thing I added was "#define BuildFonts NO". The manual compile went fine. I don't know if there were any errors, though. It all looked okay when I turned on the monitor this morning. Next I tried modifying the tinyx-?.?.?-r2.ebuild file, removing the line that would use site.def as a base. Again, this worked fine. I noticed some errors scrolling by, as if there were scripting errors, but it seems to have installed fine. To complete the install, even though it was installed with emerge, I had to do: cd /usr/X11R6/bin chmod a+s Xvesa rm -f X ln -s Xvesa X I'm sure that there are better ways to do the things that I did, & I'm sure that there are still some errors. I noticed that dragging a window seems to be a bit more slower with TinyX. It also seems to take longer to load up the Opera web browser. It could be all my imagination. I think that this is ready to be put in the portage tree, but as masked. I don't understand the entire process, so I can't say for sure. I'm just trying to suggest & help. What does everybody think?
