This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/49178] [4.6/4.7 Regression] Space between linker option and library in gfortran
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 26 May 2011 19:40:20 +0000
- Subject: [Bug driver/49178] [4.6/4.7 Regression] Space between linker option and library in gfortran
- Auto-submitted: auto-generated
- References: <bug-49178-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49178
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-05-26 19:39:50 UTC ---
What exactly is the problem? Is the gfortran driver invoking a subprocess
with separate "-l" and "gfortran" arguments? The code in gcc.c that does
case OPT_l:
/* POSIX allows separation of -l and the lib arg; canonicalize
by concatenating -l with its arg */
add_infile (concat ("-l", arg, NULL), "*");
do_save = false;
break;
is supposed to act after lang_specific_driver has modified the command
line, and should avoid that issue. Or is something processing the
"Driving" line? I thought that line was human-readable output (complete
with translation of the word "Driving"); it certainly isn't unambiguous in
the presence of arguments containing spaces or newlines. If there are
defined requirements on the "Driving" line, the code that outputs it
should be adjusted to follow those requirements.