Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Doug Evans <dje@google.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
	 Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tromey@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: Possible fix for mingw32 directory relocation problems
Date: Tue, 17 Jan 2012 06:48:00 -0000	[thread overview]
Message-ID: <4F15111E.3060904@gmail.com> (raw)
In-Reply-To: <CADPb22TK7_csatjnORZoLeuRty9aXM+=hzBykYeWk6XzG-aPjQ@mail.gmail.com>

On 2012-1-17 13:29, Doug Evans wrote:
> On Mon, Jan 16, 2012 at 9:16 PM, asmwarrior <asmwarrior@gmail.com> wrote:
>> On 2012-1-17 13:09, Doug Evans wrote:
>>
>> [- gdb-patches]
>>
>> On Mon, Jan 16, 2012 at 5:07 PM, asm warrior <asmwarrior@gmail.com> wrote:
>>
>> I'm not quite familiar with autoconf either. So, suppose we can put
>> BINDIR in config.h, I think we still have some problem.
>> Those values (DEBUGDIR, GDB_DATADIR, JIT_READER_DIR, BINDIR) were
>> macro definition strings, so there are location are still fixed.
>>
>> But under Windows, I think there are many conditions that gdb.exe and
>> other related gdb's share folder will be copied and pasted to many
>> different paths. So, a true relocate scheme is still necessary.
>>
>> Beyond what GDB has already?
>>
>> [I get the feeling people just aren't listening to me ...]
>>
>> Dear Doug.
>>
>> Sorry, I may slip your messages. (My English is not quite good) or I may not
>> fully understand your idea.
>> I just review your posts under "Building GDB 7.3.92 with MinGW" thread, and
>> you have said:
>>
>> *If* there is a bug here, and it's not pilot error, it feels like
>> perhaps the bug is in relocate_gdb_directory.
>> [Why don't all calls to relocate_gdb_directory require similar treatment?
>> Thus this feels like the wrong way to go.]
>>
>> Maybe if you provide a sample session (and complete session please, no
>> editing to trim it down), that will help.
>>
>>
>> I don't fully understand the above sentences. Sorry.
>> You mean we can change/improve the function body of
>> "relocate_gdb_directory".
> Let's put it this way.
> If we move the definitions of BINDIR and TARGET_SYSTEM_ROOT to config.h,
> what is still broken?
>
> [btw, I'm working on such a patch.]
It looks like under Windows/MinGW, relocation GDB_DATADIR will
internally call a function in libiberty


char *
make_relative_prefix (const char *progname, const char *bin_prefix,
              const char *prefix)

Now, the arguments maybe looks like:
progname          = "e:/mymingw/bin/gdb.exe"  (this is the folder you
copy to)
bin_prefix=BINDIR = "E:/msys/mingw32/msys/1.0/local/bin"   
prefix            = "/usr/local/share/gdb"

The return value should be a "relative path" to ""e:/mymingw/bin/"

Right?

asmwarrior

PS: I have cc gdb-patches mail list.





  parent reply	other threads:[~2012-01-17  6:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f143c35.4fecd80a.473e.ffffbd75SMTPIN_ADDED@mx.google.com>
2012-01-17  2:49 ` asm warrior
     [not found]   ` <CADPb22SvBMEt9=EwMNZE6m+=_jfJZxTt1C2Pn-rH9OpHKUJCJQ@mail.gmail.com>
     [not found]     ` <4F150434.3020102@gmail.com>
     [not found]       ` <CADPb22TK7_csatjnORZoLeuRty9aXM+=hzBykYeWk6XzG-aPjQ@mail.gmail.com>
2012-01-17  6:48         ` asmwarrior [this message]
2012-01-17  7:00           ` Asmwarrior
     [not found] <4f143c53.ca3c440a.1d95.ffff9b71SMTPIN_ADDED@mx.google.com>
2012-01-17  9:56 ` Doug Evans
2012-01-17 13:40   ` asmwarrior
2012-01-17 14:15     ` asmwarrior
2012-01-17 15:03   ` Pierre Muller
     [not found]   ` <4f158a75.65ecd80a.69cb.7083SMTPIN_ADDED@mx.google.com>
2012-01-17 15:34     ` asmwarrior
     [not found]   ` <4f158a77.833ed80a.629b.7837SMTPIN_ADDED@mx.google.com>
2012-01-17 16:11     ` Doug Evans
2012-01-18 19:01     ` Doug Evans
2012-01-16 15:17 Pierre Muller

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=4F15111E.3060904@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=tromey@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