<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Greetings,<br><br>> Date: Mon, 1 Sep 2008 12:19:50 -0400<br>> From: jciccone<br>> <br>> Subject: Re: [Clfs-dev] CLFS 1.1.0-rc2<br>> <br>> db m wrote:<br>> > I was going to say I completed a build of rc1 in x86-64_multilib guise via<br>> > chroot over the weekend without any apparent hiccups, but seeing this<br>> > posting, I've got time to do it again and pay a bit more attention viz<br>> > ticket-169....<br>><br>jciccone> The build command still havn't changed, and most likely wont. 169 just<br>jciccone> has todo with some text changes.<br>><br>> > On the side, I've been building against CLFS SVN-20080714 in the same<br>> > guise, following the CBLFS wiki -- this is pretty close to what 1.1.0<br>> > is going<br>> > to be. So far (322 packages) and the travel has been really good with<br>> > this base set. That said, 1.1.0 will break -some- parts of the CBLFS<br>> > pages,<br>> > but I'm loath to do any editing there before 1.1.0 rolls out...<br>><br>jciccone> I should probably re-work the development version of Xorg in CBLFS as<br>jciccone> well. It's been a month or two and quite a bit has changed.<br>><br>> > Perhaps OT here...but can one leave oneself notes on the 'my talk' pages<br>> > of the CBLFS wiki ...?...<br>><br>jciccone> Sure, we just wanted to leave stuff off the packages talk pages. The<br>jciccone> better place to report errors is on this mailing list or in the IRC<br>jciccone> channel. The talk pages were forgotten about and errors would sit there<br>jciccone> for a month or so before someone noticed. There's just too many pages to<br>jciccone> watch all the talk pages.<br>><br>><br><br>Ahh, okay.....I wasn't absolutely sure CBLFS stuff was fodder for in here - being<br>on the other side of the lower half of the planet, IRC somehow doesn't quite<br>cut it (everyone asleep when I'm awake and vice-versa ;)...<br><br>I'm going to agree with you about an Xorg re-work.....most of that I did using the<br>semi-automated build scripts where possible, which seem to complete okay.<br>Later on though, a couple of curious things happen....(multilib build)<br><br>1> The command 'Xorg -configure' refused to work for me, claiming to be unable<br>to find it's libs (drivers, modules, etc). Strangely, issuing 'Xorg' (without the <br>-configure switch) -did- work, so I basically just copied across my old xorg.conf<br>and went from there. It left me thinking something in the '-configure' switch was <br>hard-coded in regards path to xorg_libs.....<br><br>2> Later....I think qt3 first tossed this up, but a few other packages did too....there's<br>some confusion with Xmd.h when building 32bit stuffs. Xmd.h defines 'CARD32' as<br>being 'typedef long unsigned int', however a couple of parts of qt3 (& others) have <br>'CARD32' slated as being 'typedef unsigned int' .... which will of course cause a <br>compilation error. I haven't worked out if this is xorg's fault or not yet....(so far my<br>resolve has been to manually edit those few offending headers to agree with Xmd.h's <br>view of the world...)....(which is probably not a correct thing to do)...<br><br> As said though, perhaps the priority is to first get 1.1.0 out there and fix CBLFS issues<br>beyond that juncture..and with that, I head off to build rc2....<br><br>Regards,<br><br>Don<br><br><br><br><br><br><br><br /><hr />Find great deals on eBay <a href='http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Frover%2Eebay%2Ecom%2Frover%2F1%2F705%2D10129%2D5668%2D323%2F4%3Fid%3D10&_t=763807330&_r=hotmailTAGLINES&_m=EXT' target='_new'>Net yourself a bargain</a></body>
</html>