From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>,
asmwarrior@gmail.com, gdb@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: gdb with python support still get crash on showing uninitialized local variables
Date: Fri, 29 Oct 2010 19:18:00 -0000 [thread overview]
Message-ID: <20101029191820.GA2936@adacore.com> (raw)
In-Reply-To: <83bp6l9b4l.fsf@gnu.org>
> > asmwarrior> /bin/sh: line 1: ../../../../src/gdb/bfd/../mkinstalldirs: Permission denied
> >
> > This file should be +x.
>
> There's no such thing on Windows.
Yes, because it's a script, the makefile should execute it via $SHELL.
I see that we're making the same error in gdb/doc, for instance, so
it looks like we would be unable to build the documentation if building
using MinGW tools.
I am flying back this evening, so I will try to remember to send a patch
soon.
--
Joel
next prev parent reply other threads:[~2010-10-29 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CB66700.3000907@gmail.com>
[not found] ` <m3tykn2id8.fsf@fleche.redhat.com>
2010-10-19 20:17 ` RFA: add python exception subclasses (Was: gdb with python support still get crash on showing uninitialized local variables) Tom Tromey
2010-10-19 21:13 ` Eli Zaretskii
2010-10-20 5:19 ` gdb with python support still get crash on showing uninitialized local variables asmwarrior
2010-10-22 19:13 ` Tom Tromey
2010-10-22 21:22 ` Eli Zaretskii
2010-10-29 19:18 ` Joel Brobecker [this message]
2010-10-29 22:01 ` Eli Zaretskii
2010-10-31 2:24 ` asmwarrior
2010-11-12 20:47 ` RFA: add python exception subclasses Tom Tromey
[not found] ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04 ` Tom Tromey
2010-12-18 2:26 ` asmwarrior
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=20101029191820.GA2936@adacore.com \
--to=brobecker@adacore.com \
--cc=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--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