[lfs-support] sh: -I.: command not found while build openssl-1.1.1b?

[Pei Jia]

Hi, all:


Sorry to bother you again. Although I succeeded to build the basic lfs 
onto a USB stick, now I'm trying to redo everything from scratch onto a 
SD card... However, I failed to build openssl-1.1.1b this time. 
http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/openssl.html .



/(blfs chroot) root:/sources/openssl-1.1.1b# ./config 
--prefix=/usr \//

//>  --openssldir=/etc/ssl \//
//>  --libdir=lib  \//
//>  shared    \//
//>  zlib-dynamic  \//
//>  --verbose//
//Operating system: x86_64-whatever-linux2//
//Configuring OpenSSL version 1.1.1b (0x1010102fL) for linux-x86_64//
//Using os-specific seed configuration//
//Creating configdata.pm//
//Creating Makefile//
/*/sh: -I.: command not found/*


As shown, *sh* has been successfully installed./
/

/
/

/(blfs chroot) root:/sources/openssl-1.1.1b# whereis sh//
//sh: /bin/sh /tools/bin/sh//
//(blfs chroot) root:/sources/openssl-1.1.1b# sh --version//
//GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu)//
//Copyright (C) 2019 Free Software Foundation, Inc.//
//License GPLv3+: GNU GPL version 3 or later 
//

//
//This is free software; you are free to change and redistribute it.//
//There is NO WARRANTY, to the extent permitted by law./
/(blfs chroot) root:/sources/openssl-1.1.1b# echo $PATH//
///bin:/usr/bin:/sbin:/usr/sbin:/tools/bin/


Seriously have NO idea where I did wrong...



Anyway, I now ignore openssl and move forward


Cheers

Pei



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Colorize

[Pei Jia]

Hi, all:


I noticed from 
http://www.linuxfromscratch.org/blfs/view/6.3/postlfs/logon.html 
that*/etc/issue* can display plain text. Just wonder if there is a way 
to colorize the characters ? If so, how?


BTW, is it possible to run a simple script and display customized and 
colorized ART characters, as done within PC terminal?



Cheers

Pei

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Building LFS on a usb drive

[Pei Jia]

On 2019-03-20 2:04 a.m., Pierre Labastie wrote:

On 20/03/2019 00:43, Bruce Dubbs wrote:

After a long thread on -support today I did a test build on a USB drive
today.  These are some observations.

The USB drive was /dev/sdg.   I only had one partition on the MSDOS style
partition table.

 From the host I installed GRUB with
   grub-install /dev/sdg

To boot, I needed a grub.cfg file:

# Begin /boot/grub/grub.cfg
set default=0
set timeout=5

insmod ext2
set root=(hd0,1)

menuentry "GNU/Linux, vmlinuz-5.0-lfs-SVN-20190305" {
     linux   /boot/vmlinuz-5.0-lfs-SVN-20190305 rootdelay=10 root=/dev/sdg1 
ro
}

When booting, I had to tell the system firmware (BIOS) to boot from the USB
drive.

In grub.cfg the line

    set root=(hd0,1)

refers to GRUB's view of the system where it thinks the boot drive is hd0.
This allows GRUB to find the kernel, load it and then start it.

The kernel, on the other hand, searches the entire system for hard drives and
identifies them as it finds them.  In my case I have six hard drives in the
system. sda, sdb, sdc, sdd, sde, and sdf.  The USB drive is thus identified as
sdg.  The linux boot line then requires

     root=/dev/sdg1 rootdelay=10

The rootdelay is needed so the system has time to find the USB drive, but
/dev/sdg1 is needed for the kernel to find the root partition.  The fstab file
also needs the same drive designations as the kernel command line.

If this USB drive is inserted into another system with a different disk
configuration, then these values will need to be changed.  The workaround is
to use UUID or PARTUUID designations.  PARTUUID is only available on GPT
partition tables [sic], but plain UUID requires an initrd to be created and
loaded by GRUB.


Good summary. I think one of the issues that occured is that the kernel on the
USB stick did not have all the drivers to be able to recognize all the drives
that the host had recognized (sorry for English, hope it is clear
nevertheless). So the host kernel was seeing the USB drive as /dev/sde, while
the lfs kernel could see it as /dev/sdd.

I had not thought of grub seeing the drive it sits on as hd0... That makes 
sense.

Pierre



I'd love to report some other *trivial* bugs while building LFS:


1. 
http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-libstdc++.html


../libstdc++-v3/configure \ --host=$LFS_TGT \ --prefix=/tools \ 
--disable-multilib \ --disable-nls \ --disable-libstdcxx-threads \ 
--disable-libstdcxx-pch \ 
--with-gxx-include-dir=/tools/$LFS_TGT/include/c++/8.3.0


should be

../configure   \
--host=$LFS_TGT \
--prefix=/tools \
--disable-multilib  \
--disable-nls   \
--disable-libstdcxx-threads \
--disable-libstdcxx-pch \
--with-gxx-include-dir=/tools/$LFS_TGT/include/c++/8.3.0



2. 
http://www.linuxfromscratch.org/lfs/view/development/chapter05/binutils-pass2.html


CC=$LFS_TGT-gcc \ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ ../configure 
\ --prefix=/tools \ --disable-nls \ --disable-werror \ 
--with-lib-path=/tools/lib \ --with-sysroot



better separate into two parts:


CC=$LFS_TGT-gcc \ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib

and

