From: "Frank Ch. Eigler" <fche@redhat.com>
To: Erland Lewin <erl@voxi.com>
Cc: sid@sources.redhat.com
Subject: Re: [Fwd: gdb/187: cp error in sid/component/lcd/testsuite]
Date: Wed, 01 Aug 2001 08:16:00 -0000 [thread overview]
Message-ID: <20010801111625.A31688@redhat.com> (raw)
In-Reply-To: <3B681BB7.6010204@voxi.com>
Hi -
On Wed, Aug 01, 2001 at 05:09:43PM +0200, Erland Lewin wrote:
: Since gdb-gnats said:
:
: Thank you very much for your problem report.
: It has the internal identification `gdb/187'.
: The individual assigned to look at your
: report is: unassigned.
:
: I thought I'd make sure you got this because it seems to be in your
: Makefile.am that the cp statement is... :-)
: See the attached bug report.
Thanks. sid/ is not really associated with gdb/, so I expect
gdb-gnats guys will close this problem and pass it over to
sid@sources.redhat.com anyway. Or you could close it and save
them some effort.
: [...]
: Subject: gdb/187: cp error in sid/component/lcd/testsuite
: [...]
: cp ./hd-one-line.conf .
: cp: `./hd-one-line.conf' and `./hd-one-line.conf' are the same file
: [...]
: ./configure --prefix=/usr
: [...]
In general, we need to build sid in a tree separate from the source tree.
Most of the other tools also prefer this arrangement, so you should probably
mkdir /some-build-tree
cd /some-build-tree
/path_to_source_tree/configure --prefix=/path_to_install_tree
make
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7aB1JVZbdDOm/ZT0RAmz0AJ0VwUBsE++ET+SU7cnY4WX5iKp9JQCfZXvs
7MQHgy9cT6jCjfoM+UuUVeQ=
=/bBv
-----END PGP SIGNATURE-----
parent reply other threads:[~2001-08-01 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3B681BB7.6010204@voxi.com>]
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=20010801111625.A31688@redhat.com \
--to=fche@redhat.com \
--cc=erl@voxi.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).