Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sed: can't read /tools/lib/libstdc++.la: No such file or directory #14

Closed
fishcharlie opened this issue Jul 8, 2019 · 10 comments · Fixed by #15
Closed

sed: can't read /tools/lib/libstdc++.la: No such file or directory #14

fishcharlie opened this issue Jul 8, 2019 · 10 comments · Fixed by #15

Comments

@fishcharlie
Copy link
Contributor

I'm getting an error sed: can't read /tools/lib/libstdc++.la: No such file or directory.

It looks like it's coming from this line:

sed 's/tools/usr/' /tools/lib/libstdc++.la > /usr/lib/libstdc++.la

The confusing thing for me, is in the book in the 6.6 it doesn't mention that command anywhere.

Was this something that had to be added in to work with Docker or something? Any ideas on how to fix it?

Last logs:

Running build..
Preparing Virtual Kernel File Systems..
mkdir: created directory '/mnt/lfs/dev'
mkdir: created directory '/mnt/lfs/proc'
mkdir: created directory '/mnt/lfs/sys'
mkdir: created directory '/mnt/lfs/run'
mount: /dev bound on /mnt/lfs/dev.
mount: devpts mounted on /mnt/lfs/dev/pts.
mount: proc mounted on /mnt/lfs/proc.
mount: sysfs mounted on /mnt/lfs/sys.
mount: tmpfs mounted on /mnt/lfs/run.
Continue with chroot environment..
mkdir: created directory '/bin'
mkdir: created directory '/boot'
mkdir: created directory '/etc'
mkdir: created directory '/etc/opt'
mkdir: created directory '/etc/sysconfig'
mkdir: created directory '/home'
mkdir: created directory '/lib'
mkdir: created directory '/lib/firmware'
mkdir: created directory '/mnt'
mkdir: created directory '/opt'
mkdir: created directory '/media'
mkdir: created directory '/media/floppy'
mkdir: created directory '/media/cdrom'
mkdir: created directory '/sbin'
mkdir: created directory '/srv'
mkdir: created directory '/var'
install: creating directory '/root'
install: creating directory '/tmp'
install: creating directory '/var/tmp'
mkdir: created directory '/usr'
mkdir: created directory '/usr/bin'
mkdir: created directory '/usr/include'
mkdir: created directory '/usr/lib'
mkdir: created directory '/usr/sbin'
mkdir: created directory '/usr/src'
mkdir: created directory '/usr/local'
mkdir: created directory '/usr/local/bin'
mkdir: created directory '/usr/local/include'
mkdir: created directory '/usr/local/lib'
mkdir: created directory '/usr/local/sbin'
mkdir: created directory '/usr/local/src'
mkdir: created directory '/usr/share'
mkdir: created directory '/usr/share/color'
mkdir: created directory '/usr/share/dict'
mkdir: created directory '/usr/share/doc'
mkdir: created directory '/usr/share/info'
mkdir: created directory '/usr/share/locale'
mkdir: created directory '/usr/share/man'
mkdir: created directory '/usr/local/share'
mkdir: created directory '/usr/local/share/color'
mkdir: created directory '/usr/local/share/dict'
mkdir: created directory '/usr/local/share/doc'
mkdir: created directory '/usr/local/share/info'
mkdir: created directory '/usr/local/share/locale'
mkdir: created directory '/usr/local/share/man'
mkdir: created directory '/usr/share/misc'
mkdir: created directory '/usr/share/terminfo'
mkdir: created directory '/usr/share/zoneinfo'
mkdir: created directory '/usr/local/share/misc'
mkdir: created directory '/usr/local/share/terminfo'
mkdir: created directory '/usr/local/share/zoneinfo'
mkdir: created directory '/usr/libexec'
mkdir: created directory '/usr/share/man/man1'
mkdir: created directory '/usr/share/man/man2'
mkdir: created directory '/usr/share/man/man3'
mkdir: created directory '/usr/share/man/man4'
mkdir: created directory '/usr/share/man/man5'
mkdir: created directory '/usr/share/man/man6'
mkdir: created directory '/usr/share/man/man7'
mkdir: created directory '/usr/share/man/man8'
mkdir: created directory '/usr/local/share/man/man1'
mkdir: created directory '/usr/local/share/man/man2'
mkdir: created directory '/usr/local/share/man/man3'
mkdir: created directory '/usr/local/share/man/man4'
mkdir: created directory '/usr/local/share/man/man5'
mkdir: created directory '/usr/local/share/man/man6'
mkdir: created directory '/usr/local/share/man/man7'
mkdir: created directory '/usr/local/share/man/man8'
mkdir: created directory '/lib64'
mkdir: created directory '/var/log'
mkdir: created directory '/var/mail'
mkdir: created directory '/var/spool'
'/var/run' -> '/run'
'/var/lock' -> '/run/lock'
mkdir: created directory '/var/opt'
mkdir: created directory '/var/cache'
mkdir: created directory '/var/lib'
mkdir: created directory '/var/lib/color'
mkdir: created directory '/var/lib/misc'
mkdir: created directory '/var/lib/locate'
mkdir: created directory '/var/local'
'/bin/bash' -> '/tools/bin/bash'
'/bin/cat' -> '/tools/bin/cat'
'/bin/dd' -> '/tools/bin/dd'
'/bin/echo' -> '/tools/bin/echo'
'/bin/ln' -> '/tools/bin/ln'
'/bin/pwd' -> '/tools/bin/pwd'
'/bin/rm' -> '/tools/bin/rm'
'/bin/stty' -> '/tools/bin/stty'
'/usr/bin/install' -> '/tools/bin/install'
'/usr/bin/perl' -> '/tools/bin/perl'
'/usr/lib/libgcc_s.so' -> '/tools/lib/libgcc_s.so'
'/usr/lib/libgcc_s.so.1' -> '/tools/lib/libgcc_s.so.1'
'/usr/lib/libstdc++.a' -> '/tools/lib/libstdc++.a'
'/usr/lib/libstdc++.so' -> '/tools/lib/libstdc++.so'
'/usr/lib/libstdc++.so.6' -> '/tools/lib/libstdc++.so.6'
sed: can't read /tools/lib/libstdc++.la: No such file or directory
@fishcharlie
Copy link
Contributor Author

