public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: John Gilmore <gnu@toad.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Doug Evans <dje@google.com>,
	       Meador Inge <meadori@codesourcery.com>,
	gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Thu, 11 Oct 2012 08:42:00 -0000	[thread overview]
Message-ID: <20121011084229.GA15186@host2.jankratochvil.net> (raw)
In-Reply-To: <201210040732.q947Wok7025038@new.toad.com>

On Thu, 04 Oct 2012 09:32:50 +0200, John Gilmore wrote:
> Package management is a sinkhole, unfortunately.  The OLPC project has
> unfortunately discovered that despite the great support in the GNU
> tools for cross-compilation, the Fedora package management tools are
> completely incapable of cross-compilation.  So now that they are
> making hardware with three architectures to build software for (i386,
> i686, and ARM), they need to dedicate three kinds of hardware to
> building their Fedora-based releases.  They can't make an OS image on
> a fast x86 machine that will install or boot on an ARM.(*)
> 
> (I think Debian/Ubuntu package managers suffer from the same problem;

They have:
	http://wiki.debian.org/Multiarch


> I recommend NOT assuming that package managers are the cat's pajamas
> and that therefore we can all skip the ability to usefully build from
> source.

This was also my goal, to be able to build from source.  Currently you
"cannot", as you will build something doing unexpected things (the
relocations).


> and yet I still don't understand why y'all care,

Because GDB introduces serious change in where its files are located without
it being relevant to its debugger subject.  The same way every other package
on system could be self-relocated; it is not.  Therefore GDB also should not.

If anybody needs it for GDB it should be introduced first as a general package
relocation feature.


> perhaps someone
> should try to write up a solid proposal that explains what the hell is
> going on, with pros and cons listed and generally agreed upon.  That
> might help point a path to making a decision that sticks for a while.

$ set | grep /var/lib/mock/fedora-16-x86_64/root
$ echo foo >>/var/lib/mock/fedora-16-x86_64/root/usr/share/gdb/python/gdb/__init__.py
$ /var/lib/mock/fedora-16-x86_64/root/usr/bin/gdb
Traceback (most recent call last):
  File "<string>", line 70, in <module>
  File "<string>", line 67, in GdbSetPythonDirectory
  File "/var/lib/mock/fedora-16-x86_64/root/usr/share/gdb/python/gdb/__init__.py", line 42, in <module>
    foo

This is apparently broken, there is no reason why
/var/lib/mock/fedora-16-x86_64/root/usr/bin/gdb should touch anything under
/var/lib/mock/fedora-16-x86_64/root , no other package does so.


And this leads to the issues what everything should be self-relocated as no
other system package is self-relocated.  So then GDB tries to self-relocate
also Python etc. and it can never work completely.


Regards,
Jan

  reply	other threads:[~2012-10-11  8:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46   ` Jan Kratochvil
2012-09-18 19:38     ` Doug Evans
2012-09-19  8:04       ` Jan Kratochvil
2012-09-21 15:37         ` Joel Brobecker
2012-09-21 15:44           ` Jan Kratochvil
2012-09-21 15:58             ` Joel Brobecker
2012-09-21 17:28               ` Jan Kratochvil
2012-10-02 13:09                 ` Joel Brobecker
2012-10-03 15:13                   ` Jan Kratochvil
2012-10-03 15:14                     ` Jan Kratochvil
2012-10-03 15:39                     ` Joel Brobecker
2012-10-03 17:44                       ` Eli Zaretskii
2012-10-03 17:54                       ` Jan Kratochvil
2012-10-03 17:57                         ` Paul_Koning
2012-10-03 18:35                           ` Eli Zaretskii
2012-10-03 18:43                             ` Jan Kratochvil
2012-10-03 18:52                               ` Eli Zaretskii
2012-10-03 19:03                                 ` Jan Kratochvil
2012-10-03 19:10                                   ` Eli Zaretskii
2012-10-03 19:54                               ` Paul_Koning
2012-10-03 20:04                                 ` Jan Kratochvil
2012-10-03 20:11                               ` Alfred M. Szmidt
2012-10-03 18:40                         ` Eli Zaretskii
2012-10-03 19:26                         ` Terekhov, Mikhail
2012-10-04  7:33                         ` John Gilmore
2012-10-11  8:42                           ` Jan Kratochvil [this message]
2012-10-11 14:54                             ` Doug Evans
2012-09-21 15:55   ` Meador Inge
2012-09-21 16:01     ` Jan Kratochvil
2012-09-21 16:36       ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121011084229.GA15186@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=gnu@toad.com \
    --cc=meadori@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).