../configure \ --prefix=/tools \ --disable-nls \ --disable-werror \ 
--with-lib-path=/tools/lib \ --with-sysroot



Otherwise, I met some problem as 
https://www.linuxquestions.org/questions/linux-from-scratch-13/ch-5-9-binutils-pass-2-error-cannot-run-c-compiled-programs-807747/ 





To be confirmed 


Cheers

Pei


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Pierre and Bruce:


My bad... I tried */dev/sdd1*, and it's *working* :'(:'(

There are still some *errors*: https://longervision.cc/bugs/booting_bugs.jpg

And it's seriously basic, but it's already 1.1 Giga?

No command *adduser*, *addgroup*?

hmmm..


Any further suggestions? What's *NEXT*? *blfs*?


So far, I didn't use *systemd*, is *systemd* *preferred*?



Cheers

Pei



On 2019-03-19 2:32 p.m., Pei Jia wrote:



Hi, Bruce,


this is *already* my current *grub.cfg on USB stick*. All the bugs I 
posted are just with this *grub.cfg*:



/➜  grub cat grub.cfg //
//# Begin /boot/grub/grub.cfg//
//set default=0//
//set timeout=5//
//
//insmod part_msdos//
//insmod ext2//
//set root=(hd0,msdos1)//
//
//menuentry "GNU/Linux, Linux 5.0.2-lfs-8.5" {//
//    linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 
root=/dev/sda1 ro//

//}/



I may have to try using *gpt* as *Partition table* ?


cheers

Pei


On 2019-03-19 12:49 p.m., Bruce Dubbs wrote:

On 3/19/19 1:55 PM, Pei Jia wrote:



Hi, Thank you Pierre and Bruce:


1. Right now, I booted into my laptop's  Ubuntu 18.04.2, and 
/dev/sde1 corresponds to my USB stick for sure, as I can definitely 
see the following line:



➜  ~ sudo blkid

...

/dev/sde1: LABEL="skyvision-3.0" 
UUID="d8a7b940-0ff5-41c4-81a0-9fd1797501ed" TYPE="ext4" 
PARTUUID="0860eda0-01"

...


2. However, when I *reboot*, after pressing *ESC*, I entered *grub >* :

if I do *ls*, I'm 100% sure (hd0), (hd0,msdos1) corresponds to my 
*USB stick drive* and *partition* respectively, as I can do:


*set root=(hd0,msdos1)*

*cat /boot/grub/grub.cfg*

which I can easily tell it is just the grub I put under the *USB 
stick's /boot/grub/ folder*, which is of course, totally different 
from the one on my laptop's 



3. So, I believe there might be 2 possible reasons?

 From this picture: https://longervision.cc/bugs/gparted.jpg

  * My USB stick is NOW of a *msdos partition table*, but *ext4
    filesystem*, is that OK? As mentioned by William that I may *NOT*
    have *vfat* built into the *kernel*. I'll check it again...
  * On this page:
http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html,
    I *didn't *do *grub-install* at all (under lfs configuration and on
    the USB stick). However, I did *sudo update-grub* to have my *host
    laptop's grub updated*, which seems working properly, because it
    *did successfully detect and add the booting info* under*/dev/sde1*
    to my *host laptop's grub.cfg*. And... how can I detect if *EXT4*
    *module* is successfully loaded by the *LFS kernel*? It seems *EXT4
    is NOT a module*, but *built into kernel by default *already?



If you top post again after we have asked you not to do so several 
times, I will not answer again.


An msdos filesystem is OK.  You can make any type of filesystem on 
any partition.  GRUB is finding your kernel just fine.  The problem 
is how the kernel recognizes the disk.  When you boot and get the 
grub prompt, type e for edit and change the root= line to /dev/sda1 
on the *linux* line.   Do *not* change the line that says set 
root=(hd0,msdos1).  That part is working properly.


If that doesn't work, try different variations sdb1, sdc1, sdc1, etc.

  -- Bruce





-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Bruce,


this is *already* my current *grub.cfg on USB stick*. All the bugs I 
posted are just with this *grub.cfg*:



/➜  grub cat grub.cfg //
//# Begin /boot/grub/grub.cfg//
//set default=0//
//set timeout=5//
//
//insmod part_msdos//
//insmod ext2//
//set root=(hd0,msdos1)//
//
//menuentry "GNU/Linux, Linux 5.0.2-lfs-8.5" {//
//    linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sda1 ro//
//}/



I may have to try using *gpt* as *Partition table* ?


cheers

Pei


On 2019-03-19 12:49 p.m., Bruce Dubbs wrote:

On 3/19/19 1:55 PM, Pei Jia wrote:



Hi, Thank you Pierre and Bruce:


1. Right now, I booted into my laptop's  Ubuntu 18.04.2, and 
/dev/sde1 corresponds to my USB stick for sure, as I can definitely 
see the following line:



➜  ~ sudo blkid

...

/dev/sde1: LABEL="skyvision-3.0" 
UUID="d8a7b940-0ff5-41c4-81a0-9fd1797501ed" TYPE="ext4" 
PARTUUID="0860eda0-01"

...


2. However, when I *reboot*, after pressing *ESC*, I entered *grub >* :

if I do *ls*, I'm 100% sure (hd0), (hd0,msdos1) corresponds to my 
*USB stick drive* and *partition* respectively, as I can do:


*set root=(hd0,msdos1)*

*cat /boot/grub/grub.cfg*

