Keith:
The first ln command that Bruce provided you, works just fine if
you're under the /bin directory.
Then he corrected himself by giving you a flawless command which
works, no matter where you stand on your file system.
The intention of the list is to help users with LFS, not to prove
their ex
Martins,
> I guess I would use dmesg -n1 right
> after logging in, or better yet include it in ..bash_rc or .bash_profile.,
> correct?
I could better set the variable LOGLEVEL="1" in the file
/etc/sysconfig/console or in /etc/sysconfig/rc.site which has the same
effect as dmesg -n1.
About the er
Martins,
Maybe you could try to disable EHCI.
By the way, I forgot to tell you. You could stop all those kernel messages with:
dmesg -n1
or:
echo 1 > /proc/sys/kernel/printk
or in LFS you can make this permanent by seting LOGLEVEL="1" in the
file /etc/sysconfig/console or in /etc/sysconfig/rc.sit
Hello Martins,
It seems like a speed problem:
[ 186.450841] ehci_hcd :00:1d.7: GetStatus port:2 status 001403 0
ACK POWER sig=k CSC CONNECT
[ 186.450854] hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
...
[ 186.605119] hub 2-0:1.0: port 2, status 0301, change 0001, 1.5 Mb/s
[ 186.
Hello everyone.
I've built LFS many times before. Just one time I used a package
manager, called paco [1], described in the LFS hints. It worked ok.
But now I'm trying with the Package Users technique [2]. I'm using LFS
Book 7.0, and now I just finished with the phase 6.10. Re-adjusting
the Toolcha
> checking for gmp.h... no
> configure: error: gmp.h can't be found, or is unusable.
> make[1]: *** [configure-mpfr] Error 1
> make[1]: Leaving directory `/media/lfs/build/gcc-4.5.2'
> make: *** [all] Error 2
>
> What this means?
Looks like you're missing gmp. Di
2011/7/25 Bill Cunningham
>
> http://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html
>
> This case 'uname -m' and so on text is not working for me. Where should
> this configparams file be created. It's not being created anywhere for me.
>
> Bill
According to the book, the file s
Seems like makeinfo from package texinfo is missing. Did you forget
that package?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Yes, you can always omit the tests. They are there to ensure that the
build and functioning was right but you can do it yourself.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
>From the LFS Book:
Groff expects the environment variable PAGE to contain the default
paper size. For users in the United States, PAGE=letter is
appropriate. Elsewhere, PAGE=A4 may be more suitable. While the
default paper size is configured during compilation, it can be
overridden later by echoin
I also had an idea some time ago somehow related to what you are
saying. I used to compile the kernel several times with different
configurations, so every time I compile it, I wanted to know how long
will it take beforehand. So I think about compiling a small program as
a reference, and then use t
You can compile multiple programs at the same time, keeping in mind
that those programs should not depend on each other. And also if your
computer is tough enough for the task.
Cheers.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Un
2009/8/4, Juan Alberto Regalado Galván <00j...@gmail.com>:
> 2009/5/14, Juan Alberto Regalado Galván <00j...@gmail.com>:
>
>> problem so I just ignored them. I'll try to see what they are all
>> about. I'll compile the kernel again and I'll bring the
I compile it without modules before asking for help. About the errors,
two appear, but they don't seem to have something to do with my
problem so I just ignored them. I'll try to see what they are all
about. I'll compile the kernel again and I'll bring the errorlog here.
Thanks.
---
JARG
--
La
Both. When it starts booting, it mount the root partition, an other
things that are done at bootup, etc. And then at some point it just
say "Error Initializing control socket" and stops there, and there's
nothing I can do but reboot with the SysRq key.
I find a temporal solution to this, that was c
Sorry It was "Error initializing control socket"
2009/5/12, Juan Alberto Regalado Galván <00j...@gmail.com>:
> Hi, I just build my LFS system with the LFS-6.4 book. And I get the
> error mesasage "Error initializing device socket" at bootup, I check
> the FAQ a
Hi, I just build my LFS system with the LFS-6.4 book. And I get the
error mesasage "Error initializing device socket" at bootup, I check
the FAQ and the mailing list but I could not find the answer there so
I'm asking here. If these is not correct place to do this please
excuse me.
--
http://linux
17 matches
Mail list logo