From: Andrew Cagney <ac131313@cygnus.com>
To: binutils@sources.redhat.com
Cc: Pierre Muller <muller@cerbere.u-strasbg.fr>, gdb@sources.redhat.com
Subject: Can't build binutils with read-only source; Was: Linux GDB compilation problem
Date: Thu, 25 Oct 2001 09:00:00 -0000 [thread overview]
Message-ID: <3BD836FF.3060100@cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20011025133816.02483e80@ics.u-strasbg.fr>
The below was sent to GDB@
As far as i can tell the analysis is correct. A simple build shouldn't
be trying to modify files in the ``read only'' src/opcodes tree.
enjoy,
Andrew
> I have a trouble to compile gdb on my new linux box.
>
> I have the sources on a subdir of
>
> /data dir that is a mount of a fat32 partition
> (used with cygwin in binmode, so that there are no
> lineend problems)
>
> Trying to compile GDB for linux in a subdir of my /home dir
> that is a mount of another partition,
> I can successfully configure
> but running "make all-gdb" ends with the following error :
> A mv command fails because it tries to move a file
> from my compilation dir into a subdir of the sourcedir.
>
> 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 ?)
>
> I don't think that its normal that
> the make process change the source dir !
> The precise location where this happens is in
> [all-opcodes]
> [1] [all-recursive-am]
> [2] [all-recurvise]
> [3] [POTFILES.in]
> [4] [po/POTFILES.in]
>
>
>
> Pierre Muller
> Institut Charles Sadron
> 6,rue Boussingault
> F 67083 STRASBOURG CEDEX (France)
> mailto:muller@ics.u-strasbg.fr
> Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2001-10-25 9:00 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 ` Andrew Cagney [this message]
2001-10-26 2:26 ` Can't build binutils with read-only source; Was: " Nick Clifton
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=3BD836FF.3060100@cygnus.com \
--to=ac131313@cygnus.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