which I can easily tell it is just the grub I put under the *USB 
stick's /boot/grub/ folder*, which is of course, totally different 
from the one on my laptop's 



3. So, I believe there might be 2 possible reasons?

 From this picture: https://longervision.cc/bugs/gparted.jpg

  * My USB stick is NOW of a *msdos partition table*, but *ext4
    filesystem*, is that OK? As mentioned by William that I may *NOT*
    have *vfat* built into the *kernel*. I'll check it again...
  * On this page:
http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html,
    I *didn't *do *grub-install* at all (under lfs configuration and on
    the USB stick). However, I did *sudo update-grub* to have my *host
    laptop's grub updated*, which seems working properly, because it
    *did successfully detect and add the booting info* under*/dev/sde1*
    to my *host laptop's grub.cfg*. And... how can I detect if *EXT4*
    *module* is successfully loaded by the *LFS kernel*? It seems *EXT4
    is NOT a module*, but *built into kernel by default *already?



If you top post again after we have asked you not to do so several 
times, I will not answer again.


An msdos filesystem is OK.  You can make any type of filesystem on any 
partition.  GRUB is finding your kernel just fine.  The problem is how 
the kernel recognizes the disk.  When you boot and get the grub 
prompt, type e for edit and change the root= line to /dev/sda1 on the 
*linux* line.   Do *not* change the line that says set 
root=(hd0,msdos1).  That part is working properly.


If that doesn't work, try different variations sdb1, sdc1, sdc1, etc.

  -- Bruce



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Thank you Pierre and Bruce:


1. Right now, I booted into my laptop's  Ubuntu 18.04.2, and /dev/sde1 
corresponds to my USB stick for sure, as I can definitely see the 
following line:



➜  ~ sudo blkid

...

/dev/sde1: LABEL="skyvision-3.0" 
UUID="d8a7b940-0ff5-41c4-81a0-9fd1797501ed" TYPE="ext4" 
PARTUUID="0860eda0-01"

...


2. However, when I *reboot*, after pressing *ESC*, I entered *grub >* :

if I do *ls*, I'm 100% sure (hd0), (hd0,msdos1) corresponds to my *USB 
stick drive* and *partition* respectively, as I can do:


*set root=(hd0,msdos1)*

*cat /boot/grub/grub.cfg*

which I can easily tell it is just the grub I put under the *USB stick's 
/boot/grub/ folder*, which is of course, totally different from the one 
on my laptop's 



3. So, I believe there might be 2 possible reasons?

From this picture: https://longervision.cc/bugs/gparted.jpg

 * My USB stick is NOW of a *msdos partition table*, but *ext4
   filesystem*, is that OK? As mentioned by William that I may *NOT*
   have *vfat* built into the *kernel*. I'll check it again...
 * On this page:
   http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html,
   I *didn't *do *grub-install* at all (under lfs configuration and on
   the USB stick). However, I did *sudo update-grub* to have my *host
   laptop's grub updated*, which seems working properly, because it
   *did successfully detect and add the booting info* under*/dev/sde1*
   to my *host laptop's grub.cfg*. And... how can I detect if *EXT4*
   *module* is successfully loaded by the *LFS kernel*? It seems *EXT4
   is NOT a module*, but *built into kernel by default *already?


Thank you very much.




On 2019-03-19 10:33 a.m., Pierre Labastie wrote:

On 19/03/2019 16:59, Bruce Dubbs wrote:

On 3/19/19 10:01 AM, Pierre Labastie wrote:

On 19/03/2019 14:57, William Harrington wrote:

On Mon, 18 Mar 2019 16:20:32 -0700
Pei Jia  wrote:


Hey all.  The problem is with the linux command line in grub.cfg 
and/or the drivers in the kernel.


Note that he *IS* booting kernel.  GRUB is finding it just fine.


Hmm, possible, but since the grub prompt comes clearly from ubuntu, 
isn't it the ubuntu kernel?


I have this doubt that according to one of the pictures, /dev/sdd is 
15GB, while /dev/sde is 5TB. Pei, when you say "an USB drive", is it 
the 5TB one or the 15GB one? Also, /dev/sde has 2 partitions. And 
/dev/sde1 seems to be a FAT filesystem (if this is the one that is 
mounted)... I'd believe the right partition to mount is /dev/sdd1, but 
update-grub seems to have generated /dev/sde1...


Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, all:


Thank you for your help so far... I make some progress, please refer to 
the following pictures...



https://longervision.cc/bugs/gparted.jpg

https://longervision.cc/bugs/grub.jpg

https://longervision.cc/bugs/kernel_panic.jpg



I'm pretty sure I've got *2 grubs*, *one on laptop*, *the other on USB 
stick*.


For now, I'm sure I boot from laptop's grub, ti comes to the

*Kernel panic - not syncing: No working init found. Try passing init= 
option to kernel.*


*..
*


Does that mean, *an initrd.img is a must?*


It seems I come to the final stage before make it installable 



Thanks



On 2019-03-18 2:41 p.m., spiky0011 wrote:



On 18/03/2019 20:54, Bruce Dubbs wrote:

On 3/18/19 3:20 PM, Pei Jia wrote:


Hi, Bruce:


Thank you for your detailed explanation.


1. 2 grubs

  * *grub on my host's laptop*, please refer to
https://longervision.cc/bugs/grub.jpg . And the contents in
    */boot/grub/grub.cfg* is too much, I'm *NOT* copy/paste it here.
  * grub on my USB stick, the contents in /boot/grub/grub.cfg:

 ➜  grub cat grub.cfg
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5

