-
Notifications
You must be signed in to change notification settings - Fork 85
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
Comments
@EvilFreelancer @reinterpretcat Any ideas on this? |
@fishcharlie hm, seems you may just remove this line. @reinterpretcat can you fix it, just need remove one from 6.6 script? |
Removed in 911bde7 I checked: it exists in LFS-8.1 book, but not in 8.2 |
Ok what about the following section? lfs/scripts/build/6.6-create-essentials.sh Lines 10 to 14 in ece7b0b
It looks like it's failing there now too.
|
Also, commenting out those lines I posted above, results in an error in the man pages build.
|
Any ideas on this one @EvilFreelancer @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: |
@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. |
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) |
@fishcharlie @EvilFreelancer |
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:
lfs/scripts/build/6.6-create-essentials.sh
Line 9 in ece7b0b
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:
The text was updated successfully, but these errors were encountered: