[GHC] #12971: gcc not finding default temporary directory

newer
[GHC] #13305: static: check for...

older
[GHC] #13315: Compile broken on...

GHC

13 Dec 2016 13 Dec '16

10:26 p.m.

#12971: gcc not finding default temporary directory -------------------------------------+------------------------------------- Reporter: erikprantare | Owner: Type: feature | Status: new request | Priority: normal | Milestone: Component: Compiler | Version: 8.0.1 Keywords: | Operating System: Unknown/Multiple Architecture: | Type of failure: None/Unknown Unknown/Multiple | Test Case: | Blocked By: Blocking: | Related Tickets: Differential Rev(s): | Wiki Page: -------------------------------------+------------------------------------- Hello, I've been trying to get the ghc to compile a .hs file to binary. I get an error that seems to be caused during the C compilation phase from the special character ä in my user directory. When compiling I get this: {{{ C:\Users\Erik Präntare>ghc C:\code\Haskell\test.hs Linking C:\code\Haskell\test.exe ... realgcc.exe: error: C:\Users\Erik Pr├ñntare\AppData\Local\Temp\ghc28912_0\ghc_1. c: No such file or directory realgcc.exe: fatal error: no input files compilation terminated. `gcc.exe' failed in phase `C Compiler'. (Exit code: 1) }}} Notice how it says Pr├ñntare instead of Präntare. The UTF-8 encoding for ä is 0xC3 0xA4 which, surprise surprise, corresponds to ├ñ in ASCII. Now, I managed to get around this by changing the tmpdir to my actual temporary directory, but as a new user of ghc it was very troublesome to find a solution. Maybe consider changing the default tmpdir, at least if special characters are encountered? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

Show replies by date

GHC

13 Dec 13 Dec

10:30 p.m.

New subject: [GHC] #12971: Change default tmpdir (was: gcc not finding default temporary directory)

#12971: Change default tmpdir -------------------------------------+------------------------------------- Reporter: erikprantare | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

15 Dec 15 Dec

5:20 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC (was: Change default tmpdir)

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Changes (by bgamari): * priority: normal => highest * os: Unknown/Multiple => Windows * type: feature request => bug * milestone: => 8.2.1 Comment: Oh dear, it looks like we are failing to encode a filename with UTF-16 as expected by Windows. This is quite -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

