From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4160 invoked by alias); 16 Jun 2010 18:09:26 -0000 Received: (qmail 4148 invoked by uid 22791); 16 Jun 2010 18:09:25 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 Jun 2010 18:09:20 +0000 Received: from kpbe15.cbf.corp.google.com (kpbe15.cbf.corp.google.com [172.25.105.79]) by smtp-out.google.com with ESMTP id o5GI9HDp003909 for ; Wed, 16 Jun 2010 11:09:18 -0700 Received: from gxk22 (gxk22.prod.google.com [10.202.11.22]) by kpbe15.cbf.corp.google.com with ESMTP id o5GI8vdX007260 for ; Wed, 16 Jun 2010 11:09:16 -0700 Received: by gxk22 with SMTP id 22so1423810gxk.8 for ; Wed, 16 Jun 2010 11:09:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.87.106 with SMTP id v42mr4579513qal.23.1276711748397; Wed, 16 Jun 2010 11:09:08 -0700 (PDT) Received: by 10.220.189.201 with HTTP; Wed, 16 Jun 2010 11:08:57 -0700 (PDT) In-Reply-To: References: <4C162783.4010706@gmail.com> Date: Wed, 16 Jun 2010 18:09:00 -0000 Message-ID: Subject: Re: issue about building windows version of gdb with python support From: Doug Evans To: tromey@redhat.com Cc: asmwarrior , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-06/txt/msg00061.txt.bz2 On Wed, Jun 16, 2010 at 10:36 AM, Tom Tromey wrote: >>>>>> ">" =3D=3D Asm gmail writes: > >>> Today, I have build a gdb.exe with python support under windows(i'm >>> using TDMMinGW 4.5 dw2 version, I use the latest gdb snapshot 7.1.5 >>> 20100613, python 2.6.5). > [...] >>> E:\XXXX\python this is the root folder. >>> Then E:\XXXX\python\include, this is the header directory. >>> Then, the lib foldee was: E:\XXXX\python\libs =A0 =A0 =A0 =A0(please no= te that >>> the path name is"libs" not lib.) > > Hmm, I would have thought that the python-config.py stuff (in > gdb/python/) would do the right thing here. It should for ldflags I think, but the include files assume pythonX.Y/*.h. I didn't want to bubble up all of python's headers to the top level (crikey!) so I kept gdb's original way of including them.