> From: Keith Marshall <keith****@users*****> > Date: Sat, 25 Jul 2020 12:12:32 +0100 > > > This GDB was configured as follows: > > configure --host=i686-pc-mingw32 --target=i686-pc-mingw32 > > ... > > --with-python=d:/usr/Python26 (relocatable) > > ... > > --with-system-gdbinit=d:/usr/etc/gdbinit (relocatable) > > From the latter, I deduce that your GDB was configured with > > --prefix=d:/usr > > and, when you installed Python, you also changed its default prefix from > C:/, to also place it under d:/usr ... which is fine; it is your choice > to make. Yes. I generally consider the C: drive to be not such a good place for installing add-on programs, since that's the system drive that has issues with protection and access rights. > OTOH, _my_ GDB is configured with > > --prefix=C:/MinGW > > (which is consistent with convention for _all_ packages distributed by > MinGW.org, as has been enshrined in project policy for years), whereas, > since Python is _not_ distributed by MinGW.org, so I've installed it in > the default prefix prescribed by _its_ distributor, equivalent to > > --prefix=C:/Python27 > > Since, in your case, the GDB and Python prefixes are the same, _your_ > GDB views Python as bound to, and relocatable with, GDB. OTOH, in my > case the two prefixes are not the same, so _my_ GDB views Python as > independent, and thus not relocatable with GDB. So you are saying that an "empty" prefix such as "C:/" is not considered as "common" by the code that examines "relocatability"? Could be, I admit I never looked into how it works, I just know it does with non-"empty" common prefixes.
Fork