public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/98175] New: Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path)
@ 2020-12-07 13:50 marcoxa at gmail dot com
  2020-12-07 14:33 ` [Bug driver/98175] " dominiq at lps dot ens.fr
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: marcoxa at gmail dot com @ 2020-12-07 13:50 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98175

            Bug ID: 98175
           Summary: Problem with gcc front end and ld on vanilla Windows
                    10 installation (spaces in path)
           Product: gcc
           Version: 8.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marcoxa at gmail dot com
  Target Milestone: ---

Hi

this came up while installing an update for "ps" in the latest R/Rtools/Rstudio
combination.  This is for 8.3.0 as included in Rtools 4.0.x.  I don't know if
it affects later versions of the GCC toolchain.

I was able to reproduce it on a simpler case.  Bottom line: while the GCC
compiler frontend does not quote the "ld.exe" invocation.

```
g:\My Drive\Work\Projects\Hacking\elisp\iron-main\tests>"c:\Program
Files\R\Rtools40\mingw64\bin\gfortran" hello.f 
"c:\Program Files\R\Rtools40\mingw64\bin\gfortran" hello.f 
c:/Program
Files/R/Rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
cannot find c:/Program: No such file or directory
c:/Program
Files/R/Rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
cannot find
Files/R/Rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/lib/../lib/default-manifest.o:
No such file or directory
collect2.exe: error: ld returned 1 exit status

```

Note that Rtools 4.0.x correctly quotes the gfortran (or gcc) command.  But
then, the inner call to "ld.exe" is not.

I know I can work around this by changing the installation path, but people
using vanilla W10 are bound to trip on this quite often. 

All the best

Marco Antoniotti

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug driver/98175] Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path)
  2020-12-07 13:50 [Bug fortran/98175] New: Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path) marcoxa at gmail dot com
@ 2020-12-07 14:33 ` dominiq at lps dot ens.fr
  2020-12-07 15:41 ` marcoxa at gmail dot com
  2021-09-01 22:27 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2020-12-07 14:33 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98175

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-12-07
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This seems target specific.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug driver/98175] Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path)
  2020-12-07 13:50 [Bug fortran/98175] New: Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path) marcoxa at gmail dot com
  2020-12-07 14:33 ` [Bug driver/98175] " dominiq at lps dot ens.fr
@ 2020-12-07 15:41 ` marcoxa at gmail dot com
  2021-09-01 22:27 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: marcoxa at gmail dot com @ 2020-12-07 15:41 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98175

--- Comment #2 from Marco Antoniotti <marcoxa at gmail dot com> ---
In what sense is "target specific"?  Windows specific?

I am asking because I am not versed in the details of the drivers
implementation.

All the best

Marco

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug driver/98175] Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path)
  2020-12-07 13:50 [Bug fortran/98175] New: Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path) marcoxa at gmail dot com
  2020-12-07 14:33 ` [Bug driver/98175] " dominiq at lps dot ens.fr
  2020-12-07 15:41 ` marcoxa at gmail dot com
@ 2021-09-01 22:27 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-09-01 22:27 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98175

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|WAITING                     |RESOLVED

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 89249.

*** This bug has been marked as a duplicate of bug 89249 ***

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-09-01 22:27 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-07 13:50 [Bug fortran/98175] New: Problem with gcc front end and ld on vanilla Windows 10 installation (spaces in path) marcoxa at gmail dot com
2020-12-07 14:33 ` [Bug driver/98175] " dominiq at lps dot ens.fr
2020-12-07 15:41 ` marcoxa at gmail dot com
2021-09-01 22:27 ` pinskia at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).