set root=(*hd0*,*msdos1*)
insmod ext4

menuentry "GNU/Linux, Linux 5.0.2-lfs-8.5" {
 linux   /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 
root=*/dev/**sde* ro

}


Obviously, the *grub.cfg* on my *USB stick* is *incorrect*, right? 
From *grub* *bash*, if I want to load *USB stick's LFS Linux*, I'm 
quite sure the hard drive is *hd0*, which should *corresponds to 
sda* instead of *sde*. No matter what, while booting, my laptop pops 
up https://longervision.cc/bugs/grub.jpg *by default*. So, it seems 
I'm using *my laptop's grub* right now.


I am only guessing, but if the firmware is booting the usb drive, 
then I would try changing the grub.cfg file on the usb drive to say


linux   /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sda1 ro

From the point of view if the system at this time the only drive is 
/dev/sda.


fstab should reflect the same.

grub identifies hard disks differently from the kernel.  hd0 is the 
first drive, but which drive is first?  Depends on the firmware, but 
my guess is the usb drive since it is finding the kernel for 
booting.  The problme is telling the kernel about the system.


  -- Bruce


What is confusing the matter is so many drives, /dev/sd,b,c,d are they 
usb or internal, can they be removed? if yes that would help.


Which grub are you using to boot with? laptop grub or grub on usb, 
stick. Usb stick grub will be harder to setup at 1st.


A good thing to learn would be "booting from grub prompt" this is a 
very usefull piece of knowledge and helps in situations like this.


https://www.linux.com/learn/how-rescue-non-booting-grub-2-linux

grub.cfg should look

set root=(*hd0,msdos1)
insmod ext4

menuentry "GNU/Linux, Linux 5.0.2-lfs-8.5" {
 linux   /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 
root=/dev/sde1 rootdelay=10 ro

}

*"*is vmlinuz-5.0.2-lfs-8.5 in host */boot?* (confirm please) Because 
set root=(hd0,msdos1) is looking in /dev/sda1/boot for 
vmlinuz-5.0.2-lfs-8.5.


Your grub.cfg from host we only need the lfs part none of the rest is 
required.


looking at your fstab

# *_/boot/efi _*was on /dev/sdb1 during installation
UUID=Y *_/boot/efi_*   vfat umask=0077  0   1

is this a uefi boot system??? If it is there's alot wrong.




-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Bruce:


Thank you for your detailed explanation.


1. 2 grubs

 * *grub on my host's laptop*, please refer to
   https://longervision.cc/bugs/grub.jpg . And the contents in
   */boot/grub/grub.cfg* is too much, I'm *NOT* copy/paste it here.
 * grub on my USB stick, the contents in /boot/grub/grub.cfg:

    ➜  grub cat grub.cfg
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5

set root=(*hd0*,*msdos1*)
insmod ext4

menuentry "GNU/Linux, Linux 5.0.2-lfs-8.5" {
    linux   /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 
root=*/dev/**sde* ro

}


Obviously, the *grub.cfg* on my *USB stick* is *incorrect*, right? From 
*grub* *bash*, if I want to load *USB stick's LFS Linux*, I'm quite sure 
the hard drive is *hd0*, which should *corresponds to sda* instead of 
*sde*. No matter what, while booting, my laptop pops up 
https://longervision.cc/bugs/grub.jpg *by default*. So, it seems I'm 
using *my laptop's grub* right now.



2. UUID

On my *laptop's /etc/fstab*, I am using *UUID*.

➜  ~ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#           
# / was on /dev/sdc3 during installation
UUID= /   ext4    
errors=remount-ro 0   1

# /dev/sde1
UUID=*d8a7b940-0ff5-41c4-81a0-9fd1797501ed* / ext4    errors=remount-ro 
0   1

# /boot/efi was on /dev/sdb1 during installation
UUID=Y  /boot/efi   vfat    umask=0077  0   1
/swapfile


3. initrd

 * Yes, I used *Gparted* to create both the *filesystem* (*msdos*) as
   well as the *partition* .
 * And yes, I do NOT have *initrd* so for. Is it a *must*? On my *host
   laptop*, I can see:

➜  /boot ls
config-4.18.0-15-generic  grub memtest86+.bin    
System.map-4.18.0-15-generic vmlinuz-4.18.0-16-generic
config-4.18.0-16-generic  initrd.img-4.18.0-15-generic 
memtest86+.elf    System.map-4.18.0-16-generic
efi   initrd.img-4.18.0-16-generic 
memtest86+_multiboot.bin  vmlinuz-4.18.0-15-generic



Any further suggestions?

Thank you very much...

Pei



On 2019-03-18 10:28 a.m., Bruce Dubbs wrote:

On 3/18/19 5:22 AM, thomas wrote:

Am 2019-03-18 11:14, schrieb Pei Jia:

Hi:

I now make some progress:

 * I followed your suggestions, CP -A LFS OUT TO MY HOST, AND
PARTITION THE USB DRIVE.
 * However, I still failed to boot, please refer to my new result:
https://longervision.cc/bugs/lfs_kernel_panic.jpg

I believe I'm already very close to the RIGHT answer...

Anyway, I now have  2 GRUBS, one is ON MY HOST'S LAPTOP GRUB, the
other is ON MY USD DRIVER.

BTW, is this
http://linuxfromscratch.org/lfs/view/stable/chapter08/grub.html for
configuring GRUB2 on the HOST COMPUTER (EXISTING GRUB) ? or for the
NEWLY USB DRIVE?

Cheers

Pei

On 2019-03-17 2:13 p.m., spiky0011 wrote:


On 17/03/2019 20:33, Pei Jia wrote:

...


Please do not top-post. Add your comments *below* the text you're 
answering. That helps to follow the discussion.


Please provide the grub.cfg file, the fstab of the system to boot and 
the partition layout including info about which partition contains 
which file system.
Indeed, it looks like we not too far from success, but you never 
know...   ;-)




If you want to boot from the usb drive you have to tell the system 
firmware to boot from that system.  That can get tricky because the 
devices will change.  The usb drive will be /dev/sde (for example) 
when booting from the hard disk and /dev/sda (probably) when booting 
from the usb drive.


You can get around that by by using UUIDs instead of devices, but that 
is a bit tricky.  If the drives are partitioned with GPT, then you can 
use PARTUUID and not need an initrd.


Personally I think at the current knowledge level, Pei is trying to 
run before he can walk.


  -- Bruce
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Thank you Thomas ...


1.

➜  ~ blkid

/dev/sde1: LABEL="XX" UUID="*d8a7b940-0ff5-41c4-81a0-9fd1797501ed*" 
TYPE="ext4" PARTUUID="0860eda0-01"


➜  ~ sudo fdisk -l

Disk /dev/sde: 14.8 GiB, 15833497600 bytes, 30924800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0860eda0

Device Boot Start  End  Sectors  Size Id Type
/dev/sde1    2048 30924799 30922752 14.8G 83 Linux


/It is clear that I've correctly partitioned my //*USB stick*//./


2.

➜  ~ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#           
# / was on /dev/sdc3 during installation
UUID= /   ext4    
errors=remount-ro 0   1

# /dev/sde1
UUID=*d8a7b940-0ff5-41c4-81a0-9fd1797501ed* / ext4    errors=remount-ro 
0   1

# /boot/efi was on /dev/sdb1 during installation
UUID=Y  /boot/efi   vfat    umask=0077  0   1
/swapfile


/This is my //*host laptop's fstab*//. Hmm, here is what I'm 
//*NOT*//quite clear. //*mtab automatically*//mounts my *USB stick* 
every time if I don't specify this //*USB stick*//in //*fstab*//. 
Anyway, now I clearly specified this */dev/sde1* via *UUID* in 
/*/fstab/*/, it's *NOT* showing *in mtab* any more, which is just what 
I'm expecting. *However*, how about if I *plug out this USB stick* and 
want to use it on *another laptop*?/



3. Rebooting ... Let me show you some more pictures first...

https://longervision.cc/bugs/grub.jpg

https://longervision.cc/bugs/grub_advanced_option.jpg

https://longervision.cc/bugs/kernel_panic.jpg


/It's weird the names listed in *grub*... Can I change them? But how? I 
checked my *host's grub.cfg*, and found:/


//

menuentry 'Longer Vision Technology (8.4) (on /dev/sde1)' --class 
longervisiontechnology --class gnu-linux --class gnu --class os 
$menuentry_id_option 
'osprober-gnulinux-simple-d8a7b940-0ff5-41c4-81a0-9fd1797501ed' {

    insmod part_msdos
    insmod ext2
    set root='hd4,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 
--hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 
d8a7b940-0ff5-41c4-81a0-9fd1797501ed

    else
      search --no-floppy --fs-uuid --set=root 
d8a7b940-0ff5-41c4-81a0-9fd1797501ed

    fi
    linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sde ro
}
submenu 'Advanced options for Longer Vision Technology (8.4) (on 
/dev/sde1)' $menuentry_id_option 
'osprober-gnulinux-advanced-d8a7b940-0ff5-41c4-81a0-9fd1797501ed' {
    menuentry 'GNU/Linux, Linux 5.0.2-lfs-8.5 (on /dev/sde1)' --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'osprober-gnulinux-/boot/vmlinuz-5.0.2-lfs-8.5--d8a7b940-0ff5-41c4-81a0-9fd1797501ed' 
{

        insmod part_msdos
        insmod ext2
        set root='hd4,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root 
--hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 
--hint-baremetal=ahci4,msdos1 d8a7b940-0ff5-41c4-81a0-9fd1797501ed

        else
          search --no-floppy --fs-uuid --set=root 
d8a7b940-0ff5-41c4-81a0-9fd1797501ed

        fi
        linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sde ro
    }
}


It looks the options are *automatically built* into this*host's* 
*grub.cfg* while I was doing *sudo update-grub* ? I just do NOT like the 
name, and I believe I can modify this *host's grub.cfg* into to show a 
different name (doing it now). However, since it's automatically built 
into this *host's grub.cfg*, where is the *original place* that I can 
specify this info? Just cannot remember. It must be ME who specified 
those info somewhere .




Anyway, Thank you very much for your prompt reply...



Cheers

Pei




On 2019-03-18 3:22 a.m., thomas wrote:

Am 2019-03-18 11:14, schrieb Pei Jia:

Hi:

I now make some progress:

 * I followed your suggestions, CP -A LFS OUT TO MY HOST, AND
PARTITION THE USB DRIVE.
 * However, I still failed to boot, please refer to my new result:
https://longervision.cc/bugs/lfs_kernel_panic.jpg

I believe I'm already very close to the RIGHT answer...

Anyway, I now have  2 GRUBS, one is ON MY HOST'S LAPTOP GRUB, the
other is ON MY USD DRIVER.

BTW, is this
http://linuxfromscratch.org/lfs/view/stable/chapter08/grub.html for
configuring GRUB2 on the HOST COMPUTER (EXISTING GRUB) ? or for the
NEWLY USB DRIVE?

Cheers

Pei

On 2019-03-17 2:13 p.m., spiky0011 wrote:


On 17/

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi:


I now make some progress:

1. I followed your suggestions, *cp -a lfs out to my HOST, and
   partition**the USB drive*.
2. However, I still failed to boot, please refer to my new result:
   https://longervision.cc/bugs/lfs_kernel_panic.jpg

I believe I'm already very close to the RIGHT answer...


Anyway, I now have *2 grubs*, one is *on my host's laptop grub*, the 
other is *on my USD driver*.



BTW, is this 
http://linuxfromscratch.org/lfs/view/stable/chapter08/grub.html for 
configuring *grub2* on the *host computer (existing grub) *? or for the 
*newly USB drive*?




Cheers

Pei



On 2019-03-17 2:13 p.m., spiky0011 wrote:



On 17/03/2019 20:33, Pei Jia wrote:



Hi, Bruce:


Thank you very much for your prompt reply.

I actually *boot from grub*, please refer to:

https://www.longervision.cc/bugs/lfs_grub_boot.jpg


It looks *EXT4* module is *NOT* able to load successfully?


Yes, you are right. I AM booting from a *USB stick*, which I actually 
do *NOT partition the drive*.



From my *HOST Ubuntu 18.04.2*, the USD stick is the drive */dev/sde*, 
I do NOT have a */dev/sde1* 



BTW, did I put *rootdelay=10* at the right position?



Thank you very much Bruce

Pei



On 2019-03-17 11:48 a.m., Bruce Dubbs wrote:

On 3/17/19 1:25 PM, Pei Jia wrote:



Hi, Can anybody give me a hand why my built LFS failed to boot? 
Thank you very much...


The ERROR is displayed at:


https://www.longervision.cc/bugs/lfs_endtrace_fail2boot.jpg


Can you give us some details about your hardware?  Most of the time 
you get a kernel panic at boot is because your did not compile the 
drivers needed to access the disk/root partition into the kernel.


Note the message: "Unable to mount root fs ..."

Another reason that boot fails is because you are trying to boot 
from a USB drive and will need a rootdelay=10 option on the kernel 
command line.


  -- Bruce



You should partition the usb stick not just create a file system on it 
sde1. sde wont work.


You can copy (cp -a) your lfs to HDD, partition the usb /dev/sde1 cp 
-a lfs back, set /etc/fstab as needed and grub,cfg



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Bruce:


Thank you very much for your prompt reply.

I actually *boot from grub*, please refer to:

https://www.longervision.cc/bugs/lfs_grub_boot.jpg


It looks *EXT4* module is *NOT* able to load successfully?


Yes, you are right. I AM booting from a *USB stick*, which I actually do 
*NOT partition the drive*.



From my *HOST Ubuntu 18.04.2*, the USD stick is the drive */dev/sde*, I 
do NOT have a */dev/sde1* 



BTW, did I put *rootdelay=10* at the right position?



Thank you very much Bruce

Pei



On 2019-03-17 11:48 a.m., Bruce Dubbs wrote:

On 3/17/19 1:25 PM, Pei Jia wrote:



Hi, Can anybody give me a hand why my built LFS failed to boot? Thank 
you very much...


The ERROR is displayed at:


https://www.longervision.cc/bugs/lfs_endtrace_fail2boot.jpg


Can you give us some details about your hardware?  Most of the time 
you get a kernel panic at boot is because your did not compile the 
drivers needed to access the disk/root partition into the kernel.


Note the message: "Unable to mount root fs ..."

Another reason that boot fails is because you are trying to boot from 
a USB drive and will need a rootdelay=10 option on the kernel command 
line.


  -- Bruce

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] LFS Fail to Boot at End Trace...

