On 6 April 2010 20:47, lux-integ wrote:
> PROBLEM B:
>
> On starting X with the instruction
> X -retro -config ~/xorg.confXXX (
> http://www.linuxfromscratch.org/blfs/view/cvs/x/x-setup.html)
> the Control+Alt+Backspace does not work. I could not find a way to stop X
> save crashing the s
On 6 April 2010 20:31, wrote:
> On 04/06/2010 10:55 AM, Ken Moffat wrote:
>>
>> However, like *many* packages with updated configure scripts, the old
>> --disable options no longer work. If you look at configure --help you will
>> see that the dri option is now --enable-dri=no. The glx option
On 6 April 2010 19:28, wrote:
> Hi when i test my libtool-2.2.6b i get 2 unexpected failures:
>
> 37: localized compiler messages FAILED
> (localization.at:50)
> 74: Run tests with low max_cmd_len FAILED
> (cmdline_wrap.at:43)
>
> Are these considered crit
Kaleb Hosie wrote:
> I'm really stumped right now and I could use some help.
>
> I've finished compiling the Kernel for my first LFS deployment
[...]
> VFS: Cannot open root device "sda1" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
>
> This rings a bell with me. I think these are messages from
> udev that would normally
> be output to /dev/null but if /dev/null doesn't exist, udev
> prints them to stdout.
> Udev tries to load modules for things but if they're built
> into the kernel (or you
> don't need them) then the FATAL mes
Hi when i test my libtool-2.2.6b i get 2 unexpected failures:
37: localized compiler messages FAILED
(localization.at:50)
74: Run tests with low max_cmd_len FAILED
(cmdline_wrap.at:43)
Are these considered critical, or can i just keep going?
If they are
Hi All,
> > It would seem that your Makefile is significantly different from mine.
> > That would indicate to me that there is something wrong with your
> > Chapter 5 build as once you get into chroot, the builds really should be
> > the same.
>
>
Maybe you are right, but if you do, the failure i
