This is the mail archive of the
mailing list for the binutils project.
Re: Is binutils allowed to use $(prefix)/i686-pc-mingw32 directory?
- From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
- To: "Richard W.M. Jones" <rjones at redhat dot com>
- Cc: binutils at sourceware dot org
- Date: Tue, 08 Jul 2008 17:31:54 +0200
- Subject: Re: Is binutils allowed to use $(prefix)/i686-pc-mingw32 directory?
- References: <20080708152003.GA16951@amd.home.annexia.org>
On Tue, 2008-07-08 at 16:20 +0100, Richard W.M. Jones wrote:
> I'm building a cross-compile toolchain for Fedora, and I've come
> across the possible problem that binutils places files under
> Start from upstream binutils-2.18.50, then:
> ./configure \
> --prefix=/usr \
> --build=i686-gnu-linux --host=i686-gnu-linux --target=i686-pc-mingw32
> make install
> will create /usr/i686-pc-mingw32/bin directory.
Correct. This is the binutils', internal, private tools' directory.
> The FHS doesn't say anything about being allowed to create this
> directory within /usr so I'm wondering what standard allows this, and
> whether this is the right directory to use.
Correct, this directory doesn't comply to the FHS, but is being used by
GCC for decades. So it's more or less an existing defacto standard.
Unfortunately changing this is non-trivial and would require substantial
surgery to GCC.