On Fri, 5 Jul 2019, Bruce Dubbs via blfs-dev wrote:
In the current gcc-9.1 instructions after 'make install' we have:
mkdir -pv /usr/share/gdb/auto-load/usr/lib &&
mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib &&
chown -v -R root:root \
/usr/lib/gcc/*linux-gnu/9.1.0/include{,-fixed}
In the first segment, my build script stopped becasue there are no
/usr/lib/*gdb.py files. Indeed, I have no /usr/lib/*.py files at all.
I do have /usr/share/gdb/auto-load/usr/lib, but that was installed bu
gcc in LFS.
In the second segment, I ran the chown command by hand and got
"ownership of '<filename>' retained as root:root" in every case.
I recommend removing these statements, but want to ask for other opinions.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Hi Bruce.
For the first segment, GCC chapter 6 reports the following:
[...]
make[2]: Leaving directory '/sources/gcc-9.1.0/build/gcc'
make[1]: Leaving directory '/sources/gcc-9.1.0/build'
'/usr/bin/cc' -> 'gcc'
install: creating directory '/usr/lib/bfd-plugins'
'/usr/lib/bfd-plugins/liblto_plugin.so' ->
'../../libexec/gcc/x86_64-pc-linux-gnu/9.1.0/liblto_plugin.so'
mkdir: created directory '/usr/share/gdb'
mkdir: created directory '/usr/share/gdb/auto-load'
mkdir: created directory '/usr/share/gdb/auto-load/usr'
mkdir: created directory '/usr/share/gdb/auto-load/usr/lib'
renamed '/usr/lib/libstdc++.so.6.0.26-gdb.py' ->
'/usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.26-gdb.py'
[...]
So it appears that on my build, there is indeed one *gdb.py file to be
moved.
As for the second segment, I don't see any of that stuff on the GCC
page.
Regards,
-- Ryan
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
