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

[reinterpretcat]

Removed in 911bde7

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

[fishcharlie]

@EvilFreelancer @reinterpretcat Any ideas on this?

[EvilFreelancer]

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

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

[fishcharlie]

Ok what about the following section?

lfs/scripts/build/6.6-create-essentials.sh

Lines 10 to 14 in ece7b0b

	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]

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]

Any ideas on this one @EvilFreelancer @reinterpretcat?

[reinterpretcat]

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]

@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]

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]

@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.