View previous topic :: View next topic |
Author |
Message |
ch64 Guru
Joined: 09 Jun 2010 Posts: 412
|
Posted: Sat Jul 17, 2021 12:35 pm Post subject: Can't compile via Genkernel on Notebook |
|
|
Hi again Dear Gentoo Forum
I was just trapping into my new Notebook/ThinkPad , there is Genkernel sub-functionating anyhow.
I can't Genkernel my own configs and I can't do genkernel all with standart run.
See my paste:
https://paste.it-flash.de/24-paste.txt
PS: In the initial merging and installing process I could make the actual kernel.
But after installation I can't go further cpio / busybox / => initramfs
Ah and btw. I tried IT not to touch the conf file. So genkernel all doesnt work obviosly.
Thanks |
|
Back to top |
|
|
ch64 Guru
Joined: 09 Jun 2010 Posts: 412
|
|
Back to top |
|
|
larrys Tux's lil' helper
Joined: 20 Jul 2020 Posts: 81 Location: New Jersey
|
Posted: Fri Jul 30, 2021 2:58 am Post subject: Path |
|
|
ch64, I noticed this error:
Code: | make -C /var/tmp/genkernel/gk_bfrcPIPu/busybox/busybox-1.33.1 KBUILD_SRC= .kernelrelease
/var/tmp/genkernel/gk_bfrcPIPu/busybox/busybox-1.33.1/scripts/Kbuild.include:83: *** Recursive variable 'PATH' references itself |
Could you please share what your PATH is set to? When I run this command manually, it works. |
|
Back to top |
|
|
ch64 Guru
Joined: 09 Jun 2010 Posts: 412
|
Posted: Sat Jul 31, 2021 3:39 pm Post subject: |
|
|
Koofn Koofn, Koofn |
|
Back to top |
|
|
larrys Tux's lil' helper
Joined: 20 Jul 2020 Posts: 81 Location: New Jersey
|
Posted: Sun Aug 01, 2021 3:04 am Post subject: |
|
|
ch64,
Genkernel would not build busybox if the system version was up to date. Have you tried to emerge @world first before attempting your kernel build.
Regards. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Sun Aug 01, 2021 9:49 am Post subject: |
|
|
ch64,
Sorry, I don't use genkernel.
The error that larrys pointed out is a problem but I don't know the solutiion.
Can you build the kernel and the initrd for the kernel separately?
What version of genkernel are you using?
Try a different version.
Code: | * sys-kernel/genkernel
Available versions: 4.0.10 4.2.3 **9999*l |
Not the -9999 version.
larrys,
genkernel builds the entire initrd for itself. Any packages that may be installed on the system are not used. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
ch64 Guru
Joined: 09 Jun 2010 Posts: 412
|
Posted: Sun Aug 01, 2021 10:14 am Post subject: |
|
|
I did a complete world also rebuild toolchain.
Now after 15 days of not knowing what to do (and mixing 5 tracks) (for your honor: https://lab.spacecourt.org/flash2_aka_djspacecourt-theperfectmatch_original.mp3 )
I now firstly, do recompile the latest world ... avuDN
I also did a manual make V=1 but don't remember how to make an initfs https://wiki.gentoo.org/wiki/Initramfs/Guide
Code: | [detached from 20569.emerge1]
ThinkPad ~ # echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/lib/llvm/12/bin:/usr/lib/llvm/11/bin:/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}
ThinkPad ~ # |
distcc shouldn't be the problem and:
Think! Geek!
Could IT be fstab? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Sun Aug 01, 2021 11:00 am Post subject: |
|
|
ch64,
I was intending that you used genkernel to build both the kernel and initrd but issue separate commands.
The idea is to try to break the problem into small pieces ... like eating an elephant, do it one plateful at a time. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
larrys Tux's lil' helper
Joined: 20 Jul 2020 Posts: 81 Location: New Jersey
|
Posted: Sun Aug 01, 2021 11:47 am Post subject: |
|
|
NeddySeagoon,
Then busybox in /var/log/genkernel.log is new than the one on my system, so I see your point.
Code: | * busybox: >> Using busybox-1.33.1 binpkg ... |
Code: | # qlist -Iv | grep busybox
sys-apps/busybox-1.32.1-r1 |
ch64,
If you look closely at your PATH, the last element is :${PATH}. So PATH is recursive. This is what the Makefile error for busybox was complaining about. You should probably should find where you added that setting and remove it. You might have done some thing like Code: | PATH="${PATH}:\${PATH}" | . I don't know for sure, but make does not like it. |
|
Back to top |
|
|
ch64 Guru
Joined: 09 Jun 2010 Posts: 412
|
Posted: Wed Aug 04, 2021 4:17 pm Post subject: |
|
|
Neddy, I have tried both:
Available versions: 4.0.10 4.2.3
genkernel initramfs does make that error.
Only thing I could do is making all manually which I did not for a longer time.
Okay, not pretty hard, but I want genkernel for the first go, because I don't know every hardware component unlessly.
After fixing $PATH it now seems to work probably.
I answer later, again.
Ah yes: DONE
* You will find the initramfs in '/boot/initramfs-5.10.49-gentoo-r1-x86_64.img'.
I now reboot once
Ok, all done.
The question is, - If I reboot the Path is wrong, again.
Where do I put it best? I like bashrc |
|
Back to top |
|
|
|