<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div>What about just adding some tests to properly move the scripts to their sane names. Try it, then just add it to the book when it's perfected (multilib only).<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: db m <myheadblewoff@hotmail.com><br>To: clfs-dev@lists.cross-lfs.org<br>Sent: Thursday, September 18, 2008 12:26:13 AM<br>Subject: [Clfs-dev] CBLFS -- Xorg7/Libraries<br><br>
<style>
.hmmessage P
{
margin:0px;padding:0px;}
body.hmmessage
{
FONT-SIZE:10pt;FONT-FAMILY:Tahoma;}
</style>
Greets,<br><br>A couple of notes here (relative to clfs-1.1.0-rc2 x86_64 multilib)<br><br><font size="3"><span class="mw-headline">Semi-Automated Build</span></font>;<br><br>----<br><br>text reads;<br><br>"You must also have an unaltered copy of Lib-20080914.wget in the main working directory (xc). "<br><br>Most of us will probably know that '(xc)' is actually referring to 'xorg-20080914'. Those who do<br>not may become confused by this...<br><br>----<br><br>The semi-automated build script in no way takes into account the situation regarding libxft and<br>xft-config. If one chooses to use this semi-automated approach, you will end up with a single<br>'/usr/bin/xft-config' installed, and it will be the 64bit version of same. I am unsure what possible<br>ramifications this may give rise to later in the book....<br><br>I do realize 'semi-automated' means that....ie; some manual intervention will/may be required,<br>however that situation
might not be immediately obvious to first-time CBLFS exponents. Lets<br>face it, having to do all this manually can be rather tedious and repetitive, and as such the<br>semi-automated scripting will appeal to many folks...and save a good bit of time.<br><br>As such, one can utilize the semi-automated build scripts here, however in the case of a <br>multilib build, I'm supposing people should 'rm /usr/bin/xft-config' and then unpack/rebuild<br>libxft again following the manual build instructions so everything is 'as expected'.<br><br><br>Regards,<br><br>Don<br><br><br><hr>Enter today! <a rel="nofollow" target="_blank" href="http://www.livelife.ninemsn.com.au/compIntro.aspx?compId=4602">Win a Hotmail Go-Kart to race at Bathurst.</a></div></div></div><br>
</body></html>