5:26 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Comment (by bgamari): Indeed I can reproduce this with, {{{ $ mkdir Präntare $ export TMP=`pwd`/Präntare $ echo 'main = putStrLn "hello world!"' > Hello.hs $ ghc Hello.hs 1 of 1] Compiling Main ( Hello.hs, Hello.o ) Linking Hello.exe ... realgcc.exe: error: C:\msys64\home\ben\Präntare\ghc2596_0\ghc_4.c: No such file or directory realgcc.exe: fatal error: no input files compilation terminated. `gcc.exe' failed in phase `C Compiler'. (Exit code: 1) $ export TMP=/tmp $ ghc Hello.hs Linking Hello.exe ... }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

5:28 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Comment (by bgamari): `ghc -v` reveals that the failing command is, {{{ Linking Hello.exe ... *** C Compiler: "C:\msys64\home\ben\ghc-8.0.1-i386\lib/../mingw/bin/gcc.exe" "-U__i686" "-march=i686" "-fno-stack-protector" "-DTABLES_NEXT_TO_CODE" "-c" "C:\msys64\home\ben\Prntare\ghc4688_0\ghc_4.c" "-o" "C:\msys64\home\ben\Prntare\ghc4688_0\ghc_5.o" "-IC:\msys64\home\ben\ghc-8.0.1-i386\lib/include" realgcc.exe: error: C:\msys64\home\ben\Präntare\ghc4688_0\ghc_4.c: No such file or directory realgcc.exe: fatal error: no input files compilation terminated. }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

5:37 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

GHC

5:46 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Comment (by bgamari): Hmm, the missing `ä` above may have just been due to the terminal. Redirecting `ghc`'s output to a file and viewing the file with vim shows the following, {{{ Linking Hello.exe ... *** C Compiler: "C:\msys64\home\ben\ghc-8.0.1-i386\lib/../mingw/bin/gcc.exe" "-U__i686" \ "-march=i686" "-fno-stack-protector" "-DTABLES_NEXT_TO_CODE" "-c" \ "C:\msys64\home\ben\Pr<84>ntare\ghc4344_0\ghc_4.c" \ "-o" "C:\msys64\home\ben\Pr<84>ntare\ghc4344_0\ghc_5.o" \ "-IC:\msys64\home\ben\ghc-8.0.1-i386\lib/include" realgcc.exe: error: C:\msys64\home\ben\PrÃ¤ntare\ghc4344_0\ghc_4.c: No such file or directory }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

7:33 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

GHC

11:17 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Phyx Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Comment (by Ben Gamari ): In [changeset:"8f0546bfaf47ec865bb0c6dc2cb0ac451367f65a/ghc" 8f0546bf/ghc]: {{{ #!CommitTicketReference repository="ghc" revision="8f0546bfaf47ec865bb0c6dc2cb0ac451367f65a" testsuite: Add test for #12971 Test Plan: Validate Reviewers: austin Subscribers: thomie Differential Revision: https://phabricator.haskell.org/D2855 GHC Trac Issues: #12971 }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:8 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

21 Dec 21 Dec

12:11 a.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC ---------------------------------+---------------------------------------- Reporter: erikprantare | Owner: Phyx Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | ---------------------------------+---------------------------------------- Comment (by Phyx-): Ok, this issue is an upstream one. The problem is with how the response files are read into GCC. We write out a UTF8 file but the relevant code in `libiberty`[1] assumes 1 byte per character. It works fine if response files aren't used since the rest of the argument handling code seems to work fine with utf-16 and utf-8. Assuming we want to keep the response files, one possible work around would be to convert all paths to the dos short paths. [1] https://github.com/gcc-mirror/gcc/blob/master/libiberty/argv.c#L420 -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:9 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

5 Jan 5 Jan

3:01 a.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

GHC

8 Jan 8 Jan

2:14 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

GHC

15 Jan 15 Jan

1 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

#12971: Paths are encoded incorrectly when invoking GCC -------------------------------------+------------------------------------- Reporter: erikprantare | Owner: Phyx Type: bug | Status: patch Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.0.1 Resolution: | Keywords: Operating System: Windows | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D2917 Wiki Page: | Phab:/D2942 -------------------------------------+------------------------------------- Comment (by Tamar Christina ): In [changeset:"f63c8ef33ec9666688163abe4ccf2d6c0428a7e7/ghc" f63c8ef/ghc]: {{{ #!CommitTicketReference repository="ghc" revision="f63c8ef33ec9666688163abe4ccf2d6c0428a7e7" Use latin1 code page on Windows for response files. Summary: D2917 added a change that will make paths on Windows response files use DOS 8.3 shortnames to get around the fact that `libiberty` assumes a one byte per character encoding. This is actually not the problem, the actual problem is that GCC on Windows doesn't seem to support Unicode at all. This comes down to how unicode characters are handled between POSIX and Windows. On Windows, Unicode is only supported using a multibyte character encoding such as `wchar_t` with calls to the appropriate wide version of APIs (name post-fixed with the `W` character). On Posix I believe the standard `char` is used and based on the value it is decoded to the correct string. GCC doesn't seem to make calls to the Wide version of the Windows APIs, and even if it did, it's character representation would be wrong. So I believe GCC just does not support utf-8 paths on Windows. So the hack in D2917 is the only way to get Unicode support. The problem is however that `GCC` is not the only tool with this issue and we don't use response files for every invocation of the tools. Most of the tools probably don't support it. Furthermore, DOS 8.1 shortnames only exist when the path or file physically exists on disk. We pass lots of paths to GCC that don't exist yet, like the output file. D2917 works around this by splitting the path from the file and try shortening that. But this may not always work. In short, even if we do Unicode correctly (which we don't atm, the GCC driver we build uses `char` instead of `wchar_t`) we won't be able to compile using unicode paths that need to be passed to `GCC`. So not sure about the point of D2917. What we can do is support the most common non-ascii characters by writing the response files out using the `latin1` code page. Test Plan: compile + make test TEST=T12971 Reviewers: austin, bgamari, erikd Reviewed By: bgamari Subscribers: thomie, #ghc_windows_task_force Differential Revision: https://phabricator.haskell.org/D2942 GHC Trac Issues: #12971 }}} -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12971#comment:12 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

GHC

1:02 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

GHC

24 Feb 24 Feb

7:44 p.m.

New subject: [GHC] #12971: Paths are encoded incorrectly when invoking GCC

3060

Age (days ago)

3133

Last active (days ago)

List overview

Download

14 comments

1 participants

[GHC] #12971: gcc not finding default temporary directory

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

GHC

tags

participants (1)