[Pei Jia]

Hi, Can anybody give me a hand why my built LFS failed to boot? Thank 
you very much...


The ERROR is displayed at:


https://www.longervision.cc/bugs/lfs_endtrace_fail2boot.jpg


Cheers

Pei



--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] System Configuration on a USB stick?

[Pei Jia]

Hello:

Finally, I successfully built LFS, and now I come to *Chapter 7 System 
Configuration*.


*Chapter 7: System Configuration*

*Chapter 8: Making the LFS System Bootable*

*Chapter 9: The END*


My question is:

Is *chapter 7 System Configuration* a *must*? I built everything onto a 
USB stick.


 * It does *NOT* have a *video/camera* connecting to it
 * It does *NOT* have a *Wifi module*.
 * I, of course, expect this USB stick is *able to boot*, but *with a
   Wifi connection using my laptop's Wifi*, hopefully the same IP
   address as my local laptop's Ubuntu.
 * What's more, I'm expecting this USB stick is *NOT ONLY bootable*,
   *BUT ALSO installable*.


I wonder if there is a more detailed manual for me to follow?


Thank you very much


Cheers

Pei


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Install readline's header files ...

[Pei Jia]

I've successfully installed Python-3.7.2, but still got this ERROR message:


//sources/python/Python-3.7.2/Modules/readline.c:31:10: fatal error: 
readline/readline.h: No such file or directory//

