1 |
On 2017-04-24 22:20, Alexander Kapshuk wrote: |
2 |
|
3 |
> > [23+0]~$ ldd /usr/bin/palemoon |
4 |
> > linux-vdso.so.1 (0x00007ffd1cb8a000) |
5 |
> > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd5202a7000) |
6 |
> > libdl.so.2 => /lib64/libdl.so.2 (0x00007fd5200a3000) |
7 |
> > libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libstdc++.so.6 (0x00007fd51fca5000) |
8 |
> > ^^^^^ |
9 |
> > libm.so.6 => /lib64/libm.so.6 (0x00007fd51f9a0000) |
10 |
> > libc.so.6 => /lib64/libc.so.6 (0x00007fd51f602000) |
11 |
> > /lib64/ld-linux-x86-64.so.2 (0x00007fd5204c4000) |
12 |
> > libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libgcc_s.so.1 (0x00007fd51f3eb000) |
13 |
|
14 |
> You did remember to run: |
15 |
> env-update && source /etc/profile |
16 |
> |
17 |
> After doing: |
18 |
> gcc-config 1 |
19 |
> |
20 |
> Did you? |
21 |
|
22 |
I believe this has nothing to do with the environment, and indeed the |
23 |
gcc related environment variables point to gcc-4: |
24 |
|
25 |
[1+0]~$ env | grep -F gcc |
26 |
MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.4/man:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.26.1/man |
27 |
PATH=/home/itz/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.9.4:/usr/games/bin:/home/itz/bin/cargo:/home/itz/bin/gap:/home/itz/bin/ocaml:/home/itz/bin/rc-scripts:/home/itz/bin/opam:/home/itz/bin/polyml:/home/itz/bin/quarry:/home/itz/bin/hugs:/home/itz/bin/HOL |
28 |
INFOPATH=/usr/share/info:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.4/info:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.26.1/info:/usr/share/info/emacs-24 |
29 |
|
30 |
But your post pointed me in the right direction, nonetheless. |
31 |
|
32 |
[2+0]~$ cat /etc/ld.so.conf.d/05gcc-x86_64-pc-linux-gnu.conf |
33 |
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/32 |
34 |
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0 |
35 |
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/32 |
36 |
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4 |
37 |
|
38 |
equery b cannot find any package responsible for this file, so it must |
39 |
be dynamically generated by something. The remaining question is: what |
40 |
is something, and why isn't something plugged into the gcc-config framework? |
41 |
|
42 |
-- |
43 |
Please *no* private Cc: on mailing lists and newsgroups |
44 |
Personal signed mail: please _encrypt_ and sign |
45 |
Don't clear-text sign: |
46 |
http://primate.net/~itz/blog/the-problem-with-gpg-signatures.html |