From: asmwarrior <asmwarrior@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Possible fix for mingw32 directory relocation problems
Date: Tue, 17 Jan 2012 13:40:00 -0000 [thread overview]
Message-ID: <4F156BDE.6030609@gmail.com> (raw)
In-Reply-To: <CADPb22Q+3zmxi4-cr=-ze7eyJEizDqL_Yn2YxtuopKD3ZaDR+A@mail.gmail.com>
On 2012-1-17 15:00, Doug Evans wrote:
> Possible patch is attached. Can you try it? I don't know that it will fix things, but based on what you've said it seems reasonable to try. There is an open issue that the current --with-sysroot relocatability computation is different than what GDB_AC_WITH_DIR does. We should fix that regardless. I've left that as a separate issue. [We should resolve it before checkin, but at this point I'm willing to just experiment until we know what the right fix is.]
>> I don't have enough knowledge about autoconf scripts to
>> handle this...
>> An extra bonus of this change would be that it would
>> render the special rule for main.o compilation unnecessary.
Would you mind to give a full patch (include the diff of configure and config.in).
Under MSYS+autotools
I have problems generate those files by reference:
http://sourceware.org/gdb/wiki/DeveloperTips#Editing_configure.ac
$ aclocal -I gnulib/m4
acinclude.m4:84: the serial number must appear before any macro definition
configure.ac:22: error: Please use exactly Autoconf 2.64 instead of 2.68.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:22: the top level
autom4te: /bin/m4 failed with exit status: 1
aclocal: autom4te failed with exit status: 1
Thanks.
asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2012-01-17 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f143c53.ca3c440a.1d95.ffff9b71SMTPIN_ADDED@mx.google.com>
2012-01-17 9:56 ` Doug Evans
2012-01-17 13:40 ` asmwarrior [this message]
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
[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
2012-01-17 7:00 ` Asmwarrior
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=4F156BDE.6030609@gmail.com \
--to=asmwarrior@gmail.com \
--cc=dje@google.com \
--cc=gdb-patches@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