@EvilFreelancer @reinterpretcat Any ideas on this?

@EvilFreelancer
Copy link
Contributor

EvilFreelancer commented Jul 20, 2019

@fishcharlie hm, seems you may just remove this line.

@reinterpretcat can you fix it, just need remove one from 6.6 script?

@reinterpretcat
Copy link
Owner

Removed in 911bde7

I checked: it exists in LFS-8.1 book, but not in 8.2

@fishcharlie
Copy link
Contributor Author

Ok what about the following section?

for lib in blkid lzma mount uuid
do
ln -sv /tools/lib/lib$lib.{a,so*} /usr/lib
sed 's/tools/usr/' /tools/lib/lib${lib}.la > /usr/lib/lib${lib}.la
done

It looks like it's failing there now too.

'/usr/lib/libstdc++.so.6' -> '/tools/lib/libstdc++.so.6'
'/usr/lib/libblkid.a' -> '/tools/lib/libblkid.a'
'/usr/lib/libblkid.so' -> '/tools/lib/libblkid.so'
'/usr/lib/libblkid.so.1' -> '/tools/lib/libblkid.so.1'
'/usr/lib/libblkid.so.1.1.0' -> '/tools/lib/libblkid.so.1.1.0'
sed: can't read /tools/lib/libblkid.la: No such file or directory

@reinterpretcat @EvilFreelancer

@fishcharlie
Copy link
Contributor Author

Also, commenting out those lines I posted above, results in an error in the man pages build.

Building man pages..
Approximate build time: less than 0.1 SBU
Required disk space: 27 MB
tar: /sources/man-pages-*.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
make: *** No rule to make target 'install'.  Stop.

@fishcharlie
Copy link
Contributor Author

Any ideas on this one @EvilFreelancer @reinterpretcat?

@reinterpretcat
Copy link
Owner

Sorry for late answer.

My guess is that current master is a bit broken and does not match LFS-8.2 book. To be honest, I haven't checked pull request and it might not work. I would suggest to use release version:

https://github.com/reinterpretcat/lfs/releases/tag/v8.1.0

@fishcharlie
Copy link
Contributor Author

@reinterpretcat You should really archive the repository if you aren't going to maintain it any longer. Or put a notice/warning in the README.

Totally fine with people moving onto other projects and not being able to dedicate the time to open source anymore. But the minimum you should do is notify people by posting a warning in the README or archiving the repository on GitHub.

@EvilFreelancer
Copy link
Contributor

Hi to all! @reinterpretcat maybe you may rebase with --force to old relese the master branch? (remove my changes, or move it to another branch)

@reinterpretcat
Copy link
Owner

@fishcharlie
thanks for suggestion. I've updated README: 9b78c27

@EvilFreelancer
Let's see, if there will be more confusion with current master branch, I'll reset it to the latest release state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants