Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Steve Ellcey " <sellcey@mips.com>
To: <gdb@sourceware.org>
Subject: GDB/Python configuration question
Date: Fri, 08 Nov 2013 00:03:00 -0000	[thread overview]
Message-ID: <d0bdf801-dcec-4757-81d9-f1cb92326ab9@BAMAIL02.ba.imgtec.org> (raw)


This question should probably be asked on the python list but since the only
reason I am building python is to build gdb I thought I would start here and
find out if I am really the only person running into this issue and in the
hopes that someone here has some good connections into that project and could
forward the bug on.

I am building and installing python into a non-standard location on my
x86 linux box (ubuntu 12.04), this seems to all work fine.  It builds and
installs an archive, but not shared, python library (libpython2.7.a).  I add
the bin directory containing python-config.py to my PATH and then I try to
configure and build gdb (configuring with --with-python).

The GDB configure script uses python-config.py to set python_libs and
compiles and links a test program that calls Py_Initialize to see if
the python installation is good.  This test fails for me.

The reason is that "python-config.py --ldflags" is returning:

	-L/local/home/sellcey/gcc/mt/src/install-python/lib/python2.7/config -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic

and if I link with this I get undefined references because libpython2.7 is
listed *after* libutil, libm, and libdl and is an archive library.  If I
move it before (by hand) the link works.

Has anyone else run into this?

Steve Ellcey
sellcey@mips.com


             reply	other threads:[~2013-11-08  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  0:03 Steve Ellcey  [this message]
2013-11-08  2:45 ` Joel Brobecker

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=d0bdf801-dcec-4757-81d9-f1cb92326ab9@BAMAIL02.ba.imgtec.org \
    --to=sellcey@mips.com \
    --cc=gdb@sourceware.org \
    /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