// #include /


So, I wonder while installing readline 
, 
we may also install the header files ?


cheers

Pei

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Python failed to make while constructing a temporary system...

[Pei Jia]

To whom it may concern:


I'm building LFS, so far everything is good, until *Python while
constructing a temporary system*.

http://www.linuxfromscratch.org/lfs/view/systemd/chapter05/Python.html


 1.  If I strictly follow what's instructed, I obtained the following
*ERROR* messages:

/INFO: Could not locate ffi libs and/or headers//
///mnt/lfs/sources/python/Python-3.7.2/Modules/_dbmmodule.c:16:10: fatal
error: ndbm.h: No such file or directory//
// #include //
//  ^~~~//
//compilation terminated.//
//In file included from ./Include/py_curses.h:36,//
// from
/mnt/lfs/sources/python/Python-3.7.2/Modules/_curses_panel.c:15://
///usr/include/ncursesw/curses.h:60:10: fatal error:
ncursesw/ncurses_dll.h: No such file or directory//
// #include //
//  ^~~~//
//compilation terminated.//
///mnt/lfs/sources/python/Python-3.7.2/Modules/_hashopenssl.c:23:10:
fatal error: openssl/evp.h: No such file or directory//
// #include //
//  ^~~//
//compilation terminated.//
///mnt/lfs/sources/python/Python-3.7.2/Modules/nismodule.c:17:10: fatal
error: rpc/rpc.h: No such file or directory//
// #include //
//  ^~~//
//compilation terminated.//
//In file included from ./Include/py_curses.h:36,//
// from
/mnt/lfs/sources/python/Python-3.7.2/Modules/_cursesmodule.c:113://
///usr/include/ncursesw/curses.h:60:10: fatal error:
ncursesw/ncurses_dll.h: No such file or directory//
// #include //
//  ^~~~//
//compilation terminated./


