From: Keith Seitz <keiths@redhat.com>
To: "Stephen P. Smith" <ischis2@cox.net>
Cc: insight@sources.redhat.com
Subject: Re: What does thios error mean
Date: Wed, 29 Oct 2003 14:33:00 -0000 [thread overview]
Message-ID: <3F9F5F55.2080503@redhat.com> (raw)
In-Reply-To: <3F9F444C.9060504@cox.net>
Stephen P. Smith wrote:
>
> /htc/GNUSource/gdb-source-tree/gdb-current/configure
> --prefix=/usr/local/bleeding-edge-gdb --target=powerpc-motorola-elf
> --host=i686-pc-cygwin --build=i686-pc-cygwin
> make
> make install
> make[3]: Leaving directory
> `/htc/GNUSource/gdb-source-tree/build-insight-powerpc-motorola-elf/dejagnu'
> make[2]: Leaving directory
> `/htc/GNUSource/gdb-source-tree/build-insight-powerpc-motorola-elf/dejagnu'
> make[1]: Leaving directory
> `/htc/GNUSource/gdb-source-tree/build-insight-powerpc-motorola-elf/dejagnu'
> cd: can't cd to etc
> make: *** [install-etc] Error 2
> + cd /htc/GNUSource/gdb-source-tree
>
> Funny thing, the etc directory was there when I did the cvs co.
Don't know about the specific error, but it looks like something failed
to install into PREFIX/etc. If you're just trying to build insight/gdb,
and you don't care about the stuff in etc (which insight and gdb don't),
you can "work around" this problem by using the make target
"install-gdb". FWIW, I usually only use "make all-gdb" and "make
install-gdb" when I build, which is why I've never noticed this.
If you do care, or you just want to notify someone that something might
be amiss, src/MAINTAINERS will list the person/mailing list to contact.
Keith
prev parent reply other threads:[~2003-10-29 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F9EDA45.3090908@cox.net>
2003-10-28 21:40 ` Keith Seitz
[not found] ` <3F9EE402.7080005@cox.net>
[not found] ` <3F9E7433.4030305@redhat.com>
[not found] ` <3F9EE70D.6050506@cox.net>
[not found] ` <3F9E78C2.3000508@redhat.com>
2003-10-29 4:38 ` Stephen P. Smith
2003-10-29 14:33 ` Keith Seitz [this message]
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=3F9F5F55.2080503@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=ischis2@cox.net \
/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).