From: Nick Clifton <nickc@cambridge.redhat.com>
To: muller@cerbere.u-strasbg.fr
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Can't build binutils with read-only source; Was: Linux GDB compilation problem
Date: Fri, 26 Oct 2001 02:26:00 -0000 [thread overview]
Message-ID: <m3y9lyu58a.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <3BD836FF.3060100@cygnus.com>
Hi Pierre,
Your message has been forwarded to the binutils mailing list, since
the opcodes library is officially part of that project.
> > Shouldn't it be possible to confugre and make even if
> > the source is on another mount or even only read-only
> > (on a cd-rom or owner by someone else ?)
You are correct however, a simple build of the opcodes library, as
part of GDB or for any other reason, should not try to modify the
source directory.
> > A mv command fails because it tries to move a file
> > from my compilation dir into a subdir of the sourcedir.
Can you provide some more information please ? Which version of the
binutils sources are you using. (If you build the objdump
disassembler program and run "objdump --version", this should tell
you). What file was the build process trying to move into the
source directory ?
> > The precise location where this happens is in
> > [all-opcodes]
> > [1] [all-recursive-am]
> > [2] [all-recursive]
> > [3] [POTFILES.in]
> > [4] [po/POTFILES.in]
The all-recursive-am target is for the automatic rebuilding of the
Makefile. In this case it would appear that make is trying to
rebuild the Makefile.in or config.h files in the source directory.
This would indicate that the timestamps on your Makefile.am or
config.in files are wrong (or you have edited them).
Cheers
Nick
prev parent reply other threads:[~2001-10-26 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 5:03 Pierre Muller
2001-10-25 9:00 ` Can't build binutils with read-only source; Was: " Andrew Cagney
2001-10-26 2:26 ` Nick Clifton [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=m3y9lyu58a.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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