public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: crossgcc@sources.redhat.com
Subject: Disable gdb Python support?
Date: Tue, 14 Aug 2012 20:52:00 -0000	[thread overview]
Message-ID: <k0edq5$cdc$1@dough.gmane.org> (raw)

We've been using crosstool-ng for a couple years -- we're currently
using 1.12.  Gdb used to work find for us, but it seems to have broken
when we switched our configuration from 6.8 to 7.2. It appears that
newer versions of gdb are being built with some sort of Python
dependency:

ldd ./arm-linux-gdb
        linux-gate.so.1 (0xffffe000)
        libncurses.so.5 => /lib/libncurses.so.5 (0xb7743000)
        libz.so.1 => /lib/libz.so.1 (0xb772e000)
        libm.so.6 => /lib/libm.so.6 (0xb7707000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb76ee000)
        libdl.so.2 => /lib/libdl.so.2 (0xb76e9000)
        libutil.so.1 => /lib/libutil.so.1 (0xb76e5000)
>>>>    libpython2.6.so.1.0 => /usr/lib/libpython2.6.so.1.0 (0xb758a000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7560000)
        libc.so.6 => /lib/libc.so.6 (0xb7410000)

That's causing problems for us since not all of our host machines have
the same python versions installed.

We didn't seem to have this problem with gdb 6.8.

Is there any way to disable the Python support when crosstool-ng
builds the host-side gdb?

-- 
Grant Edwards               grant.b.edwards        Yow! When this load is
                                  at               DONE I think I'll wash it
                              gmail.com            AGAIN ...


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-08-14 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 20:52 Grant Edwards [this message]
2012-08-14 21:00 ` Yann E. MORIN
2012-08-14 21:17   ` Grant Edwards
2012-08-14 21:33     ` Yann E. MORIN
2012-08-14 21:41       ` Grant Edwards

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='k0edq5$cdc$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=crossgcc@sources.redhat.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).