| View previous topic :: View next topic |
| Author |
Message |
mightysilentsaint
n00b
Joined: 11 Aug 2018
Posts: 12
|
 Posted: Mon Nov 05, 2018 1:53 am Post subject: question about fully ~amd64 installation |
 |
|
it's solved all thanks to awesome guide of u/gyakovlev. here's the way to get a fully working ~amd64 installation, do refer to the amd64 handbook for the other parts though, go through these steps after the "step 20 - configuring the locales" section in the amd64 handbook (do add the "~amd64" keyword to your make.conf):
don't skip this `-1` option for emerge in my examples, otherwise you'll add packages to your world file.
| Code: | # get new portage
emerge portage -av1
# update linux-headers and glibc and co, so it's using up to date headers
emerge linux-headers glibc -av1
etc-update
# update binutils and libtool, get rid of old
emerge libtool binutils binutils-config -avu1
emerge -ca binutils
env-update && source /etc/profile && export PS1="(CHROOT) $PS1"
# update gcc and co, skipping old.
emerge gcc mpfr mpc gcc-config -avu1
gcc-config x86_64-pc-linux-gnu-8.2.0
emerge -ca gcc
env-update && source /etc/profile && export PS1="(CHROOT) $PS1"
# rebuild toolchain and co with all new gcc
emerge libtool binutils glibc libnsl opensp mpc mpfr gmp libtirpc dev-libs/libffi -av1
# update perl and update all it's deps to prevent build falures
emerge perl perl-CPAN-Meta perl-cleaner -avu1
perl-cleaner --reallyall
# update all packages to unstable
emerge -uDN --with-bdeps=y --changed-deps y --dynamic-deps y --complete-graph @world @system -av1 --keep-going
etc-update
# clean up unneeded
emerge -ca
# read the news!
eselect news read
# run this to rebuild all packages with the new flags
emerge -e world |
after all of these steps, your system is completely ~amd64. you can continue the handbook from the kernel compiling section to complete your installation.
-----------------------------------------------------------------------------------------
i partitioned my disks, untarred the latest stage3-amd64, chrooted, selected my profile (17.0/), added my own make.conf flags but just did a -uDUpv so didn't compile anything, compiled my kernel, configured the locale and the network and installed grub. this is basically a fully working but empty gentoo install without the use flags components compiled.
at this point, given the fact that i haven't compiled anything other than grub os-prober intel-microcode bc lz4 and libelf, i added the ACCEPT_KEYWORDS="~amd64" to my make.conf. when i added ~amd64 and ran emerge -uDU @world @system, i saw uncopiable amounts of dependency errors in a huge wall of text.
what is the way to get a fully working clean ~amd64 gentoo install? i'm not asking if i should do it or not, i just want to know how.
Last edited by mightysilentsaint on Tue Nov 06, 2018 11:59 am; edited 1 time in total |
|
| Back to top |
|
 |
matt_w
Apprentice
Joined: 17 Nov 2003
Posts: 233
Location: UK
|
| Posted: Mon Nov 05, 2018 3:51 am Post subject: |
|
|
| Can you post your make.conf? You should also be able to post the error messages, but it might be easiest to put it in a place like pastebin since the logs can be pretty lengthy |
|
| Back to top |
|
|
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Mon Nov 05, 2018 4:41 am Post subject: |
|
|
On a clean install I would just do an emerge -e @world then you rebuild all the generic packages and update to ~amd64 cleanly. As long as your use flags are sane it shouldn't trigger anything odd.
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Mon Nov 05, 2018 12:06 pm Post subject: |
|
|
mightysilentsaint,
| Code: | | emerge -uDU @world @system |
is redundant. @system is included in @world.
As you have changed your profile, you probably need -N rather that -U. but as The Doctor says, should just work.
If it fails,
| Code: | emerge wgetpaste
wgetpaste -c "emerge -ep @world" |
and tell us the link.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
mightysilentsaint
n00b
Joined: 11 Aug 2018
Posts: 12
|
| Posted: Tue Nov 06, 2018 12:03 pm Post subject: |
|
|
| NeddySeagoon wrote: | mightysilentsaint,
| Code: | | emerge -uDU @world @system |
is redundant. @system is included in @world.
As you have changed your profile, you probably need -N rather that -U. but as The Doctor says, should just work.
If it fails,
| Code: | emerge wgetpaste
wgetpaste -c "emerge -ep @world" |
and tell us the link. |
i've updated the main post and added the way i proceeded, i now have a fully working ~amd64 install. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Tue Nov 06, 2018 12:28 pm Post subject: |
|
|
mightysilentsaint,
Those with long memories will remember | Code: | | /usr/portage/scripts/bootstrap.sh |
which does much of what you recommend.
That's the script that takes you from a stage1 tarball to stage2, in the days when stage1 and stage2 were supported install starting points.
stage1 and stage2 are still generated by the stage3 building process but only the stage3 is distributed now.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