2. After some investigation, I added up *2 includedirs* as:

/./configure --prefix=/tools --without-ensurepip
--includedir=/usr/include --includedir=/usr/include/x86_64-linux-gnu/


But, obtained more ERRORs as :


..

/In file included from /tools/include/stdio.h:864,//
// from ./Include/Python.h:25,//
// from
/mnt/lfs/sources/python/Python-3.7.2/Modules/_hashopenssl.c:16://
///usr/include/x86_64-linux-gnu/bits/stdio.h:36:40: error: unknown type
name '_G_va_list'; did you mean 'va_list'?//
// vprintf (const char *__restrict __fmt, _G_va_list __arg)//
//    ^~//
//    va_list//
//gcc -pthread -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result
-Wno-unused-parameter -Wno-missing-field-initializers
-Wno-cast-function-type -Werror=implicit-function-declaration
-DHAVE_NCURSESW=1 -I/usr/include/ncursesw -I./Include
-I/usr/include/x86_64-linux-gnu -I. -I/usr/local/include
-I/mnt/lfs/sources/python/Python-3.7.2/Include
-I/mnt/lfs/sources/python/Python-3.7.2 -c
/mnt/lfs/sources/python/Python-3.7.2/Modules/_cursesmodule.c -o
build/temp.linux-x86_64-3.7/mnt/lfs/sources/python/Python-3.7.2/Modules/_cursesmodule.o//
//building '_curses_panel' extension//
//gcc -pthread -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result
-Wno-unused-parameter -Wno-missing-field-initializers
-Wno-cast-function-type -Werror=implicit-function-declaration
-DHAVE_NCURSESW=1 -I/usr/include/ncursesw -I./Include
-I/usr/include/x86_64-linux-gnu -I. -I/usr/local/include
-I/mnt/lfs/sources/python/Python-3.7.2/Include
-I/mnt/lfs/sources/python/Python-3.7.2 -c
/mnt/lfs/sources/python/Python-3.7.2/Modules/_curses_panel.c -o
build/temp.linux-x86_64-3.7/mnt/lfs/sources/python/Python-3.7.2/Modules/_curses_panel.o//
///usr/include/x86_64-linux-gnu/bits/stdio.h:114:16: error: unknown type
name '_IO_ssize_t'//
// __STDIO_INLINE _IO_ssize_t//
//    ^~~//
///usr/include/x86_64-linux-gnu/bits/stdio.h:115:1: error: conflicting
types for 'getline'//
// getline (char **__lineptr, size_t *__n, FILE *__stream)//
// ^~~//
//In file included from ./Include/Python.h:25,//
// from
/mnt/lfs/sources/python/Python-3.7.2/Modules/_hashopenssl.c:16://
///tools/include/stdio.h:616:18: note: previous declaration of 'getline'
was here//
// extern __ssize_t getline (char **__restrict __lineptr,//
//  ^~~//
//building '_bz2' extension//
//gcc -pthread -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result
-Wno-unused-parameter -Wno-missing-field-initializers
-Wno-cast-function-type -Werror=implicit-function-declaration
-I./Include -I/usr/include/x86_64-linux-gnu -I. -I/usr/local/include
-I/mnt/lfs/sources/python/Python-3.7.2/Include
-I/mnt/lfs/sources/python/Python-3.7.2 -c
/mnt/lfs/sources/python/Python-3.7.2/Modules/_bz2module.c -o
build/temp.linux-x86_64-3.7/mnt/lfs/sources/python/Python-3.7.2/Modules/_bz2module.o//
//In file included from /tools/include/stdio.h:864,//
// from ./Include/Python.h:25,//
// from
/mnt/lfs/sources/python/Python-3.7.2/Modules/_dbmmodule.c:6://
///usr/include/x86_64-linux-gnu/bits/stdio.h:36:40: error: unknown type
name '_G_va_list'; did you mean 

