This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
stringification of PREFIX etc...
- From: Basile Starynkevitch <basile at starynkevitch dot net>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 26 Sep 2011 11:07:53 +0200
- Subject: stringification of PREFIX etc...
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, such as double-quotes " or backslashes \ or perhaps even spaces.
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.?
(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 tabulations in file names is very bad taste but probably possible.).
Do we have a convention that the PREFIX can only have sensible characters, so that backslashes, spaces, double-quotes are forbidden there? What about Unicode UTF8?
Within the context of MELT, I also have to make as string constants several directories (etc.) related to the prefix or to the plugin directory. Should I care about naughty characters inside?
For curious people, see
http://groups.google.com/group/gcc-melt/browse_thread/thread/74c36fae50a2b47d
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***