Link errors due to forcibly exporting findPtr
The change in https://phabricator.haskell.org/rGHC900c47f88784b91517c00be3e1087322e62f698e is causing link errors due to the combination of `-Wl,-u` and `-Wl,--export-all-symbols`
```
Wrong exit code for T10955dyn()(expected 0 , actual 2 )
Stderr ( T10955dyn ):
E:/ghc-dev/msys64/home/Tamar/ghc/rts/dist/build/libHSrts_thr.a(Printer.thr_o): In function `findPtr':
E:\ghc-dev\msys64\home\Tamar\ghc/rts/Printer.c:880: multiple definition of `findPtr'
./bin_dyn/libA.dll.a(d020776.o):(.text+0x0): first defined here
```
I believe the correct solution is to just use a cabal flag to emulate the setup we had with make, instead of forcing this symbol always.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ---------------------------------------------- |
| Version | 8.4.3 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Compiler |
| Test case | |
| Differential revisions | [D5138](https://phabricator.haskell.org/D5138) |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"Link errors due to forcibly exporting findPtr","status":"New","operating_system":"","component":"Compiler","related":[],"milestone":"8.6.1","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"8.4.3","keywords":[],"differentials":[5138],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"The change in https://phabricator.haskell.org/rGHC900c47f88784b91517c00be3e1087322e62f698e is causing link errors due to the combination of `-Wl,-u` and `-Wl,--export-all-symbols`\r\n\r\n{{{\r\nWrong exit code for T10955dyn()(expected 0 , actual 2 )\r\nStderr ( T10955dyn ):\r\nE:/ghc-dev/msys64/home/Tamar/ghc/rts/dist/build/libHSrts_thr.a(Printer.thr_o): In function `findPtr':\r\nE:\\ghc-dev\\msys64\\home\\Tamar\\ghc/rts/Printer.c:880: multiple definition of `findPtr'\r\n./bin_dyn/libA.dll.a(d020776.o):(.text+0x0): first defined here\r\n}}}\r\n\r\nI believe the correct solution is to just use a cabal flag to emulate the setup we had with make, instead of forcing this symbol always.\r\n","type_of_failure":"OtherFailure","blocking":[]} -->
issue