| View previous topic :: View next topic |
| Author |
Message |
Sir Platypus
n00b
Joined: 10 Aug 2017
Posts: 17
|
 Posted: Mon May 07, 2018 9:10 pm Post subject: kmod compilation checking build flags for every file[SOLVED] |
 |
|
Hi, I'm installing Gentoo on an old Dimension 4600 that I had lying around, in hopes of later using it to bootstrap LFS. I am currently just before the part where I compile the kernel, and I am installing the kmod package for module compression. It has been going for 15 hours, and from what I can tell it is checking the environment for support for all of the build flags with every file that it includes. A friend of mine said it most likely should not be doing this, so I am wondering if there is a problem with the package.
I see it saying | Code: | | checking if i686-pc-linux-gnu-gcc supports flag [whatever flag it is] |
for every compiler flag that is being passed, and it does it for every individual file, taking much more time than it should. Is this normal?
Last edited by Sir Platypus on Wed May 09, 2018 12:01 am; edited 1 time in total |
|
| Back to top |
|
 |
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Mon May 07, 2018 11:43 pm Post subject: |
|
|
You have a problem if kmod need 15 hours to build for sure.
Check heat (overheating cpu decrease its speed as protection)
Memory short (swapping is killer sometimes, but for kmod, i doubt it could be that)
Dying hdd (a dying hdd could crawl to its knees)
Even if really it does that on each file like you say and no caching is at work (because many build system are caching results), i doubt you would need 15 hours just for kmod. |
|
| Back to top |
|
|
Sir Platypus
n00b
Joined: 10 Aug 2017
Posts: 17
|
| Posted: Tue May 08, 2018 2:05 am Post subject: |
|
|
| The ram isn’t the issue, and I don’t think the cpu or hard drive are having problems. I installed Debian with no trouble, and installing all the profile packages went by with no trouble either. As of now, it’s still going over 24 hours after I started it. I assumed that checking the build environment for every file was the problem, but if it’s not done by morning I’m cutting it off and checking my hardware. |
|
| Back to top |
|
|
Sir Platypus
n00b
Joined: 10 Aug 2017
Posts: 17
|
| Posted: Tue May 08, 2018 11:32 pm Post subject: |
|
|
| I found the problem. I rebooted a few days ago, and I did not think to realize that when I started up again, the livecd would reset the time back to 2004 when it is set to. So, I never went back and synced to a time server again, leading to a timestamp that was 14 years in the future. This made the configure script get stuck in a loop. |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Wed May 09, 2018 12:03 am Post subject: |
|
|
| Sir Platypus wrote: | | Is it possible that for some reason the compiler is stuck in a loop? |
Well, when you have excluded the impossible, whatever remains, however improbable, must be the truth 
You should have a build.log that will help you, you know, to first remove the possible before calling an exorcist
portage store it in /var/tmp/portage/package_category/package_name-version/temp
But as you might already found the cause, maybe just use an ntp service |
|
| Back to top |
|
|
Sir Platypus
n00b
Joined: 10 Aug 2017
Posts: 17
|
| Posted: Wed May 09, 2018 12:37 am Post subject: |
|
|
| Yeah, I resynced to ntp and now it works great. I wasn’t aware of the build.log, I’ll have to have a look next time. |
|
| Back to top |
|
|
|
Installing Gentoo
