On Mon, Apr 15, 2013 at 07:30:06AM -0400, LM wrote: > On Sun, Apr 14, 2013 at 2:00 AM, Ken wrote: > > Announcing the latest in a long and boring series of documents > > listing what I'm currently building on my desktops, and in what order. > > This one is at > >http://www.linuxfromscratch.org/~ken/desktop-builds/desktop-build-april-2013.txt > > and is for LFS-7.3. Hopefully I'll get started on LFS-svn with > > gcc-4.8 real soon now. > > Actually I thought the list was quite interesting and pretty impressive. > Thanks. > > As always, I'm willing to answer questions about those packages I do > build. > > Would be very curious as to approximately how long it takes to complete the > build of everything from start to finish on your system. >
On this current machine (Intel i3-2120, 3.9-rc kernels with the new cpufreq driver) the most recent build was just a shakedown run to make sure that everything still held together. I'd built a few things in the previous run, then decided that I probably didn't need them if I changed certain configure options. LFS itself took about 3 hours. Normally I build most things with make -j3 (to give me some CPU for ssh, browsing or whatever, and my backup runs), but on this occasion I forgot to set the environment variable when I entered chroot, so that part was -j1. Only the toolchain tests on this run. Everything after that took about 6 hours 20 min. I mentioned the cpufreq driver because it is a lot faster than the acpi driver. > > Replaced jpegsrc with libjpeg-turbo. For x86_64 this can use yasm > >(x86_32 needs nasm), so I've moved that forward in my build. > > Am also curious if you notice any differences between jpegsrc and > libjpeg-turbo and if there are any programs that may build with one that > won't build with the other. > The only issue I've seen was on upgraded systems - I found one error in my scripts which caused the .so.8 symlink (I think) to link to the old version. Oddly, a recent upgrade of something triggered that again, for reasons I don't understand. The symptom is that firefox doesn't display a lot of images on some web pages. So far, everything I use has built without any problems. I can see that the turbo version won't work on (some) other architectures, and perhaps it won't be useful on very old x86 CPUs. > >Dropped openjpeg - I very much doubt that anything I ever see > > uses it. From memory, the current version requires cmake - I wasn't > > willing to build that. I might change my mind about cmake - I still > > loathe the way it reinvents the wheel, but I've now found some > > documentation of the many -DCMAKE_FUBAR variables) at > > I use openjpeg with mupdf (an extremely fast, lightweight pdf viewer). > Seems like a nuisance openjpeg dropped support to build using standard gnu > autotools and switched only to using cmake. Other projects (like sdl) > support multiple build methods. Don't know if it's good or bad news, but > I've seen some bug listings that the latest version of mupdf doesn't work > with the latest version of openjpeg anyway. I'm thinking of continuing to > use an earlier version of openjpeg that doesn't require cmake for as long > as I can. Would be nice if mupdf could use a different jpeg library > besides openjpeg. Also, since they include the source for openjpeg with > mupdf, there's always the possibility of forking openjpeg and creating a > version specifically for mupdf. Was hoping to run across some more news on > this topic, but haven't heard anything useful yet. > > When I have time to rebuild xine on my machine, I'm very curious about the > issue you ran into. Hope to at least take a look at it. At least you > found a work-around even if it doesn't make sense. On the xine-devel list there have been two replies so far - there _is_ a logical explanation (.png files aren't like movies as far as the status is concerned), and a better patch [ mine might break one use case ]. I'm waiting to see what develops. > > Sincerely, > Laura ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
