View previous topic :: View next topic |
Author |
Message |
tckosvic n00b
Joined: 18 Apr 2023 Posts: 67
|
Posted: Wed Mar 27, 2024 6:33 pm Post subject: Upgrading from 17.1 profile to 23 profile. question! |
|
|
News item 28 in step 4 says "note down the value of the CHOST variable". see below:
my *old* chost --> CHOST="x86_64-pc-linux-gnu"
Step 6 says: "In some cases (hppa, x86) the table will tell you to pick between two choices.
What you need should be obvious from your *old* CHOST value (from step 4)."
My 2 choices for new binhost directory are:
amd64/binpackages/23.0/x86-64
amd64/binpackages/23.0/x86-64-v3
Which choice seems the most "obvious"?
thanks,
tom kosvic |
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 1660
|
Posted: Wed Mar 27, 2024 6:43 pm Post subject: |
|
|
While step 6 is primarily referring to the profile column, the article https://www.gentoo.org/news/2024/02/04/x86-64-v3.html would help you decide if using the official binhost.
I will caution that there have been some initial issues with 23.0 profiles on that binhost but they are quickly being worked through. |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1535
|
|
Back to top |
|
|
tckosvic n00b
Joined: 18 Apr 2023 Posts: 67
|
Posted: Wed Mar 27, 2024 6:57 pm Post subject: |
|
|
Everything seems to be running fine so I will skip profile upgrade for a while until things look under control |
|
Back to top |
|
|
tckosvic n00b
Joined: 18 Apr 2023 Posts: 67
|
Posted: Wed Mar 27, 2024 8:55 pm Post subject: |
|
|
It looks like amd64/binpackages/23.0/x86-64-v3 for new binhost directory should be used per the ld command results. Agreed? see below.
Code: |
(base) tom@gentooVM ~ $ ld.so --help
Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
You have invoked 'ld.so', the program interpreter for dynamically-linked
ELF programs. Usually, the program interpreter is invoked automatically
when a dynamically-linked executable is started.
You may invoke the program interpreter program directly from the command
line to load and run an ELF executable file; this is like executing that
file itself, but always uses the program interpreter you invoked,
instead of the program interpreter specified in the executable file you
run. Invoking the program interpreter directly provides access to
additional diagnostics, and changing the dynamic linker behavior without
setting environment variables (which would be inherited by subprocesses).
--list list all dependencies and how they are resolved
--verify verify that given object really is a dynamically linked
object we can handle
--inhibit-cache Do not use /etc/ld.so.cache
--library-path PATH use given PATH instead of content of the environment
variable LD_LIBRARY_PATH
--glibc-hwcaps-prepend LIST
search glibc-hwcaps subdirectories in LIST
--glibc-hwcaps-mask LIST
only search built-in subdirectories if in LIST
--inhibit-rpath LIST ignore RUNPATH and RPATH information in object names
in LIST
--audit LIST use objects named in LIST as auditors
--preload LIST preload objects named in LIST
--argv0 STRING set argv[0] to STRING before running
--list-tunables list all tunables with minimum and maximum values
--list-diagnostics list diagnostics information
--help display this help and exit
--version output version information and exit
This program interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2
Shared library search path:
(libraries located via /etc/ld.so.cache)
/lib64 (system search path)
/usr/lib64 (system search path)
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
(base) tom@gentooVM
|
|
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 4157 Location: Bavaria
|
Posted: Wed Mar 27, 2024 10:15 pm Post subject: |
|
|
tckosvic wrote: | It looks like amd64/binpackages/23.0/x86-64-v3 for new binhost directory should be used per the ld command results. Agreed? |
Yes, I agree.
_________________ https://wiki.gentoo.org/wiki/User:Pietinger |
|
Back to top |
|
|
|