On Tue, 27 Sep 2011 21:56:12 + (UTC)
"Joseph S. Myers" wrote:
> On Mon, 26 Sep 2011, Basile Starynkevitch wrote:
>
> > Hello All,
> >
> > It seems to me (file gcc/Makefile.in, definition of DRIVER_DEFINES) that
> > the configure-d PREFIX is wired inside gcc.o (hence inside the gcc
> > dri
On Mon, 26 Sep 2011, Basile Starynkevitch wrote:
> Hello All,
>
> It seems to me (file gcc/Makefile.in, definition of DRIVER_DEFINES) that
> the configure-d PREFIX is wired inside gcc.o (hence inside the gcc
> driver executable) without precautions.
>
> In particular, I don't understand if som
Basile Starynkevitch writes:
> My intuition is that GCC won't even build if the prefix contains such naughty
> characters. If it is the case, should we document that.?
It's easy enough to try it. You're right: spaces and double quotes in
--prefix don't work. Rather than document that restrict
(I heard that on Windows systems, it is often the case that the
prefix contains spaces. I believe that on GNU/Linux systems, the only
forbidden characters in file paths are the slash -used as directory
separator- and the null character, putting spaces, asterisks,
question marks, newlines or tabu
Hello All,
It seems to me (file gcc/Makefile.in, definition of DRIVER_DEFINES) that the
configure-d PREFIX is wired inside
gcc.o (hence inside the gcc driver executable) without precautions.
In particular, I don't understand if someone can configure gcc with a prefix
containing weird characters
