On 01/25/2013 01:35 PM, Randy McMurchy wrote: > Armin K. wrote these words on 01/25/13 06:22 CST: >> Sure, that's okay with me. Now I noticed, as I said in the other mail, >> that --enable-cups is required to enable CUPS backend. And it does not >> use the CUPS at build time, but backend is practicaly useless without >> CUPS at runtime ... > > I agree. It is about the only package that builds something for another > package > without it being installed. It is strange. But if you look at the book, I > think > the instructions I made for it make sense. Don't you? > >
Right, But at least it should me mentioned that it's installed in --enable-cups explanation. > > I build from a very, very old version of Hummingbird X-Windows server on an > old Windows XP machine using ssh to the host machine. It works for almost > everything. However, it is not GL enabled. So for some tests, I actually use > X on my host machine where it is GL enabled. I will try that for these tests. > This is why you see "you must perform the tests from a GL enabled host or some > tests will fail" in some package instructions. This is how I find that out. > Ah, that rings the bell. I think that you need to run it from local X session with D-Bus daemon running (not sure if system or session daemon though). >>>> I've always wanted to ask for this one. >>>> >>>> Can't we just stop explaining --whateverdir=/path/to/whatever switches? >>>> I mean, it should be obvious that it is setting installation paths for, >>>> lets say, docs, executable, whatever. >>> I agree But if they are already in the book, what is the harm in keeping >>> them? >>> >> >> There is no harm, but I guess we can stop doing that in the future (for >> new packages, etc), if you agree. > > You bet. docdir, libexecdir, sysconfdir, all of these types of things really > do not need to be explained unless it is some bizarre location being set. But > that doesn't happen very often. > Agreed. -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
