Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: chastain@sourceware.org, gdb-prs@sources.redhat.com,
	gdb-gnats@sources.redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: server/519: gdb fails to configure since some configure scripts lack execute permission
Date: Mon, 26 Apr 2004 21:20:00 -0000	[thread overview]
Message-ID: <16525.30124.599514.494256@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20040104204951.25454.qmail@sources.redhat.com>

chastain@sourceware.org writes:

>     This problam has not been fixed yet, so I am re-opening the bug.
>     
>     In gdb HEAD as of 2004-01-04:
>     
>       % ls -l $(find * -type f -name configure -print) | sort
>       -rw-r--r--    1 mec.gnu  mgnu        30802 Apr 15  1999 gdb/testsuite/gdb.stabs/configure
>       -rw-r--r--    1 mec.gnu  mgnu        30857 Aug 29 12:37 sim/testsuite/frv-elf/configure
>       -rw-r--r--    1 mec.gnu  mgnu        60386 Jun 29  2003 gdb/gdbserver/configure
>       -rw-r--r--    1 mec.gnu  mgnu       124468 Aug 29 12:35 sim/frv/configure

This is still unfixed in GDB 6.1 ;-(

>     Can I get someone to go into the repository and chmod these four files to 0755?

Can someone *please* fix this trivial but permanently annoying issue on the
CVS server?  This is broken since at least GDB 5.2, but nobody bothered to
spend the five seconds to fix it yet.

Thanks.
	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University


       reply	other threads:[~2004-04-26 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040104204951.25454.qmail@sources.redhat.com>
2004-04-26 21:20 ` Rainer Orth [this message]
2004-04-26 21:32   ` Ian Lance Taylor
2004-04-27 16:40     ` Rainer Orth

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=16525.30124.599514.494256@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=chastain@sourceware.org \
    --cc=gdb-gnats@sources.redhat.com \
    --cc=gdb-prs@sources.redhat.com \
    --cc=gdb@sources.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