Tim, thanks for your suggestion. I made a new build for make 4.3, copied it
over to /usr/bin, then problem resolved. Many thanks again. Kevin
Sent from my iPad
> On Nov 29, 2020, at 11:04 PM, Tim Tassonis wrote:
>
>
>
>> On 11/30/20 6:02 AM, Kevin Liu wrote:
>> Dear Sir/Madam,
>> 1.
On 11/30/20 6:02 AM, Kevin Liu wrote:
Dear Sir/Madam,
1. compiling LFS version 10.0, chapter 5.5, glibc-2.32
2. too old : make error running ../configure, see below
checking for python3... python3
checking version of python3... 3.6.8, ok
configure: error:
*** These critical programs are
On 2020-01-14 16:08 -0700,Alan Feuerbacher wrote:
> On 1/14/2020 7:39 AM, Xi Ruoyao wrote:
> > On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:
> > > I'm building the LFS systemd development version, and having some
> > > difficulty deciding how to configure some UEFI things.
> > >
> > > I'm
On 1/14/2020 7:39 AM, Xi Ruoyao wrote:
On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:
I'm building the LFS systemd development version, and having some
difficulty deciding how to configure some UEFI things.
I'm using GPT partitions and LVM (Logical Volume Management).
Using LVM for root
On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:
> I'm building the LFS systemd development version, and having some
> difficulty deciding how to configure some UEFI things.
>
> I'm using GPT partitions and LVM (Logical Volume Management).
Using LVM for root FS would require an initramfs:
HI,
If you use an external support (i.e USB ) you can try to add on the linux line
: rootdelay=10 (or more). Some devices are slow during boot.
> Le 28 nov. 2018 à 21:56, thomas a écrit :
>
> Am 2018-11-28 19:57, schrieb Jimmy Zhang:
>> Hi,
>> I followed the instruction on LFS-BOOK-8.3.pdf
Am Samstag, den 01.12.2018, 03:20 + schrieb Jimmy Zhang:
>
>
> On Wednesday, November 28, 2018, 8:15:30 PM EST, renodr
> wrote:
>
>
> On 2018-11-28 14:56, thomas wrote:
> > Am 2018-11-28 19:57, schrieb Jimmy Zhang:
> >> Hi,
> >> I followed the instruction on LFS-BOOK-8.3.pdf step by step
On Wednesday, November 28, 2018, 8:15:30 PM EST, renodr
wrote:
On 2018-11-28 14:56, thomas wrote:
> Am 2018-11-28 19:57, schrieb Jimmy Zhang:
>> Hi,
>> I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
>> end.
>> During the reboot, I got the error message "Kernel
On 11/28/18 10:11 PM, Ken Moffat wrote:
On Wed, Nov 28, 2018 at 07:15:14PM -0600, renodr wrote:
Look for Fusion MPT support and build all of that, as well as the VMWare
VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, and
PVSCSI support. You might need the VMXNET3 driver
On Thu, Nov 29, 2018 at 03:16:41PM -0700, JD wrote:
> I have run fbsd kernels that support Large File System on multiple PC
> platforms with
> cpus from Intel and AMD, without any problems with missing Hardware
> dependencies.
>
> So, my response was to BRUCE who brought up missing driver
>
I have run fbsd kernels that support Large File System on multiple PC
platforms with
cpus from Intel and AMD, without any problems with missing Hardware
dependencies.
So, my response was to BRUCE who brought up missing driver
issue to the OP.
I have never run into any missing driver issues on
On Thu, Nov 29, 2018 at 02:47:38PM -0700, JD wrote:
>
> On 11/29/2018 02:41 PM, Douglas R. Reno wrote:
> >
> > On 11/29/18 3:37 PM, JD wrote:
> > >
> > > On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
> > > >
> > > > 1. LFS got on to the hard drive using the host's drivers.
> > > >
> > > > 2. The
On Thu, Nov 29, 2018 at 01:49:49PM -0700, JD wrote:
Please do not top-post.
> 1. If the kernel does not have the required driver,
> how did LFS end up on the drive?
As Bruce has already answered.
> 2. Just exactly what driver are you referring to?
> "Driver" is a generic term which is used
On 11/29/2018 02:41 PM, Douglas R. Reno wrote:
On 11/29/18 3:37 PM, JD wrote:
On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
On 11/29/2018 02:49 PM, JD wrote:
1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring
On 11/29/18 3:37 PM, JD wrote:
On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
On 11/29/2018 02:49 PM, JD wrote:
1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
"Driver" is a generic term which is used to
On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
On 11/29/2018 02:49 PM, JD wrote:
1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
"Driver" is a generic term which is used to to refer to different
interfaces
On 11/29/2018 02:49 PM, JD wrote:
1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
"Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that to say
1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
"Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that to say "re-install" is a strange piece of advice.
On Thu, Nov 29, 2018 at 11:27:11AM -0700, JD wrote:
>
>
> On 11/29/2018 11:00 AM, Xi Ruoyao wrote:
> > On 2018-11-29 15:17 +, Jimmy Zhang wrote:
> > > Hi,
> > > One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3
> > > from my partition(one partition for both
> > >
On 11/29/2018 11:00 AM, Xi Ruoyao wrote:
On 2018-11-29 15:17 +, Jimmy Zhang wrote:
Hi,
One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3 from
my partition(one partition for both
/boot and /) was loaded and run, which indicated that the system can access my
On 2018-11-29 15:17 +, Jimmy Zhang wrote:
>
> Hi,
> One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3
> from my partition(one partition for both
> /boot and /) was loaded and run, which indicated that the system can access
> my partition /dev/sda3 which was going
>
Hi,One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3
from my partition(one partition for both /boot and /) was loaded and run, which
indicated that the system can access my partition /dev/sda3 which was going to
be mounted as root, right? why the kernel will give the
On Wed, Nov 28, 2018 at 07:15:14PM -0600, renodr wrote:
>
> Look for Fusion MPT support and build all of that, as well as the VMWare
> VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, and
> PVSCSI support. You might need the VMXNET3 driver as well.
since so many people seem
On 2018-11-28 14:56, thomas wrote:
Am 2018-11-28 19:57, schrieb Jimmy Zhang:
Hi,
I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
end.
During the reboot, I got the error message "Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
I was building
Am 2018-11-28 19:57, schrieb Jimmy Zhang:
Hi,
I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
end.
During the reboot, I got the error message "Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
I was building LFS with my VMware machine.
Need help
Apologies for creating any sort of confusion.
My machine has x86_64 architecture. Earlier I was not sure of, it but now
I'm.
On Oct 29, 2016 11:53 PM, "Ken Moffat" wrote:
> On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> > Hey William,
> >
> > Thanks
On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> Hey William,
>
> Thanks for response.
>
> After hours of research I could figure out the significance of 139 but I
> still need to interpret the reason.
>
> And, as far as I know, my machine doesn't support x86_64 architecture.
>
On Sat, 29 Oct 2016 20:07:44 +0530
Aditya Dixit wrote:
> So what should I do regarding the architecture (if there is any, if my
> machine doesn't support x86_64 architecture)??
You would want to build for x86 and not x86_64.
Run "uname -m" to be certain of your host
Hey William,
Thanks for response.
After hours of research I could figure out the significance of 139 but I
still need to interpret the reason.
And, as far as I know, my machine doesn't support x86_64 architecture.
So what should I do regarding the architecture (if there is any, if my
machine
Hey Ken,
Thank you for your timely reply.
I tried compiling the a small hello world program in my lfs
environment with x86...gnu-gcc compiler. It did produce an "a.out" but
when I tried to execute it, it again gave a segmentation fault.
Another observation of mine is that - we usually have a
On Sat, Oct 29, 2016 at 08:58:46AM +0530, Aditya Dixit wrote:
> Please help me in fixing this issue. I'm following v.7.10 of
> LinuxFromScratch on Fedora 64-bit device.
>
> The problem is:
>
> configure:4496: checking whether the C compiler works
> configure:4505: ./a.out
>
31 matches
Mail list logo