From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, carlton@math.stanford.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ vs dos names
Date: Thu, 09 Jan 2003 17:33:00 -0000 [thread overview]
Message-ID: <200301091733.h09HX1D03136@duracef.shout.net> (raw)
Well, the snapshot tarball has testsuite/gdb.*/Makefile files in it,
thus there are 8.3 conflicts in every testsuite directory. We're just
lucky that ARI saw a problem with gdb.c++/Makefile because of the
gdb.c++ part.
I can't read the script that makes the snapshot tarballs,
so I can't go any further.
. doc/gdbint.texinfo is out of date
. "make -f Makefile.in gdb.tar.gz" does not work now that
Makefile.in is autogen'ed, because it has plenty of @foo@ magic.
. "configure ; make gdb.tar.gz" fails because the top Makefile
no longer has any rules to make gdb.tar.gz or gdb.tar.
. gdbadmin is not accessible to me
. http://sources.redhat.com/gdb/current has instructions for getting
the administration scripts, but they are not working
. checkout as anoncvs fails:
bash-2.05b$ cvs -z9 -d :pserver:anoncvs@sources.redhat.com:/cvs/gdbadmin login
Logging in to :pserver:anoncvs@sources.redhat.com:2401/cvs/gdbadmin
CVS password:
bash-2.05b$ cvs -z9 -d :pserver:anoncvs@sources.redhat.com:/cvs/gdbadmin co .
cvs server: Updating .
cvs server: failed to create lock directory for `/cvs/gdbadmin' (/cvs/gdbadmin/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository `/cvs/gdbadmin'
cvs [server aborted]: read lock failed - giving up
. checkout with my gdb developer identity fails:
bash-2.05b$ cvs -z9 -d :ext:chastain@sources.redhat.com:/cvs/gdbadmin co .
Enter passphrase for RSA key '/berman/home/mec/.ssh/identity':
Warning: Remote host denied authentication agent forwarding.
cvs server: Updating .
cvs server: failed to create lock directory for `/cvs/gdbadmin' (/cvs/gdbadmin/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository `/cvs/gdbadmin'
cvs [server aborted]: read lock failed - giving up
These are doco and web bugs. Which of them would you like me to
file PR's on?
Michael C
next reply other threads:[~2003-01-09 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 17:33 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 20:49 Michael Elizabeth Chastain
2003-01-09 17:52 Michael Elizabeth Chastain
2003-01-09 18:23 ` Daniel Jacobowitz
2003-01-09 18:50 ` Daniel Jacobowitz
2003-01-09 18:55 ` Andrew Cagney
2003-01-09 16:45 Michael Elizabeth Chastain
2003-01-10 20:22 ` Eli Zaretskii
2003-01-09 16:22 Andrew Cagney
2003-01-09 17:24 ` David Carlton
2003-01-09 17:27 ` David Carlton
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=200301091733.h09HX1D03136@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@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