The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "User talk:Invakid404/CLFS"
(Created page with "I went through the entire set of instructions and it's amazing. Things worked as expected. I put a couple of <tt><nowiki>{{Note}}</nowiki></tt>s on the page, and changed a {{c...") |
|||
| Line 2: | Line 2: | ||
I am now messing around inside my build (at {{f|/home/drobbins/404beast}}) and realizing that it would be really useful to have {{c|wget}} inside the fchroot so that we can grab sources and build them inside. Though I have a ton of sources in the fchroot from building that I could use to test some builds of real software, I think. | I am now messing around inside my build (at {{f|/home/drobbins/404beast}}) and realizing that it would be really useful to have {{c|wget}} inside the fchroot so that we can grab sources and build them inside. Though I have a ton of sources in the fchroot from building that I could use to test some builds of real software, I think. | ||
---- | |||
In testing a build of bzip2 inside the fchroot, I ran into this issue: | |||
{{console|body= | |||
rm -f libbz2.a | |||
ar cq libbz2.a blocksort.o huffman.o crctable.o randtable.o compress.o decompress.o bzlib.o | |||
make: /bin/sh: No such file or directory | |||
make: *** [Makefile:49: libbz2.a] Error 127 | |||
bash-5.1 # | |||
}} | |||
I think this can easily be fixed with a symlink but it would be interesting to start documenting all of the little tweaks needed to get the tools environment as functional as possible for builds of GNU software without complications. | |||
--[[User:Drobbins|Drobbins]] ([[User talk:Drobbins|talk]]) 04:25, March 1, 2022 (UTC) | --[[User:Drobbins|Drobbins]] ([[User talk:Drobbins|talk]]) 04:25, March 1, 2022 (UTC) | ||
Revision as of 04:28, March 1, 2022
I went through the entire set of instructions and it's amazing. Things worked as expected. I put a couple of {{Note}}s on the page, and changed a rm -r to rm -rf. Then I left a second one as rm -r (I think for gcc) after thinking I should check with you on this before making so many changes. The extra -f is needed to make copy/paste of the instructions work as expected.
I am now messing around inside my build (at /home/drobbins/404beast) and realizing that it would be really useful to have wget inside the fchroot so that we can grab sources and build them inside. Though I have a ton of sources in the fchroot from building that I could use to test some builds of real software, I think.
In testing a build of bzip2 inside the fchroot, I ran into this issue:
rm -f libbz2.a ar cq libbz2.a blocksort.o huffman.o crctable.o randtable.o compress.o decompress.o bzlib.o make: /bin/sh: No such file or directory make: *** [Makefile:49: libbz2.a] Error 127 bash-5.1 #
I think this can easily be fixed with a symlink but it would be interesting to start documenting all of the little tweaks needed to get the tools environment as functional as possible for builds of GNU software without complications.