View previous topic :: View next topic |
Author |
Message |
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Thu Apr 12, 2018 7:25 pm Post subject: |
|
|
hedmo,
It looks like you need cmake to build cmake. You will need to build it in your rescue system then install the binary with Code: | emerge -K1 =dev-util/cmake-3.11.0 | or if that fails, the tar method. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
hedmo Veteran
Joined: 29 Aug 2009 Posts: 1305 Location: sweden
|
Posted: Thu Apr 12, 2018 7:58 pm Post subject: |
|
|
NeddySeagoon wrote: | hedmo,
It looks like you need cmake to build cmake. |
NeddySeagoon
is it possible to build that on a old 2016 livedvd that is on a hdd and move it to the /usr on my box
regards hedmo |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Thu Apr 12, 2018 8:11 pm Post subject: |
|
|
hedmo,
I don't know. Try it and tell us.
You may be better getting the tarball from a BINHOST
As I write, its not there yet. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21631
|
Posted: Fri Apr 13, 2018 1:25 am Post subject: |
|
|
I recall from another thread recently that CMake only partially requires itself. Specifically, if you have a recent CMake installed, it will be assumed to be usable and will be used when building the to-be-built CMake. If you do not have CMake installed at all, the ebuild will follow a special path to build a minimal CMake, then use that to finish building the to-be-built CMake. Presumably, this is not done every time since it's a waste of effort when you have a working CMake. In hedmo's case, he has CMake installed, so it is wrongly assumed to be working. If I'm right, he can get past this by unmerging CMake entirely, then emerging it again. That will force the ebuild to use the bootstrap path. |
|
Back to top |
|
|
hedmo Veteran
Joined: 29 Aug 2009 Posts: 1305 Location: sweden
|
Posted: Fri Apr 13, 2018 7:46 pm Post subject: |
|
|
thanks all of you.
I am up running again
best regards hedmo |
|
Back to top |
|
|
vovan47 n00b
Joined: 21 Nov 2018 Posts: 41
|
Posted: Thu Mar 07, 2019 3:27 pm Post subject: |
|
|
Hey guys, I have similar situation like OP, but I couldn't revive portage yet. Even though all python versions are working, still "illegal instruction":
Code: | livecd / # emerge --info
Illegal instruction
livecd / # python
python python-exec2c python2-config python2.7-config python3-config python3.6-config python3.6m-config python3.7-config python3.7m-config
python-config python2 python2.7 python3 python3.6 python3.6m python3.7 python3.7m
livecd / # python2.7 --version
Python 2.7.15
livecd / # python2.7-config
Usage: /usr/bin/python2.7-config [--prefix|--exec-prefix|--includes|--libs|--cflags|--ldflags|--help]
livecd / # python3.6 --version
Python 3.6.5
livecd / # python3.7 --version
Python 3.7.0 (default, Mar 7 2019, 03:10:27)
[GCC 8.2.0]
livecd / # |
Any advice? or that's completely ruined by now? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Thu Mar 07, 2019 10:48 pm Post subject: |
|
|
vovan47,
Its really hard to ruin a gentoo install. Its unlikely you have broken it that badly.
dmesg should tell the file that caused the illegal instruction. The process will have been killed.
Put dmesg onto a pastebin please, just after you have triggered the Illegal instruction. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
vovan47 n00b
Joined: 21 Nov 2018 Posts: 41
|
Posted: Fri Mar 08, 2019 12:04 pm Post subject: |
|
|
NeddySeagoon
Code: | [ 284.252706] traps: emerge[12351] trap invalid opcode ip:7fa75412f645 sp:7ffcdafe6c18 error:0 in libcrypto.so.1.0.0[7fa75401c000+20d000]
[ 287.310696] traps: dmesg[12355] trap invalid opcode ip:562e11a832b3 sp:7ffe8f196050 error:0 in dmesg[562e11a7e000+f000]
|
I've tried to call dmesg in chroot and was a bit stunned as it gave me illegal instruction as well
I figured out that it was openssl package. Installed it with tar from binhost and emerge --info worked! Wow, that's something already! Many thanks |
|
Back to top |
|
|
|