[lfs-support] Perl 5.28.1 failed to build while Installing Basic System Software ...

[Pei Jia]

To whom it may concern:

Actually, I've already posted my question at
https://www.linuxquestions.org/questions/linux-from-scratch-13/perl-5-28-1-failed-to-build-while-installing-basic-system-software-4175648992/
.


I just strictly followed this page:
http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/perl.html

while running the configuration,
[CODE]sh Configure -des -Dprefix=/usr \
  -Dvendorprefix=/usr   \
  -Dman1dir=/usr/share/man/man1 \
  -Dman3dir=/usr/share/man/man3 \
  -Dpager="/usr/bin/less -isR"  \
  -Duseshrplib  \
  -Dusethreads[/CODE]

I got the following [B]ERROR[/B] message

[CODE]What libraries to use? [-lpthread -lgdbm -ldl -lm -lcrypt -lutil
-lc -lgdbm_compat] 
What optimizer/debugger flag should be used? [-O2] 
Any additional cc flags? [-D_REENTRANT -D_GNU_SOURCE -fwrapv
-fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include] 
Let me guess what the preprocessor flags are...
Any additional ld flags (NOT including libraries)? [
-fstack-protector-strong -L/usr/local/lib] 
Checking your choice of C compiler and flags for coherency...
I've tried to compile and run the following simple program:

#include 
int main() { printf("Ok\n"); return(0); }

I used the command:

    cc -o try -O2 -D_REENTRANT -D_GNU_SOURCE -fwrapv
-fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include
-fstack-protector-strong -L/usr/local/lib try.c -lpthread -lgdbm -ldl
-lm -lcrypt -lutil -lc -lgdbm_compat
 ./try

and I got the following output:

./try: error while loading shared libraries: libgdbm.so.6: cannot open
shared object file: No such file or directory
The program compiled OK, but exited with status 127.
You have a problem.  Shall I abort Configure [y] 
Ok.  Stopping Configure.[/CODE]

And it seems all required libraries have already been installed under
[B]/usr/lib[/B]:

[CODE](lfs chroot) root:/sources/cpan/perl-5.28.1# ls /usr/lib
Mcrt1.o libbfd-2.32.so libg.a  
liblsan.la   libncurses++w.a   libssp.so.0.0.0
Scrt1.o libbfd.a   libgcc_s.so 
liblsan.so   libncurses.so libssp_nonshared.a
audit   libbfd.la  libgcc_s.so.1   
liblsan.so.0 libncursesw.so    libssp_nonshared.la
bash    libbfd.so  libgdbm.la  
liblsan.so.0.0.0 libnss_compat.so  libstdc++.a
bfd-plugins libbz2.a   libgdbm.so  
liblsan_preinit.o    libnss_db.so  libstdc++.la
crt1.o  libbz2.so  libgdbm.so.6
libltdl.a    libnss_dns.so libstdc++.so
crti.o  libc.a libgdbm.so.6.0.0
libltdl.la   libnss_files.so   libstdc++.so.6
crtn.o  libc.so    libgdbm_compat.la   
libltdl.so   libnss_hesiod.so  libstdc++.so.6.0.25
gcc libc_nonshared.a   libgdbm_compat.so   
libltdl.so.7 libopcodes-2.32.so    libstdc++fs.a
gconv   libcap.so  libgdbm_compat.so.4 
libltdl.so.7.3.1 libopcodes.a  libstdc++fs.la
gcrt1.o libcc1.la  libgdbm_compat.so.4.0.0 
libm-2.29.a  libopcodes.la libsupc++.a
ldscripts   libcc1.so  libgmp.la   
libm.a   libopcodes.so libsupc++.la
libBrokenLocale.a   libcc1.so.0    libgmp.so   
libm.so  libpanel.so   libthread_db.so
libBrokenLocale.so  libcc1.so.0.0.0    libgmp.so.10
libmagic.la  libpanelw.so  libtsan.a
libacl.la   libcrypt.a libgmp.so.10.3.2
libmagic.so  libpanelw.so.6    libtsan.la
libacl.so   libcrypt.so    libgmpxx.la 
libmagic.so.1    libpanelw.so.6.1  libtsan.so
libacl.so.1 libcurses.so   libgmpxx.so 
libmagic.so.1.0.0    libpthread.a  libtsan.so.0
libacl.so.1.1.2253  libcursesw.so  libgmpxx.so.4   
libmcheck.a  libpthread.so libtsan.so.0.0.0
libanl.a    libdl.a    libgmpxx.so.4.5.2   
libmenu.so   libquadmath.a libtsan_preinit.o
libanl.so   libdl.so   libgomp.a   
libmenuw.so  libquadmath.la    libubsan.a
libasan.a   libexpat.la    libgomp.la  
libmenuw.so.6    libquadmath.so    libubsan.la
libasan.la  libexpat.so    libgomp.so  
libmenuw.so.6.1  libquadmath.so.0  libubsan.so
libasan.so  libexpat.so.1  libgomp.so.1
libmpc.la    libquadmath.so.0.0.0  libubsan.so.1
libasan.so.5    libexpat.so.1.6.8  libgomp.so.1.0.0
libmpc.so    libreadline.so    libubsan.so.1.0.0
libasan.so.5.0.0    libfl.a